CRITICAL npm Malware

Malicious code in @kropaku/baileys (npm)

MAL-2026-20311

Published · Modified

Dependency scanning

Check whether @kropaku/baileys is in your codebase

Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.

Description


__

Source: amazon-inspector (e634fd115885f8cb0a2e2ab98b78bdc26d5f0cb37865cea6d848296478ace3d4)

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.

Ready to move

Start Securing

Free, no credit card | First findings in minutes