@izi-coder/baileysnpm
Advisory published Updated
@izi-coder/baileys is a confirmed malicious npm package (MAL-2026-20287) that executes malicious code on install (malicious versions 2.0.5, 6.0.9, 6.0.10). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @izi-coder/baileys (npm)
What this malware does
This unofficial fork of Baileys declares a production dependency sourced directly from a GitHub repository with no commit pin: "libsignal": "github:Cogils/libsignal-node" in package.json. npm install resolves that source off-registry, fetches whatever the branch tip currently holds, and runs any lifecycle scripts inside it. The referenced repository is owned by a third party (Cogils), unrelated to the upstream WhiskeySockets/Baileys publisher, so whoever controls that repo controls code executed on the installer's machine at install time. The package also presents low-trust provenance: it is published under @izi-coder as an unofficial Baileys fork, the manifest's repository URL points at a Telegram channel rather than a source host, and lib/index.js prints a hostile ASCII banner and Telegram self-promo links on import.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for @izi-coder/baileys (3 malicious versions).
If you installed it — respond
Remove @izi-coder/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.
Did it already run?
If @izi-coder/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 @izi-coder/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.