Malicious code in whalibmob (npm)
The whalibmob npm package contains malicious code that silently subscribes the installer's authenticated WhatsApp account to attacker-controlled channels without user consent. This is achieved by injecting a covert channel-subscription action into the WhatsApp socket layer, issuing authenticated FOLLOW queries to attacker-chosen WhatsApp Channel/Newsletter JIDs. The targeted JIDs are obfuscated or dynamically fetched to evade detection. The malicious behavior does not exfiltrate credentials, establish persistence, or execute arbitrary remote code.
AI Analysis
Technical Summary
The whalibmob package, part of a large family of near-identical Baileys WhatsApp Web library forks, injects code that modifies the WhatsApp socket connection routine. Upon connection, it issues an authenticated 'w:mex' FOLLOW query using the installer's own WhatsApp session to subscribe the victim's account to attacker-controlled channels. The targeted channel JIDs are hidden via obfuscation or fetched dynamically from attacker-controlled hosts, allowing runtime modification of targets without republishing the package. This behavior abuses the installer's authenticated session to increase reach for attacker channels but does not involve credential theft, persistence, or arbitrary code execution.
Potential Impact
Victims unknowingly subscribe their WhatsApp accounts to attacker-controlled channels or newsletters, potentially exposing them to unwanted content or spam. The attack leverages the victim's authenticated session to perform these subscriptions silently. There is no direct credential theft, remote code execution, or persistence established by this malicious code.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing or updating to the affected whalibmob package versions listed. Review and verify package sources before installation. Monitor for suspicious WhatsApp channel subscriptions and remove any unauthorized subscriptions. Since this is a malicious package behavior rather than a traditional vulnerability, remediation depends on avoiding use of the compromised package versions.
Malicious code in whalibmob (npm)
Description
The whalibmob npm package contains malicious code that silently subscribes the installer's authenticated WhatsApp account to attacker-controlled channels without user consent. This is achieved by injecting a covert channel-subscription action into the WhatsApp socket layer, issuing authenticated FOLLOW queries to attacker-chosen WhatsApp Channel/Newsletter JIDs. The targeted JIDs are obfuscated or dynamically fetched to evade detection. The malicious behavior does not exfiltrate credentials, establish persistence, or execute arbitrary remote code.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The whalibmob package, part of a large family of near-identical Baileys WhatsApp Web library forks, injects code that modifies the WhatsApp socket connection routine. Upon connection, it issues an authenticated 'w:mex' FOLLOW query using the installer's own WhatsApp session to subscribe the victim's account to attacker-controlled channels. The targeted channel JIDs are hidden via obfuscation or fetched dynamically from attacker-controlled hosts, allowing runtime modification of targets without republishing the package. This behavior abuses the installer's authenticated session to increase reach for attacker channels but does not involve credential theft, persistence, or arbitrary code execution.
Potential Impact
Victims unknowingly subscribe their WhatsApp accounts to attacker-controlled channels or newsletters, potentially exposing them to unwanted content or spam. The attack leverages the victim's authenticated session to perform these subscriptions silently. There is no direct credential theft, remote code execution, or persistence established by this malicious code.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing or updating to the affected whalibmob package versions listed. Review and verify package sources before installation. Monitor for suspicious WhatsApp channel subscriptions and remove any unauthorized subscriptions. Since this is a malicious package behavior rather than a traditional vulnerability, remediation depends on avoiding use of the compromised package versions.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-17408
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6abd30852a4e24523d340116
Added to database: 09/30/2026, 15:53:41 UTC
Last enriched: 09/30/2026, 16:00:18 UTC
Last updated: 09/30/2026, 22:39:01 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.