NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@sanzoffc/baileysnpm

Advisory published Updated

@sanzoffc/baileys is a confirmed malicious npm package (MAL-2026-16281) that executes malicious code on install (malicious version 3.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sanzoffc/baileys (npm)

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

What this malware does

This package is a fork of the Baileys WhatsApp library that adds covert remote-controlled behavior driven by the installer's authenticated WhatsApp session. In lib/Socket/socket.js, socketConnect() (invoked from validateConnection on every WebSocket open) reconstructs a URL from a String.fromCharCode char-code array that resolves to https://raw.githubusercontent.com/skyzopedia/NewsletterID/refs/heads/main/VIP_Push.json, fetches that JSON list, and iterates it to issue WhatsApp GraphQL mutations with query_id 7871414976211147 (newsletter subscribe/follow) for each id in the remote-supplied list. The list is hosted on a mutable personal-GitHub branch controlled by a third party, so whoever edits that file determines which actions the installer's WhatsApp account performs. A second helper (generateMessageV) base64+XOR-decodes (key 23) a hardcoded '@newsletter' JID and pairs it with the same query_id 7871414976211147, then schedules the same subscription action 40 seconds after invocation - layered string obfuscation of a fixed destination JID that has no legitimate purpose in a WhatsApp protocol library. The behavior is not documented, not caller-configurable, and the URL and JID are deliberately obfuscated to evade string scanners. The manifest additionally declares '@whiskeysockets/eslint-config' as an unpinned github: source and pins most other dependencies to '*', widening the resolution trust boundary.

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
3.0.4

Indicators of compromise (SHA-256)

4393cd98419ed1fce683c0fde038bce830873769d85d69e64674df61f68502bc
5e518551b202e71d22a3dd3916d6b86696c778ef910311e7bb6867c1c0b171f5

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @sanzoffc/baileys (version 3.0.4).

  2. If you installed it — respond

    Remove @sanzoffc/baileys from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @sanzoffc/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. @sanzoffc/baileys on npm has been identified as a malicious package (version 3.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020178GHSA-w5cc-9p38-q2wq

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @sanzoffc/baileys-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

@sanzoffc/baileys (npm) malicious package — MAL-2026-16281 | O3 Security