Malicious code in @teamolduser/baileys (npm)
The @teamolduser/baileys npm package 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 subscription action into the WhatsApp socket layer, which issues an authenticated FOLLOW query using the installer's own WhatsApp session. The target channels are obfuscated or dynamically fetched, allowing attackers to change targets post-installation. The malicious code does not steal credentials, establish persistence, or execute arbitrary code.
AI Analysis
Technical Summary
The @teamolduser/baileys package is part of a large family of over 100 near-identical malicious forks of the Baileys WhatsApp Web library. These forks inject code that hooks into the WhatsApp socket connection and issues an authenticated 'w:mex' FOLLOW query to attacker-chosen WhatsApp Channel/Newsletter JIDs, subscribing the victim's account without their knowledge. The target JIDs are hidden via obfuscation or dynamically fetched from attacker-controlled remote sources. This mechanism leverages the victim's authenticated WhatsApp session to increase subscribers for attacker channels but does not perform credential theft, persistence, or remote code execution. Affected versions include 9.10.1, 9.7.3-beta.1, and 9.7.2.
Potential Impact
Victims unknowingly subscribe their WhatsApp accounts to attacker-controlled channels, potentially exposing them to unwanted content or spam. The attack leverages the victim's authenticated session but does not compromise credentials or allow arbitrary code execution. There is no persistence or direct data exfiltration involved.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing or using the affected versions of the @teamolduser/baileys package (9.10.1, 9.7.3-beta.1, 9.7.2). Review package sources carefully before installation and consider using verified, official Baileys library versions. Monitor for updates from the package maintainers or security advisories for any forthcoming fixes.
Malicious code in @teamolduser/baileys (npm)
Description
The @teamolduser/baileys npm package 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 subscription action into the WhatsApp socket layer, which issues an authenticated FOLLOW query using the installer's own WhatsApp session. The target channels are obfuscated or dynamically fetched, allowing attackers to change targets post-installation. The malicious code does not steal credentials, establish 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 @teamolduser/baileys package is part of a large family of over 100 near-identical malicious forks of the Baileys WhatsApp Web library. These forks inject code that hooks into the WhatsApp socket connection and issues an authenticated 'w:mex' FOLLOW query to attacker-chosen WhatsApp Channel/Newsletter JIDs, subscribing the victim's account without their knowledge. The target JIDs are hidden via obfuscation or dynamically fetched from attacker-controlled remote sources. This mechanism leverages the victim's authenticated WhatsApp session to increase subscribers for attacker channels but does not perform credential theft, persistence, or remote code execution. Affected versions include 9.10.1, 9.7.3-beta.1, and 9.7.2.
Potential Impact
Victims unknowingly subscribe their WhatsApp accounts to attacker-controlled channels, potentially exposing them to unwanted content or spam. The attack leverages the victim's authenticated session but does not compromise credentials or allow arbitrary code execution. There is no persistence or direct data exfiltration involved.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing or using the affected versions of the @teamolduser/baileys package (9.10.1, 9.7.3-beta.1, 9.7.2). Review package sources carefully before installation and consider using verified, official Baileys library versions. Monitor for updates from the package maintainers or security advisories for any forthcoming fixes.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-17380
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6abd30852a4e24523d340148
Added to database: 09/30/2026, 15:53:41 UTC
Last enriched: 09/30/2026, 16:03:40 UTC
Last updated: 09/30/2026, 22:39:12 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.