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

@kropaku/baileysnpm

Advisory published Updated

@kropaku/baileys is a confirmed malicious npm package (MAL-2026-20311) that steals credentials and exfiltrates sensitive data (malicious versions 6.7.20, 6.7.21, 6.7.22…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @kropaku/baileys (npm)

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

What this malware does

This package is a fork of the Baileys WhatsApp library that embeds code which decodes a hidden HTTPS destination from a String.fromCharCode byte array at lib/Socket/messages-send.js lines 425 and 436. The decoded host is https://fiora.nixel.my.id/, a third-party endpoint unrelated to the upstream Baileys project, reached from within the message-send path. The host string is concealed via char-code arithmetic rather than appearing as a plain literal, which is an obfuscation technique used to hide network destinations from casual inspection. The package also ships lib/Utils/license-guard.js as a heavily obfuscated module (hex-mangled identifiers such as _0x1e6253, _0x1d5468, etc., consistent with javascript-obfuscator output), hiding the logic that gates the library's behavior and its interactions with the hidden endpoint. The combination of (a) an obfuscated license/guard module loaded by a WhatsApp session library that handles authentication credentials and message contents, and (b) a char-code-concealed outbound HTTPS destination wired into the outgoing message pipeline, is the fingerprint of covert data relay or credential/session exfiltration from an upstream-impersonating fork, not of legitimate WhatsApp protocol code.

Malicious versions

5 flagged
6.7.206.7.216.7.226.7.236.7.24

Indicators of compromise (SHA-256)

000ee18abd7189f91e848581d2931bc14636b7f624218ab56ce0072064845c26
5db9ebf68a92baab0d0500598ce8910f496db0f958b33fd2c6552452f1b5bcb2
7f21c39cccccc192ea43e43dbcf21efd1ac9c273a325f7001288ccdc115748c8
e634fd115885f8cb0a2e2ab98b78bdc26d5f0cb37865cea6d848296478ace3d4
ef350901d7e283ceea2892392567e98883f225d74eaf3242d952a698b4868475

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @kropaku/baileys (5 malicious versions).

  2. If you installed it — respond

    @kropaku/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 @kropaku/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. @kropaku/baileys on npm has been identified as a malicious package (versions 6.7.20, 6.7.21, 6.7.22, 6.7.23, 6.7.24 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022967IN-MAL-2026-022970IN-MAL-2026-022971IN-MAL-2026-022963IN-MAL-2026-022969

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

@kropaku/baileys (npm) malicious package — MAL-2026-20311 | O3 Security