Malicious code in @bellaxchuu/teambails (npm)
The npm package @bellaxchuu/teambails contains malicious code that silently subscribes the victim's authenticated WhatsApp account to attacker-controlled channels without user consent. This is achieved by injecting a covert subscription action into the WhatsApp socket layer, issuing an authenticated FOLLOW query to attacker-chosen WhatsApp Channel/Newsletter JIDs. The targeted JIDs are obfuscated or dynamically fetched to evade detection. The malicious code does not exfiltrate credentials, establish persistence, or execute arbitrary remote code.
AI Analysis
Technical Summary
The @bellaxchuu/teambails npm package, part of a large family of near-identical Baileys WhatsApp Web library forks, injects a covert channel-subscription action into the WhatsApp socket layer. Upon connection, it issues an authenticated 'w:mex' FOLLOW query using the installer's authenticated WhatsApp session to silently subscribe the victim's account to attacker-controlled channels. The targeted JIDs are hidden via obfuscation or dynamically fetched from attacker-controlled remote sources, allowing the target list to change post-installation. The malicious behavior is consistent across multiple package versions and variants, but it does not involve credential theft, persistence, or remote code execution.
Potential Impact
The impact is unauthorized subscription of the victim's WhatsApp account to attacker-controlled channels, potentially leading to unwanted messages or spam. There is no credential theft, no persistence mechanism, and no arbitrary code execution involved. The attack leverages the victim's authenticated session to extend the attacker's reach within WhatsApp.
Mitigation Recommendations
No patch or official fix information is provided. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should avoid installing or using the affected package versions. Review and audit dependencies for malicious forks. Consider revoking and re-authenticating WhatsApp sessions if suspicious activity is detected.
Malicious code in @bellaxchuu/teambails (npm)
Description
The npm package @bellaxchuu/teambails contains malicious code that silently subscribes the victim's authenticated WhatsApp account to attacker-controlled channels without user consent. This is achieved by injecting a covert subscription action into the WhatsApp socket layer, issuing an authenticated FOLLOW query to attacker-chosen WhatsApp Channel/Newsletter JIDs. The targeted JIDs are obfuscated or dynamically fetched to evade detection. The malicious code 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 @bellaxchuu/teambails npm package, part of a large family of near-identical Baileys WhatsApp Web library forks, injects a covert channel-subscription action into the WhatsApp socket layer. Upon connection, it issues an authenticated 'w:mex' FOLLOW query using the installer's authenticated WhatsApp session to silently subscribe the victim's account to attacker-controlled channels. The targeted JIDs are hidden via obfuscation or dynamically fetched from attacker-controlled remote sources, allowing the target list to change post-installation. The malicious behavior is consistent across multiple package versions and variants, but it does not involve credential theft, persistence, or remote code execution.
Potential Impact
The impact is unauthorized subscription of the victim's WhatsApp account to attacker-controlled channels, potentially leading to unwanted messages or spam. There is no credential theft, no persistence mechanism, and no arbitrary code execution involved. The attack leverages the victim's authenticated session to extend the attacker's reach within WhatsApp.
Mitigation Recommendations
No patch or official fix information is provided. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should avoid installing or using the affected package versions. Review and audit dependencies for malicious forks. Consider revoking and re-authenticating WhatsApp sessions if suspicious activity is detected.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-17348
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6abd30852a4e24523d3401bc
Added to database: 09/30/2026, 15:53:41 UTC
Last enriched: 09/30/2026, 16:07:39 UTC
Last updated: 10/01/2026, 04:47:50 UTC
Views: 6
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.