The npm package @poucode/baileys used the installer's WhatsApp session to follow channels the publisher chose, without telling the user.
The package is a fork of the Baileys WhatsApp Web library. npm holds the name and now serves a security holding package.
What happened
OpenSSF record MAL-2026-18873 describes a hidden channel-follow action in the fork.
- Code in
lib/Socket/newsletter.jsruns when the WhatsApp socket connects. - It sends the WhatsApp
w:mexFOLLOW query for channel IDs120363429394939370@newsletterand120363430414713911@newsletter. - The query uses the user's own authenticated session and does not tell the user.
- OpenSSF links the behavior to the PhantomSub family, MAL-2026-17342. CyberXYZ is the credited finder.
- npm replaced the package with the placeholder
0.0.1-securityon 19 November 2026, so the code was unavailable for inspection.
Affected versions
- The OpenSSF record lists
1.0.0, published 11 October 2026 at 17:59 UTC. - The GitHub advisory range is
>= 0and lists no fixed version. - The registry timeline also shows
1.0.1,1.0.2,2.0.0,2.0.1and2.0.4, released 13 to 17 November 2026. The registry no longer serves any of them. 0.0.1-securityis the registry holding package, not a restored original release.
Indicators of compromise
- FOLLOW targets:
120363429394939370@newsletterand120363430414713911@newsletter. - OpenSSF lists
lib/Socket/newsletter.jswith SHA-256cde7d68f4e593e2d38f98918d5e671670f5242b1baf153523d48ad18fba67530.
How to check
Check your project dependency tree for the package. This command reads installed metadata and does not run the package.
npm ls @poucode/baileys
Check your CI build logs and lockfile history for the affected versions. The registry no longer serves them, so a clean install today cannot rule out earlier exposure.
What to do now
- Remove the package from every project that uses it.
- Check the followed-channels list on the affected WhatsApp account and unfollow the two channel IDs.
- From a clean machine, rotate secrets and keys stored on the affected machine.
- Treat a machine that installed or ran an affected release as compromised, as the GitHub advisory advises.
What Vigilance would show
These examples show an install hold and the corresponding owner report.
Example install message
Vigilance blocked `@poucode/baileys` 1.0.0. This version is too new or changed in a way Vigilance must check first.
Example owner report
Bad update
@poucode/baileys 1.0.0
The npm package @poucode/baileys used the installer's WhatsApp session to follow channels the publisher chose, without telling the user.
No security team? See who reads the alert.
Frequently asked questions
What did the malicious code do?
The OpenSSF record says it followed two WhatsApp channels with the user's own session and hid the action. The removed releases were unavailable for code inspection, so this page reports the advisory findings.
Does npm still serve the package?
No. npm holds the name and serves only the placeholder 0.0.1-security. Every original release is gone from the registry.
Is the real Baileys library affected?
The OpenSSF record describes @poucode/baileys as a fork. Other Baileys forks appear in their own records, including @sakataa/baileys and @shadowmd/baileys.
Sources
Send this page to the person who looks after AI at your company.