LWA-2026-14095 MAL-2026-18921 ↗ confirmed malware

@yun-xiao/baileys@2.0.0

Malicious code in @yun-xiao/baileys (npm)

T1195.002 · Compromise Software Supply ChainT1059.007 · JavaScriptT1071.001 · Web ProtocolsT1539 · Steal Web Session Cookie

Analysis

The package is a republished fork of Baileys, the WhatsApp Web JavaScript library, shipped under an unofficial scope with the upstream package name "baileys" kept intact. Its clone carries an injected, undisclosed behaviour in lib/Socket/newsletter.js: a NEWSLETTERS_V2 table hardcodes two WhatsApp channel JIDs (120363407049212252@newsletter and 120363425547320365@newsletter) and an unconditional timer of 90000 ms is started when a WhatsApp socket is created. When it fires, the code issues two w:mex newsletter FOLLOW queries (Types.QueryIds.FOLLOW) addressed to those hardcoded channels, silently subscribing the authenticated user's account to them; any error is discarded by an empty catch block. There is no option, configuration flag, consent prompt or logging around it. Upstream Baileys has no hardcoded channel IDs and never auto-follows a channel on its own, so installing this fork and connecting an account causes that account to follow the two channels above within ~90 seconds. Network destinations observed in the package are WhatsApp's own endpoints (wss://web[.]whatsapp[.]com/ws/chat, hxxps://web[.]whatsapp[.]com), hxxps://raw[.]githubusercontent[.]com/z4phdev/baileys/master/src/Defaults/baileys-version[.]json for version lookup, and media handling via child_process. The preinstall hook engine-requirements.js only reads the Node.js major version and exits when below 20; it performs no network or filesystem access. No reads of environment variables, .npmrc, ~/.ssh, ~/.aws or other credential stores were found in the shipped code.

analyzed by
Leitwacht
first seen
Nov 15, 2026, 09:32 AM
analyzed
Nov 16, 2026, 12:15 AM

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.