kevinx-baileys 1.2.0 to 1.2.2 makes a WhatsApp bot's account follow four channels without telling the user.
kevinx-baileys is a copy of Baileys, a popular library for WhatsApp bots. GitHub and OpenSSF mark versions 1.2.0 to 1.2.2 as malware, and npm no longer serves them.
What happened
The package is a fork of the Baileys WhatsApp library with a hidden channel-follow step in lib/Socket/newsletter.js.
- That file holds four WhatsApp channel IDs as base64 text.
- When the socket connects, the code sends the WhatsApp w:mex FOLLOW query for those channels with the bot's own session and without telling the user.
- The package README said "Nothing is followed unless you call it."
- Version 1.2.1 shipped one directory down under a broken
package.jsonwhoseindex.jsdoes not exist. Version 1.2.2 restored the normal layout with the same file. - CyberXYZ found the package. OpenSSF published it as MAL-2026-18688, and GitHub published advisory GHSA-m4p3-qr69-gqjp on 19 November 2026.
npm replaced the package with a security holding package on 19 November 2026. The removed code was unavailable for inspection, so this page follows the OpenSSF record and the registry.
Affected versions
1.2.0appeared on npm at 10:01 UTC on 24 October 2026.1.2.1followed on 30 October and1.2.2on 31 October 2026.- OpenSSF lists all three versions as affected. No fixed version exists.
- npm now serves only
0.0.1-security.
Indicators of compromise
- WhatsApp channels
120363408893555851@newsletter,120363424295522327@newsletter,120363426470081124@newsletterand120363427718144294@newsletter - File
lib/Socket/newsletter.js, SHA-2567db0ac4e599e7acd4b80d5f5092d43488eed474f4f1bce4b315a35e864375d52(OpenSSF) - File
kevinx-baileys/lib/Socket/newsletter.js, SHA-2566368e28be94dd2dc19d8920385b593574ca21298b560108f544371022cf10d07(OpenSSF) - npm package
kevinx-baileys
How to check
List the installed version in each Node.js project.
npm ls kevinx-baileys
npm no longer serves the old versions, so check your lockfile history and CI build logs for an earlier install of 1.2.0 to 1.2.2.
What to do now
- Run
npm uninstall kevinx-baileysin every project. Use the official Baileys package and pin its version in your lockfile. - In WhatsApp on the bot's phone, unfollow every channel that you did not choose.
- In WhatsApp Linked Devices, log out every session that the bot used.
- GitHub says to treat the computer as compromised. From a different computer, rotate the secrets and keys on it.
What Vigilance would show
These examples show an install hold and the corresponding owner report.
Example install message
Vigilance blocked `kevinx-baileys` 1.2.2. This version is too new or changed in a way Vigilance must check first.
Example owner report
Bad update
kevinx-baileys 1.2.2
A copy of a popular WhatsApp library makes each user's WhatsApp account follow four channels the user never chose.
No security team? See who reads the alert.
Frequently asked questions
Is kevinx-baileys safe to use?
No. OpenSSF lists versions 1.2.0 to 1.2.2 as malware, no fixed version exists, and npm no longer serves them.
How do I know if my WhatsApp account was affected?
Open the Updates tab in WhatsApp on the bot's phone. Look for channels that you did not follow.
Is this part of a larger campaign?
OpenSSF says the behavior matches the PhantomSub family of WhatsApp library forks. See /attacks/eleventech-npm-2026.
Sources
Send this page to the person who looks after AI at your company.