npm

The @wanzforme/bails npm Supply Chain Attack

Updated 19 Nov 2026 · Incident date 25 Oct 2026

@wanzforme/bails makes a WhatsApp bot's account follow a hidden channel, and its install step runs code from a mutable GitHub repo.

@wanzforme/bails is a copy of Baileys, a popular library for WhatsApp bots. GitHub and OpenSSF mark versions 1.0.0 to 7.0.0 as malware, and npm no longer serves them.

What happened

The package is a fork of the Baileys WhatsApp library. Two sources describe what it does.

  • OpenSSF says the code in lib/Socket/newsletter.js holds one WhatsApp channel ID as base64 text. When the socket connects, it sends the WhatsApp w:mex FOLLOW query for that channel with the bot's own session and does not tell the user.
  • Amazon Inspector reports that package.json declares "libsignal": "github:wanzchil/libsignal-node". npm then fetches the current HEAD of that GitHub repository and runs any lifecycle scripts on the installer's computer.
  • The repo has no tag, commit SHA or integrity hash, so its owner can change the bytes that npm runs at any time.
  • Amazon Inspector also notes that a static rule matched the tokens ping and GET in lib/Utils/generics.js, and that these appear in ordinary utility code.
  • CyberXYZ and Amazon Inspector found the package. OpenSSF published it as MAL-2026-18682, and GitHub published advisory GHSA-wpq7-r76p-73cp 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.0.0 appeared on npm at 12:07 UTC on 25 October 2026 and 2.0.0 the same day.
  • Versions 3.0.0 to 7.0.0 followed on 14 November 2026.
  • OpenSSF lists versions 1.0.0 to 7.0.0 as affected. No fixed version exists.
  • npm now serves only 0.0.1-security.

Indicators of compromise

  • WhatsApp channel 120363380357951328@newsletter
  • File lib/Socket/newsletter.js, SHA-256 8b1a056c480482cced3274cd351fbc3b910616fb907e63b6705928405c20c0e7 (OpenSSF)
  • Dependency github:wanzchil/libsignal-node in package.json (Amazon Inspector)
  • npm package @wanzforme/bails

How to check

List the installed version in each Node.js project.

npm ls @wanzforme/bails

npm no longer serves the old versions, so check your lockfile history and CI build logs for an earlier install of 1.0.0 to 7.0.0.

What to do now

  1. Run npm uninstall @wanzforme/bails in every project. Use the official Baileys package and pin its version in your lockfile.
  2. In WhatsApp on the bot's phone, unfollow every channel that you did not choose.
  3. In WhatsApp Linked Devices, log out every session that the bot used.
  4. 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 `@wanzforme/bails` 7.0.0. This version is too new or changed in a way Vigilance must check first.

Example owner report

Bad update

@wanzforme/bails 7.0.0

A copy of a popular WhatsApp library makes each user's WhatsApp account follow a channel the user never chose, and its install step runs code from a mutable GitHub repository.

See what to do now.

No security team? See who reads the alert.

Frequently asked questions

Is @wanzforme/bails safe to use?

No. OpenSSF lists versions 1.0.0 to 7.0.0 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.

Why does the GitHub libsignal dependency matter?

Amazon Inspector reports that npm pulled libsignal from the current HEAD of a GitHub repository with no tag or integrity hash. The repository owner can change that code at any time.

Sources

  1. github.com/advisories/GHSA-wpq7-r76p-73cp
  2. osv.dev/vulnerability/MAL-2026-18682
  3. registry.npmjs.org/@wanzforme%2Fbails

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 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