@sakataa/baileys on npm made each user's WhatsApp account follow four WhatsApp channels that the publisher picked, according to GitHub and OpenSSF.
The package is a fork of Baileys, a WhatsApp Web library for Node.js. GitHub classes every version as malware.
What happened
OpenSSF record MAL-2026-18681 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 four channel IDs. - The file stores the IDs base64-encoded.
- The query uses the user's own WhatsApp session and does not tell the user.
CyberXYZ is the credited finder. The record links the behaviour to the PhantomSub family, MAL-2026-17342. npm replaced the package with a security holding package on 16 November 2026, so we did not inspect the code.
Affected versions
- OpenSSF and GitHub advisory GHSA-v2gw-xwwr-5v2c name
1.0.0,2.0.0and3.0.0. - GitHub advisory GHSA-8868-q7gh-f9jf covers all versions (
>= 0). - npm also lists
4.0.0to5.0.1, published from 9 to 16 November 2026. No source describes their code.
Indicators of compromise
120363408893555851@newsletter120363424295522327@newsletter120363426470081124@newsletter120363427718144294@newsletterlib/Socket/newsletter.jssha2567db0ac4e599e7acd4b80d5f5092d43488eed474f4f1bce4b315a35e864375d52lib/Socket/newsletter.jssha25647f9c2471cbe7d15331c6599b2319693e4a6d65f522318aa68b6bbf8fe5ac92b
How to check
Run this command in each project folder. It only reads the dependency tree.
npm ls @sakataa/baileys
In WhatsApp, open the Updates tab. Look for channels that you did not choose to follow.
What to do now
- Remove
@sakataa/baileysfrom every project and lockfile. - In WhatsApp, unfollow each channel that you did not choose.
- In WhatsApp Linked Devices, log out every session that the bot used.
- GitHub advises that you treat the computer as compromised. From a different computer, rotate its secrets and keys.
What Vigilance would show
Vigilance checks each update before it installs. This is what a customer sees, rebuilt from the facts on this page.
On the computer, at install
Vigilance blocked `@sakataa/baileys` 1.0.0. This version is too new or changed in a way Vigilance must check first.
In the owner report
Bad update
@sakataa/baileys 1.0.0
This update now downloads from the internet and runs other programs. The version before it did not.
Frequently asked questions
Is @sakataa/baileys malware?
Yes. GitHub advisories GHSA-v2gw-xwwr-5v2c and GHSA-8868-q7gh-f9jf class it as malware under CWE-506.
Is @sakataa/baileys part of PhantomSub?
OpenSSF record MAL-2026-18681 describes the same behaviour as the PhantomSub family, MAL-2026-17342.