npm

The sauruspro-bail npm Supply Chain Attack

Updated 10 Nov 2026 · Incident date 31 Oct 2026

From version 5.0.0, sauruspro-bail makes the bot's WhatsApp account follow channels that a hidden server picks.

sauruspro-bail is a copy of Baileys, a popular library for WhatsApp bots. From version 5.0.0, it makes the bot's WhatsApp account follow channels that the user never chose.

What happened

The npm account kingsaurus published version 5.0.0 on 31 October 2026.

  • Ten seconds after the bot connects to WhatsApp, the code downloads a channel list from push-saurus.yorunime.sbs.
  • The code hides that address as base64 text in lib/Socket/newsletter.js.
  • The code then follows each channel on the list, one every five seconds. It hides every error, so the user sees nothing.
  • The list lives on the server. The server owner can change the channels at any time.
  • wormsign found the package. OpenSSF published it as MAL-2026-19073 on 3 November 2026. GitHub copied it as GHSA-7j35-x788-5m8x on 10 November.

OpenSSF and GitHub say the code follows two fixed channels. In the code, those two channel IDs only label sent messages as forwarded from a channel. wormsign's own page lists the server address.

Affected versions

  • 5.0.0, 5.0.1, 5.0.2-alpha.spr.test, 5.0.2, 5.0.3 and 5.3.1 hold the code. 5.3.1 came out on 10 November 2026.
  • The first upload, 0.0.0-stage, does not hold it.
  • GitHub marks every version as malware. OpenSSF names 0.0.0-stage, 5.0.0, 5.0.1 and 5.0.2-alpha.spr.test.

Indicators of compromise

  • Domain push-saurus.yorunime.sbs
  • Text aHR0cHM6Ly9wdXNoLXNhdXJ1cy55b3J1bmltZS5zYnMvaWRjaC5qc29u in lib/Socket/newsletter.js
  • WhatsApp channels 120363418964199743@newsletter and 120363429190136593@newsletter (named by OpenSSF)
  • npm package sauruspro-bail from account kingsaurus

How to check

List the installed version in each Node.js project.

npm ls sauruspro-bail

Search the installed files for the hidden address.

grep -rl "aHR0cHM6Ly9wdXNoLXNhdXJ1cy" node_modules

What to do now

  1. Run npm uninstall sauruspro-bail in every project. Use the official Baileys package and pin the version in your lockfile.
  2. Block push-saurus.yorunime.sbs on the bot's network.
  3. In WhatsApp, unfollow every channel that you did not choose.
  4. In WhatsApp Linked Devices, log out every session that the bot used.

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 `sauruspro-bail` 5.0.0. This version is too new or changed in a way Vigilance must check first.
The last safe version is 0.0.0-stage. Install that version.

In the owner report

Bad update

sauruspro-bail 5.0.0

This update now downloads from the internet. The version before it did not.

  1. Ask the AI tool to swap sauruspro-bail to 0.0.0-stage. That is the last safe version.

Frequently asked questions

Is sauruspro-bail safe to use?

No. Every version from 5.0.0 follows channels from a hidden server list, and no fixed version exists.

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.

Do other Baileys copies do this?

Yes. In September 2026, The Hacker News reported OX Security's find of 101 npm packages that add WhatsApp accounts to channels or groups.

Sources

  1. github.com/advisories/GHSA-7j35-x788-5m8x
  2. osv.dev/vulnerability/MAL-2026-19073
  3. wormsign.io/portfolio/sauruspro-bail/
  4. thehackernews.com/2026/09/101-malicious-npm-packages-add.html
  5. unpkg.com/sauruspro-bail@5.3.1/lib/Socket/newsletter.js
  6. registry.npmjs.org/sauruspro-bail

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