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

@ikyerza/baileysnpm

Advisory published Updated

@ikyerza/baileys is a confirmed malicious npm package (MAL-2026-20285) that executes malicious code on install (malicious versions 1.0.0, 1.1.1, 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ikyerza/baileys (npm)

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

What this malware does

package.json declares the libsignal dependency as github:tenka-san/libsignal-node with no commit SHA or tag. On npm install, npm clones whatever the current HEAD of that personal GitHub repository is and executes any lifecycle scripts it contains on the installer's machine. The dependency key libsignal also shadows the published registry package of the same name, a dependency-confusion-shape aggravator: callers reading the manifest see a familiar name but resolution is redirected to a personal account that is not associated with the declared publisher of this package or of the upstream Baileys project. The repository owner can change the installed bytes at any time without any version bump in this package.

Malicious versions

3 flagged
1.0.01.1.11.2.0

Indicators of compromise (SHA-256)

0218298ffb531a5c44ec1ff6b04cf600b8dd52addcbe6fb832b1aa4498f47d29
4130bf477ca0993c6e49d6d3ccfa6f1302ecce7b574145e524c16c3e6fbf6468
2bb2b392bb9734f3f3d241f170a854e6718a6d7e5cf1f7c84a9761c462057d70

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove @ikyerza/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 @ikyerza/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. @ikyerza/baileys on npm has been identified as a malicious package (versions 1.0.0, 1.1.1, 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022941IN-MAL-2026-022944IN-MAL-2026-022945

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @ikyerza/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

@ikyerza/baileys (npm) malicious package — MAL-2026-20285 | O3 Security