npm

The shadowmd-baileys npm Supply Chain Attack

Updated 16 Nov 2026 · Incident date 14 May 2026

OpenSSF reports that shadowmd-baileys 8.6.49 to 8.6.91 on npm make the user's WhatsApp account follow two channels that the publisher chose.

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

What happened

OpenSSF record MAL-2026-19014 describes the behavior below. CyberXYZ found the package.

  • Code in lib/Socket/newsletter.js sends a w:mex FOLLOW query.
  • The query follows channels 120363407277177688@newsletter and 120363423975826201@newsletter on the user's WhatsApp account.
  • OpenSSF says the behavior matches the PhantomSub family, MAL-2026-17342.
  • GitHub published advisory GHSA-jq2q-8r58-q95r for all versions on 16 November 2026.
  • npm replaced the package with a security placeholder the same day.

The registry shows 8.6.49 on 14 May 2026 and 8.6.91 on 24 September 2026. npm counts 4,352 downloads from May to 15 November 2026.

Affected versions

  • OpenSSF lists 11 versions, from 8.6.49 to 8.6.91.
  • GitHub marks every version as malware.
  • No fixed version exists.

Indicators of compromise

  • lib/Socket/newsletter.js SHA-256 00b41803431829dc6603059e281f6b5ed2bb11336d2d3a7f2ea0cf714b5ed073
  • lib/Socket/newsletter.js SHA-256 10e94f54201bdedee0c520757880de161c85690a43205db0ced02a4e39e74b2b
  • Channel 120363407277177688@newsletter
  • Channel 120363423975826201@newsletter

How to check

List the installed version in each Node.js project.

npm ls shadowmd-baileys

Search the installed files for the channel IDs.

grep -rlE "120363407277177688|120363423975826201" node_modules

What to do now

  1. Run npm uninstall shadowmd-baileys in every project.
  2. In WhatsApp, unfollow every channel that you did not choose.
  3. In WhatsApp Linked Devices, log out every session that the bot used.
  4. From a clean computer, rotate the secrets on the affected machine, as the GitHub advisory says.

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 `shadowmd-baileys` 8.6.49. This version is too new or changed in a way Vigilance must check first.

In the owner report

Bad update

shadowmd-baileys 8.6.49

This update now downloads from the internet and runs other programs. The version before it did not.

Frequently asked questions

Is shadowmd-baileys safe to use?

No. GitHub and OpenSSF flag the package as malware, and npm removed it on 16 November 2026.

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.

Sources

  1. github.com/advisories/GHSA-jq2q-8r58-q95r
  2. osv.dev/vulnerability/MAL-2026-19014
  3. raw.githubusercontent.com/ossf/malicious-packages/main/osv/malicious/npm/shadowmd-baileys/MAL-2026-19014.json
  4. registry.npmjs.org/shadowmd-baileys

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