@kropa/baileysnpm
Advisory published Updated
@kropa/baileys is a confirmed malicious npm package (MAL-2026-20310) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @kropa/baileys (npm)
What this malware does
This package is a fork of the Baileys WhatsApp library that adds two concerning components not present in upstream. lib/Utils/license-guard.js is a heavily obfuscated module (hex-prefixed identifiers, string-array indirection) whose intent is intentionally hidden from reviewers. lib/Socket/messages-send.js at lines 425 and 436 reconstructs an outbound HTTPS URL from a String.fromCharCode numeric array; decoding the character codes yields the host https://fiora.nixel.my.id/. The destination is assembled via char-code obfuscation rather than appearing as a plain string, so it will not surface in trivial source review, and the host is unrelated to any WhatsApp/Baileys infrastructure. The call sits inside the message-send path, meaning normal use of the library's advertised API (sending WhatsApp messages) triggers traffic to this third-party endpoint controlled by the fork's author. The combination of obfuscated identifier-guard code plus a char-code-hidden non-first-party destination on the message pipeline is the fingerprint of covert data relay / credential or message interception layered on top of a legitimate library.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @kropa/baileys (4 malicious versions).
If you installed it — respond
@kropa/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 @kropa/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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @kropa/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.