LWA-2026-13480 confirmed malware

@sakataa/baileys@2.0.0

Malicious code in @sakataa/baileys (npm)

T1195.002 · Compromise Software Supply ChainT1071.001 · Web ProtocolsT1041 · Exfiltration Over C2 Channel

Analysis

This package is an unofficial-scope copy of the Baileys WhatsApp library (@whiskeysockets/baileys) published as @sakataa/baileys, with code added on top of the upstream source tree. Two behaviours matter. First, importing the package runs lib/Store/make-cache-manager-store.js, which calls require("cache-manager") at module load, so the declared dependency range ^7.2.8 — resolving to cache-manager 7.2.10, a release with known malicious behaviour — is loaded as soon as the library is imported, not only when an optional cache store is requested. Second, lib/Socket/socket.js adds an exported helper `checkBan(number)` that sends the queried phone number to hxxps://kyuux-r[.]indevs[.]in/api/check-whatsapp?phone=<number> with a spoofed desktop-browser User-Agent and returns the response tagged with creator "t[.]me/luyatiem"; this endpoint does not exist in the upstream library and is unrelated to WhatsApp. The package also pins whatsapp-rust-bridge 0.5.4 exactly and imports it from lib/Utils/crypto.js, lib/Utils/lt-hash.js and lib/Utils/chat-utils.js, so that third-party WASM bridge is loaded on every import. Installation itself only runs a Node.js version check (preinstall: node ./engine-requirements.js); the package advertises itself via "t[.]me/infobaileys" and "t[.]me/sakata_real" console output. There is no obfuscation, no eval/eval(atob) decoding and no access to .npmrc, ~/.ssh, ~/.aws or cloud tokens in the code examined. IOCs: hxxps://kyuux-r[.]indevs[.]in/api/check-whatsapp?phone=<number>, t[.]me/luyatiem, t[.]me/infobaileys, t[.]me/sakata_real.

analyzed by
Leitwacht
first seen
Oct 30, 2026, 04:04 PM
analyzed
Oct 30, 2026, 04:04 PM
weekly installs
943

Related advisories

browse all confirmed advisories →

Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.