Malicious code in lilys-baileys (npm)
The npm package lilys-baileys (versions 1.3.2 and 1.3.3) is part of a large 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 malicious code uses obfuscation techniques to hide the target channel identifiers and may fetch dynamic target lists from remote hosts. The attack leverages the installer's own authenticated WhatsApp session but does not steal credentials, maintain persistence, or execute arbitrary code.
AI Analysis
Technical Summary
The lilys-baileys npm package versions 1.3.2 and 1.3.3 contain malicious code that hooks into the WhatsApp socket connection process. Upon connection, it issues an authenticated 'w:mex' FOLLOW query to subscribe the victim's WhatsApp account to attacker-chosen channels or newsletters. The target channel JIDs are obfuscated using methods such as base64 encoding, XOR, or runtime reconstruction, and some variants retrieve the target list dynamically from attacker-controlled remote sources. This covert subscription mechanism abuses the victim's authenticated session to increase subscribers for attacker channels without exfiltrating credentials or executing arbitrary remote code.
Potential Impact
Victims unknowingly subscribe their WhatsApp accounts to attacker-controlled channels, potentially exposing them to unwanted content or spam. The attack does not compromise account credentials, establish persistence, or allow arbitrary code execution, limiting its impact to unauthorized channel subscriptions.
Mitigation Recommendations
No official patch or remediation guidance is provided. Users should avoid installing or using the lilys-baileys package versions 1.3.2 and 1.3.3. Since this is a malicious package distributed via npm, verifying package authenticity and using trusted sources is recommended. Patch status is not yet confirmed — check the vendor advisory or npm security advisories for current remediation guidance.
Malicious code in lilys-baileys (npm)
Description
The npm package lilys-baileys (versions 1.3.2 and 1.3.3) is part of a large 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 malicious code uses obfuscation techniques to hide the target channel identifiers and may fetch dynamic target lists from remote hosts. The attack leverages the installer's own authenticated WhatsApp 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 lilys-baileys npm package versions 1.3.2 and 1.3.3 contain malicious code that hooks into the WhatsApp socket connection process. Upon connection, it issues an authenticated 'w:mex' FOLLOW query to subscribe the victim's WhatsApp account to attacker-chosen channels or newsletters. The target channel JIDs are obfuscated using methods such as base64 encoding, XOR, or runtime reconstruction, and some variants retrieve the target list dynamically from attacker-controlled remote sources. This covert subscription mechanism abuses the victim's authenticated session to increase subscribers for attacker channels without exfiltrating credentials or executing arbitrary remote code.
Potential Impact
Victims unknowingly subscribe their WhatsApp accounts to attacker-controlled channels, potentially exposing them to unwanted content or spam. The attack does not compromise account credentials, establish persistence, or allow arbitrary code execution, limiting its impact to unauthorized channel subscriptions.
Mitigation Recommendations
No official patch or remediation guidance is provided. Users should avoid installing or using the lilys-baileys package versions 1.3.2 and 1.3.3. Since this is a malicious package distributed via npm, verifying package authenticity and using trusted sources is recommended. Patch status is not yet confirmed — check the vendor advisory or npm security advisories for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-17398
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6abd30852a4e24523d340120
Added to database: 09/30/2026, 15:53:41 UTC
Last enriched: 09/30/2026, 16:01:29 UTC
Last updated: 09/30/2026, 22:40:42 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.