npm

The raiden-baileys npm Malware Advisory

Updated 11 Nov 2026 · Incident date 18 Oct 2026

raiden-baileys schedules WhatsApp channel follows. GitHub lists the package as malware, and the inspected code confirms the timer.

GitHub flags raiden-baileys as a trojanized fork of the Baileys WhatsApp library.

We inspected the newsletter timer in releases 2.1.0, 2.1.7 and 2.2.5 inside a locked container.

What happened

The inspected code schedules channel follow requests without a user action.

  • lib/Socket/newsletter.js sets a timer for 120000 milliseconds, or two minutes.
  • The timer passes hardcoded channel IDs to newsletterWMexQuery with Types_1.QueryIds.FOLLOW.
  • The inspected timer lists one channel in 2.1.0 and two in 2.1.7 and 2.2.5.
  • The advisory lists a third channel. That third ID is absent from these inspected timers.

Affected versions

  • GitHub marks all published versions as affected and lists no patched version.
  • npm currently lists 2.2.5 as latest. Its inspected timer still contains the follow requests.

Indicators of compromise

  • 120363407277177688@newsletter, present in all three inspected timers.
  • 120363407702752541@newsletter, present in the inspected 2.1.7 and 2.2.5 timers.
  • 120363411769951302@newsletter, reported by the advisory but absent from these inspected timers.

How to check

List the installed package without executing its code.

npm ls raiden-baileys

What to do now

  1. Remove raiden-baileys from affected projects.
  2. Check connected WhatsApp accounts for unexpected channel follows.
  3. Unfollow unwanted channels and review the bot dependency before reconnecting it.

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 `raiden-baileys` 2.2.5. This version is too new or changed in a way Vigilance must check first.
The last safe version is 2.1.0. Install that version.

In the owner report

Bad update

raiden-baileys 2.2.5

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

  1. Ask the AI tool to swap raiden-baileys to 2.1.0. That is the last safe version.

Sources

  1. github.com/advisories/GHSA-47pm-q564-4v9p
  2. registry.npmjs.org/raiden-baileys
  3. unpkg.com/raiden-baileys@2.1.0/lib/Socket/newsletter.js
  4. unpkg.com/raiden-baileys@2.1.7/lib/Socket/newsletter.js
  5. unpkg.com/raiden-baileys@2.2.5/lib/Socket/newsletter.js

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