npm

The @bellaxchan/eleventech npm Supply Chain Attack

Updated 16 Nov 2026 · Incident date 10 Oct 2026

@bellaxchan/eleventech 0.0.8 makes the bot's WhatsApp account follow a fixed WhatsApp channel without telling the user.

@bellaxchan/eleventech is a copy of Baileys, a popular library for WhatsApp bots. Version 0.0.8 makes the bot's WhatsApp account follow a channel that the user never chose.

What happened

The npm account bellaxchan published version 0.0.8 on 10 October 2026.

  • The code in lib/Socket/newsletter.js holds one channel ID as base64 text.
  • Ten seconds after the bot starts its WhatsApp connection, the code decodes the ID and sends a FOLLOW query for 120363431475943819@newsletter.
  • The query uses the bot's own WhatsApp session. The code hides every error, so the user sees nothing.
  • CyberXYZ found the package. OpenSSF published it as MAL-2026-18672 on 26 October 2026. GitHub copied it as GHSA-xfxr-27rj-f57f on 5 November.

GitHub and OpenSSF say the code matches the PhantomSub family, MAL-2026-17342. The facts above come from the code of 0.0.8, the only full release.

Affected versions

  • 0.0.8 holds the code. It was still the latest version on npm on 16 November 2026.
  • The first upload, 0.0.0-stage, is an empty placeholder.
  • No fixed version exists.

Indicators of compromise

  • WhatsApp channel 120363431475943819@newsletter
  • Text MTIwMzYzNDMxNDc1OTQzODE5QG5ld3NsZXR0ZXI= in lib/Socket/newsletter.js
  • File SHA-256 ae7bbc8bd28e121e1f66b7619c71feed12e138f80fb195944e7a4ebd3efe13e8 (OpenSSF)
  • npm package @bellaxchan/eleventech from account bellaxchan

How to check

List the installed version in each Node.js project.

npm ls @bellaxchan/eleventech

Search the installed files for the hidden channel ID.

grep -rl "MTIwMzYzNDMxNDc1OTQzODE5" node_modules

What to do now

  1. Run npm uninstall @bellaxchan/eleventech in every project. Use the official Baileys package and pin the version in your lockfile.
  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. GitHub says to treat the computer as compromised. From a different computer, rotate the secrets and keys on 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 `@bellaxchan/eleventech` 0.0.8. 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

@bellaxchan/eleventech 0.0.8

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

  1. Ask the AI tool to swap @bellaxchan/eleventech to 0.0.0-stage. That is the last safe version.

Frequently asked questions

Is @bellaxchan/eleventech safe to use?

No. Version 0.0.8 makes the bot's WhatsApp account follow a channel without consent, 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.

Sources

  1. github.com/advisories/GHSA-xfxr-27rj-f57f
  2. osv.dev/vulnerability/MAL-2026-18672
  3. unpkg.com/@bellaxchan/eleventech@0.0.8/lib/Socket/newsletter.js
  4. registry.npmjs.org/@bellaxchan/eleventech

More supply chain attacks

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