Malicious code in @badzz88/baileys (npm)
The @badzz88/baileys npm package, a fork of the Baileys WhatsApp Web library, contains malicious code that silently subscribes the victim's WhatsApp account to attacker-controlled channels without user consent. This is done by injecting a covert FOLLOW query into the WhatsApp socket connection using the installer's authenticated session. The targeted channel IDs are obfuscated or fetched remotely, allowing attackers to change targets post-installation. The malicious code does not steal credentials, maintain persistence, or execute arbitrary code.
AI Analysis
Technical Summary
This threat involves a family of over 100 near-identical malicious forks of the Baileys WhatsApp Web library, including the @badzz88/baileys package versions 8.5.1 through 8.5.9. These forks inject code that, upon socket connection, issues an authenticated 'w:mex' FOLLOW query to attacker-chosen WhatsApp Channel/Newsletter JIDs using the victim's own authenticated session. The target JIDs are hidden via obfuscation or dynamically fetched from attacker-controlled remote sources, enabling stealthy and flexible subscription to unwanted channels. The malicious action leverages the installer's authenticated WhatsApp session to increase subscribers for attacker channels but does not exfiltrate credentials, establish persistence, or execute arbitrary remote code.
Potential Impact
The impact is unauthorized subscription of the victim's WhatsApp account to attacker-controlled channels, which could lead to unwanted content delivery or spam. There is no credential theft, persistence, or remote code execution involved according to the provided data.
Mitigation Recommendations
No patch or official fix information is provided. Since this is a malicious fork of a third-party library, mitigation involves avoiding use of the affected package versions and sourcing Baileys library code only from trusted, official repositories. Monitor for and remove any installations of @badzz88/baileys versions 8.5.1 through 8.5.9. Patch status is not yet confirmed — check the vendor or repository advisories for current remediation guidance.
Malicious code in @badzz88/baileys (npm)
Description
The @badzz88/baileys npm package, a fork of the Baileys WhatsApp Web library, contains malicious code that silently subscribes the victim's WhatsApp account to attacker-controlled channels without user consent. This is done by injecting a covert FOLLOW query into the WhatsApp socket connection using the installer's authenticated session. The targeted channel IDs are obfuscated or fetched remotely, allowing attackers to change targets post-installation. The malicious code does not steal credentials, maintain persistence, or execute arbitrary 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
This threat involves a family of over 100 near-identical malicious forks of the Baileys WhatsApp Web library, including the @badzz88/baileys package versions 8.5.1 through 8.5.9. These forks inject code that, upon socket connection, issues an authenticated 'w:mex' FOLLOW query to attacker-chosen WhatsApp Channel/Newsletter JIDs using the victim's own authenticated session. The target JIDs are hidden via obfuscation or dynamically fetched from attacker-controlled remote sources, enabling stealthy and flexible subscription to unwanted channels. The malicious action leverages the installer's authenticated WhatsApp session to increase subscribers for attacker channels but does not exfiltrate credentials, establish persistence, or execute arbitrary remote code.
Potential Impact
The impact is unauthorized subscription of the victim's WhatsApp account to attacker-controlled channels, which could lead to unwanted content delivery or spam. There is no credential theft, persistence, or remote code execution involved according to the provided data.
Mitigation Recommendations
No patch or official fix information is provided. Since this is a malicious fork of a third-party library, mitigation involves avoiding use of the affected package versions and sourcing Baileys library code only from trusted, official repositories. Monitor for and remove any installations of @badzz88/baileys versions 8.5.1 through 8.5.9. Patch status is not yet confirmed — check the vendor or repository advisories for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-17341
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6abd30852a4e24523d3401e6
Added to database: 09/30/2026, 15:53:41 UTC
Last enriched: 09/30/2026, 16:08:27 UTC
Last updated: 10/01/2026, 04:47:50 UTC
Views: 5
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.