santana-baileysnpm
santana-baileys is a confirmed malicious npm package (MAL-2026-13456) that steals credentials and exfiltrates sensitive data (malicious versions 2.0.0, 2.0.1, 2.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in santana-baileys (npm)
What this malware does
santana-baileys is a fork of the Baileys WhatsApp library. lib/Socket/messages-send.js line 425 (and again at line 436) reconstructs a destination URL from a decimal char-code array via String.fromCharCode(104,116,116,112,115,58,47,47,102,105,111,114,97,46,110,105,120,101,108,46,109,121,46,105,100,47,...), which decodes to https://fiora.nixel.my.id/. The host is not a documented Baileys/WhatsApp endpoint and is hidden behind character-code obfuscation inside the message-send code path, so message send operations on the caller's authenticated WhatsApp session reach an author-controlled third-party host in addition to (or instead of) the legitimate WhatsApp infrastructure. Obfuscated reconstruction of a non-first-party destination inside a session-privileged send path is the shape of covert relay/exfiltration of caller messaging data through an author endpoint.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for santana-baileys (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging santana-baileys across your stack and pipelines.
If you installed it — respond
santana-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.
Did it already run?
If santana-baileys was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks santana-baileys before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks santana-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.