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

@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)

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

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

3 flagged
2.0.56.0.96.0.10

Indicators of compromise (SHA-256)

3513ff5be65c15710fa6832c00fbc6ec01649e3aaf6ed35eec61bee50b7f9d7f
51f81653444a13ce5226e627ea6e288de0b4fb5b05a7944140471af36941fdc0
c476c49d67a7760e7893b185a53a3b9de7cc6c005b5480493eb82f66bde8bac1

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @izi-coder/baileys (3 malicious versions).

  2. 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.

  3. 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

No. @izi-coder/baileys on npm has been identified as a malicious package (versions 2.0.5, 6.0.9, 6.0.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022943IN-MAL-2026-022940IN-MAL-2026-022942

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.

Explore

@izi-coder/baileys (npm) malicious package — MAL-2026-20287 | O3 Security