LWA-2026-14154 confirmed malware

@sakataa/baileys@5.0.1

Malicious code in @sakataa/baileys (npm)

T1195.002 · Compromise Software Supply ChainT1059.007 · JavaScriptT1102 · Web Service

Analysis

This package is an unofficial fork of the Baileys WhatsApp Web API library published under a non-canonical scope while keeping the canonical "baileys" package name (its README instructs aliasing "@whiskeysockets/baileys": "npm:@sakataa/baileys"). It silently modifies the library user's WhatsApp account. In lib/Socket/newsletter.js, whenever a socket is created, four hardcoded newsletter IDs — 120363427718144294@newsletter, 120363408893555851@newsletter, 120363424295522327@newsletter and 120363426470081124@newsletter — are decoded from base64 string literals and sent as WhatsApp w:mex FOLLOW queries (xwa2_newsletter_follow) on timers of 10 to 25 seconds, with errors swallowed, so the account is force-subscribed to channels the developer controls. lib/Socket/luxu.js (class "imup", instantiated from lib/Socket/messages-send.js) injects fixed forwardedNewsletterMessageInfo attribution blocks (for example newsletterJid 120363421563597486@newsletter, newsletterName "D | 7eppeli-Exloration") and hardcoded "7-Yuukey" / "7eppeli" values into messages the host sends, and lib/index.js prints a Telegram channel advertisement (t[.]me/infobaileys) on import. The package also declares cache-manager ^7.2.8, a range resolving to a dependency version distributed with a malicious payload. All network endpoints referenced are WhatsApp's own (web[.]whatsapp[.]com, call[.]whatsapp[.]com); no non-WhatsApp egress, no token or .npmrc access, and no eval/atob stages were found.

analyzed by
Leitwacht
first seen
Nov 16, 2026, 01:17 PM
analyzed
Nov 16, 2026, 01:19 PM
weekly installs
1,458

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.