Malicious code in bungoma (npm)
The npm package 'bungoma' versions 1.0.1 and 1.1.0 is part of a family of malicious forks of the Baileys WhatsApp Web library. These forks inject code that silently subscribes the victim's authenticated WhatsApp account to attacker-controlled channels without user consent. The target channels are obfuscated or dynamically fetched, allowing attackers to change targets post-installation. The malicious code abuses the installer's authenticated session but does not steal credentials, maintain persistence, or execute arbitrary code.
AI Analysis
Technical Summary
The 'bungoma' npm package (versions 1.0.1 and 1.1.0) belongs to a large family of over 100 near-identical malicious forks of the Baileys WhatsApp Web library. These forks inject a covert subscription action into the WhatsApp socket layer, issuing 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 techniques or dynamically fetched from attacker-controlled remote sources, enabling stealthy and flexible subscription to unwanted channels. The injected code activates shortly after the socket connection is established. This behavior does not involve credential theft, persistence mechanisms, or arbitrary code execution.
Potential Impact
The malicious package causes the victim's WhatsApp account to be silently subscribed to attacker-controlled channels, potentially exposing the user to unwanted content or spam. It leverages the victim's authenticated session to perform these actions without their knowledge or consent. However, it does not compromise user credentials, establish persistence on the system, or allow remote code execution.
Mitigation Recommendations
No official patch or remediation guidance is provided in the available data. Users should avoid installing or using the affected 'bungoma' package versions 1.0.1 and 1.1.0. Since no patch is confirmed, users should monitor for vendor advisories for updates. Removing the malicious package and revoking WhatsApp session tokens may help mitigate the impact.
Malicious code in bungoma (npm)
Description
The npm package 'bungoma' versions 1.0.1 and 1.1.0 is part of a family of malicious forks of the Baileys WhatsApp Web library. These forks inject code that silently subscribes the victim's authenticated WhatsApp account to attacker-controlled channels without user consent. The target channels are obfuscated or dynamically fetched, allowing attackers to change targets post-installation. The malicious code abuses the installer's authenticated session but 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
The 'bungoma' npm package (versions 1.0.1 and 1.1.0) belongs to a large family of over 100 near-identical malicious forks of the Baileys WhatsApp Web library. These forks inject a covert subscription action into the WhatsApp socket layer, issuing 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 techniques or dynamically fetched from attacker-controlled remote sources, enabling stealthy and flexible subscription to unwanted channels. The injected code activates shortly after the socket connection is established. This behavior does not involve credential theft, persistence mechanisms, or arbitrary code execution.
Potential Impact
The malicious package causes the victim's WhatsApp account to be silently subscribed to attacker-controlled channels, potentially exposing the user to unwanted content or spam. It leverages the victim's authenticated session to perform these actions without their knowledge or consent. However, it does not compromise user credentials, establish persistence on the system, or allow remote code execution.
Mitigation Recommendations
No official patch or remediation guidance is provided in the available data. Users should avoid installing or using the affected 'bungoma' package versions 1.0.1 and 1.1.0. Since no patch is confirmed, users should monitor for vendor advisories for updates. Removing the malicious package and revoking WhatsApp session tokens may help mitigate the impact.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-17389
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6abd30852a4e24523d340129
Added to database: 09/30/2026, 15:53:41 UTC
Last enriched: 09/30/2026, 16:02:33 UTC
Last updated: 09/30/2026, 22:42:19 UTC
Views: 2
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.