Malicious code in @fhkryxv/baileys (npm)
The npm package @fhkryxv/baileys versions 1.0.1 and 1.0.3 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 channel-subscription action into the WhatsApp socket layer, issuing an authenticated FOLLOW query using the installer's own WhatsApp session. The target channels are obfuscated or dynamically fetched to evade detection. The malicious code does not steal credentials, maintain persistence, or execute arbitrary remote code.
AI Analysis
Technical Summary
The @fhkryxv/baileys npm package, a fork of the Baileys WhatsApp Web library, contains injected code that, upon connection, issues an authenticated 'w:mex' FOLLOW query to attacker-chosen WhatsApp Channel/Newsletter JIDs. This causes the victim's WhatsApp account to subscribe silently to these channels. The target JIDs are obfuscated using various methods or fetched dynamically from attacker-controlled hosts, allowing the subscription targets to change post-installation. The attack leverages the installer's authenticated WhatsApp session but does not exfiltrate credentials or execute arbitrary code. Affected versions are 1.0.1 and 1.0.3.
Potential Impact
Victims unknowingly subscribe their WhatsApp accounts to attacker-controlled channels, potentially exposing them to unwanted content or spam. The attack abuses the victim's authenticated session but does not compromise credentials or enable remote code execution. There is no persistence or direct data exfiltration involved.
Mitigation Recommendations
No official patch or remediation is indicated in the provided data. Users should avoid installing or using the affected package versions 1.0.1 and 1.0.3 of @fhkryxv/baileys. Review and verify the integrity of npm packages before installation. Monitor for updates or advisories from the package maintainers or npm registry for remediation guidance.
Malicious code in @fhkryxv/baileys (npm)
Description
The npm package @fhkryxv/baileys versions 1.0.1 and 1.0.3 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 channel-subscription action into the WhatsApp socket layer, issuing an authenticated FOLLOW query using the installer's own WhatsApp session. The target channels are obfuscated or dynamically fetched to evade detection. The malicious code does not steal credentials, maintain 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 @fhkryxv/baileys npm package, a fork of the Baileys WhatsApp Web library, contains injected code that, upon connection, issues an authenticated 'w:mex' FOLLOW query to attacker-chosen WhatsApp Channel/Newsletter JIDs. This causes the victim's WhatsApp account to subscribe silently to these channels. The target JIDs are obfuscated using various methods or fetched dynamically from attacker-controlled hosts, allowing the subscription targets to change post-installation. The attack leverages the installer's authenticated WhatsApp session but does not exfiltrate credentials or execute arbitrary code. Affected versions are 1.0.1 and 1.0.3.
Potential Impact
Victims unknowingly subscribe their WhatsApp accounts to attacker-controlled channels, potentially exposing them to unwanted content or spam. The attack abuses the victim's authenticated session but does not compromise credentials or enable remote code execution. There is no persistence or direct data exfiltration involved.
Mitigation Recommendations
No official patch or remediation is indicated in the provided data. Users should avoid installing or using the affected package versions 1.0.1 and 1.0.3 of @fhkryxv/baileys. Review and verify the integrity of npm packages before installation. Monitor for updates or advisories from the package maintainers or npm registry for remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-17352
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6abd30852a4e24523d3401b8
Added to database: 09/30/2026, 15:53:41 UTC
Last enriched: 09/30/2026, 16:07:08 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.