LWA-2026-13672 MAL-2026-18675 ↗ confirmed malware

@denzz221/baileys@7.0.0

Malicious code in @denzz221/baileys (npm)

T1195.002 · Compromise Software Supply ChainT1059 · Command and Scripting InterpreterT1071 · Application Layer ProtocolT1102 · Web ServiceT1036 · MasqueradingT1565 · Data Manipulation

Analysis

This package is a trojanized clone of the Baileys WhatsApp library, republished under a different scope, that silently enrols applications into an author-controlled WhatsApp channel. In lib/Socket/newsletter.js, inside makeNewsletterSocket — which runs whenever a client socket is constructed by any application using the library — the code schedules a 90-second timer whose callback sends the w:mex newsletter query with QueryIds.FOLLOW for the hardcoded channel id 120363400780200098@newsletter, wrapped in an empty catch so the subscription is invisible to the embedding application and its user. The same file rebuilds the upstream newsletter socket with its own makeGroupsSocket instance, so the upstream source was edited rather than merely repackaged. The package also injects vanity channel metadata into outbound messages: lib/Socket/dugong.js stamps forwardedNewsletterMessageInfo with newsletterJid 120363297591152843@newsletter, newsletterName "shenvn." and senderName "kikyy dugonggg", and lib/Utils/messages.js references newsletterName "kyuu ilysm". All network activity goes to WhatsApp infrastructure (wss://web[.]whatsapp[.]com/ws/chat, *.whatsapp[.]net); the payload carries no third-party command-and-control endpoint and no credential, token or environment harvesting was found in the shipped library code. Any project that installs this fork and connects a WhatsApp session will have the victim account subscribed to the operator's channel without consent.

analyzed by
Leitwacht
first seen
Nov 5, 2026, 05:21 AM
analyzed
Nov 5, 2026, 05:23 AM
weekly installs
223

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.