npm

The spencer-baileys npm Supply Chain Attack

Updated 20 Nov 2026 · Incident date 15 Nov 2026

Version 1.0.6 of the spencer-baileys npm package silently joined WhatsApp groups and followed channels on the connected account.

The package mimics the Baileys WhatsApp library for Node. npm has since removed the whole project. Any computer or server that connected a WhatsApp socket through version 1.0.6 was exposed.

What happened

Version 1.0.6 added code inside lib/Socket/newsletter.js that acted on the user's WhatsApp account without asking.

  • It base64-decoded a hidden address and fetched a list from savage-prox.onrender.com.
  • It joined every WhatsApp group in that list with groupAcceptInvite.
  • It followed every WhatsApp channel in the list with a follow query.
  • The code ran 90 seconds after a connection opened, then every 3 hours, with all errors hidden.

Vigilance caught version 1.0.6 at 11:27 UTC on 15 November 2026, 1 minute 4 seconds after it appeared on npm.

Affected versions

  • 1.0.6, published 11:26 UTC on 15 November 2026, carried the hidden-join code.
  • 1.0.5 was the last clean release in the comparison record.
  • npm has removed every version of the package.

Indicators of compromise

  • A WhatsApp socket created with spencer-baileys 1.0.6, in lib/Socket/newsletter.js.
  • Requests to savage-prox.onrender.com/api/v1/links.
  • Unexpected group memberships or channel subscriptions on the connected WhatsApp account.

How to check

Use a shell outside the affected project. Run it in the folder that holds your lockfile.

npm ls spencer-baileys

If the package is already gone from your project, check your CI build logs and lockfile history for version 1.0.6. npm removed the package, so a clean install today cannot rule out earlier exposure.

What to do now

  1. Remove spencer-baileys 1.0.6 and rebuild the project from a clean lockfile.
  2. Check the connected WhatsApp account for unexpected groups and channels, and leave any you did not join.
  3. Review the contacts, chats and files the session shared, and rotate any credentials it shared.

What Vigilance would show

These examples show an install hold and the corresponding owner report.

Example install message

Vigilance blocked `spencer-baileys` 1.0.6. This version is too new or changed in a way Vigilance must check first.

Example owner report

Bad update

spencer-baileys 1.0.6

Acts on the connected WhatsApp account on a timer, following lists fetched from the attacker's server.

See what to do now.

No security team? See who reads the alert.

Frequently asked questions

What did the hidden code do?

It fetched a list from savage-prox.onrender.com, joined every WhatsApp group on it, and followed every channel on it, repeating every 3 hours.

Which versions are affected?

Version 1.0.6. The comparison record shows 1.0.5 without this code, and npm has removed the whole project.

Is the package still on npm?

No. npm has removed every version of spencer-baileys.

Sources

  1. github.com/Dragon-Lady/supply-chain-check/blob/08181e6ae53305d8ae122f2ff1cbbdb78ad43ae0/data/packages/npm.json
  2. registry.npmjs.org/spencer-baileys

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