Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@celestial-community/baileysnpm

Advisory published Updated

@celestial-community/baileys is a confirmed malicious npm package (MAL-2026-17438) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @celestial-community/baileys (npm)

MAL-2026-17438
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @celestial-community/baileys

What this malware does

This package is a fork of the Baileys WhatsApp Web library (npm) and belongs to the "PhantomSub" family described by OX Security in September 2026: the publisher injected code that, without the installer asking, uses the installer's own authenticated WhatsApp session to subscribe that account to WhatsApp Channels (newsletters) the publisher chose, by sending the WhatsApp w:mex FOLLOW query (query_id 7871414976211147) for each target channel JID.

The package carries three independent follow routines, all unconditional and undocumented:

  1. package/lib/Socket/socket.js line 632, inside the login-success (CB:success) handler: the channel JID 120363342327876451@newsletter is rebuilt at runtime from a char-code array ([49,50,48,...].map(c=>String.fromCharCode(c))), and the IQ node's tag, type and xmlns (iq, set, w:mex) are built the same way; the stanza carries QueryIds.FOLLOW and fires after a random delay of roughly 4 seconds to 2 minutes.

  2. package/lib/Socket/socket.js lines 633-652: fetches https://raw.githubusercontent.com/Denzy-Lawrence/anu/refs/heads/main/anu.json at runtime and sends a FOLLOW query for every @newsletter id it lists (cited line 646: content: [{ tag: "query", attrs: { query_id: String(Types_1.QueryIds.FOLLOW) }, ... newsletter_id: _id ...), so the target list can change without a new npm release. On 2026-10-01 the list contained 120363342327876451@newsletter.

  3. package/lib/Socket/newsletter.js lines 156-164: a new Function(...) whose body is a base64 string; decoded, it fetches the same anu.json list 30 seconds after the connection opens and, for each id, sends FOLLOW and then, 3 seconds later, MUTE, so the victim is not notified of the channel's posts. Line 165 onward adds a second connection.update handler that fetches a base64-encoded URL, https://raw.githubusercontent.com/Denvy-Lawrence/anu/refs/heads/main/anu.json (HTTP 404 on 2026-10-01), and FOLLOWs each id it returns.

package/lib/index.js line 7 also evals a base64 string on import; decoded, it only prints a "Baileys Custom By Denzy ZeroDay" banner.

Line numbers refer to version 1.0.0.

Static review of the published tarball(s) found no code that sends WhatsApp credentials or session keys off-host, no install-time payload (the only install hook is Baileys' stock Node.js version check in engine-requirements.js), and no persistence; the payload runs when an application creates a WhatsApp socket with the library. The harm is the covert use of the victim's account to inflate the publisher's channel subscribers.

SHA-256 of the published npm tarball(s): 1.0.0: 7145cc1447909b6e0d14a0743f1cc5a4072303add062bfb7cb9cccee3b032620.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

308c25b04f022ef3533f881f9495a8ca81f944a994d02b3db6b70bc2ed26630d

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @celestial-community/baileys (version 1.0.0).

  2. If you installed it — respond

    @celestial-community/baileys is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @celestial-community/baileys was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @celestial-community/baileys on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5ghv-64gv-gv29

References

Credits

  • Rising Sun Solutions LLC · finder

Detect & block this

O3 blocks @celestial-community/baileys-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@celestial-community/baileys (npm) malicious package — MAL-2026-17438 | O3 Security