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

@iky-erza/baileysnpm

Advisory published Updated

@iky-erza/baileys is a confirmed malicious npm package (MAL-2026-20284) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @iky-erza/baileys (npm)

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

What this malware does

package.json declares the runtime dependency libsignal as github:tenka-san/libsignal-node with no commit SHA, tag, or semver pin. On npm install, npm fetches whatever the repository's default branch HEAD currently points at and runs any lifecycle scripts inside it on the installer's machine, with no integrity check and no version pinning. Whoever controls that GitHub account can change the resolved code at any time without republishing this package, and installers running npm install @iky-erza/baileys will pick up the change on the next install. This is an off-registry, mutable dependency source — a different trust surface from the registry-published libsignal used by upstream Baileys. A separate static match on lib/Utils/generics.js corresponds to standard cross-platform ping dispatch for connectivity checks and is not by itself indicative of exfiltration.

Malicious versions

1 flagged
0.1.0

Indicators of compromise (SHA-256)

967763a0fcb8295a6cee58761594b585651571a5be455f106435bc70aa59b400

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @iky-erza/baileys (version 0.1.0).

  2. If you installed it — respond

    @iky-erza/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.

  3. Did it already run?

    If @iky-erza/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. @iky-erza/baileys on npm has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022946

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @iky-erza/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.

Explore

@iky-erza/baileys (npm) malicious package — MAL-2026-20284 | O3 Security