npm

The @ubedsockets/baileys npm Supply Chain Attack

Updated 16 Nov 2026 · Incident date 15 Apr 2026

Every version of @ubedsockets/baileys on npm, 1.0.0 to 1.7.12, made the user's WhatsApp account follow two channels without consent, according to OpenSSF.

The package is a fork of Baileys, a WhatsApp Web library for Node.js. npm removed it on 16 November 2026, so the code was unavailable for inspection.

What happened

OpenSSF record MAL-2026-18600 describes these actions in the fork:

  • When the WhatsApp socket connects, the code sends a w:mex newsletter FOLLOW request.
  • The request makes the user follow two hardcoded WhatsApp channels, without notice to the user.
  • Amazon Inspector reports that package.json pulls the libsignal dependency from github:rexxzyid/libsignal-node with no pinned commit or version.
  • Amazon Inspector also reports that verifyIP() calls api.ipify.org and exits unless the IP address matches one of two hardcoded addresses.

wormsign and Amazon Inspector are the credited finders. OpenSSF published the record on 13 November 2026. GitHub published advisory GHSA-c2qr-82xm-x8m4 on 16 November 2026.

Affected versions

  • OpenSSF and GitHub list every version as malicious (>= 0), with no fixed version.
  • OpenSSF names 26 versions, from 1.0.0 (15 April 2026) to 1.7.12 (1 November 2026).
  • npm replaced the package with 0.0.1-security on 16 November 2026.

Indicators of compromise

  • Dependency source: github:rexxzyid/libsignal-node.
  • package.json sha256 (OpenSSF): 302a9434f15e8af33afc2fa623c2a14cf72e705eb14264194bc66eb529ab9d38.
  • baileys-1.7.12.tgz sha1 (OpenSSF): efc8c1fe53a2d8fec57bb6847e3c7960e0a9860c.

How to check

Run this command in each project folder. It only reads the dependency tree.

npm ls @ubedsockets/baileys

In WhatsApp, open the Updates tab. Look for channels that you did not choose to follow.

What to do now

  1. Remove @ubedsockets/baileys from every project and lockfile.
  2. In WhatsApp, unfollow each channel that you did not choose.
  3. In WhatsApp Linked Devices, log out every session that the bot used.
  4. 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 `@ubedsockets/baileys` 1.0.0. This version is too new or changed in a way Vigilance must check first.

In the owner report

Bad update

@ubedsockets/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 @ubedsockets/baileys malware?

GitHub advisory GHSA-c2qr-82xm-x8m4 and OpenSSF record MAL-2026-18600 class every version as malware under CWE-506.

Does the official Baileys library do this?

OpenSSF states that the legitimate Baileys library does not send this channel FOLLOW request.

Sources

  1. github.com/advisories/GHSA-c2qr-82xm-x8m4
  2. raw.githubusercontent.com/ossf/malicious-packages/main/osv/malicious/npm/@ubedsockets/baileys/MAL-2026-18600.json
  3. registry.npmjs.org/@ubedsockets%2Fbaileys

More supply chain attacks

All 145 attacks in the library · npm supply chain attacks · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library