Malicious code in luoxy-baileys (npm)

This package is a fork of the Baileys WhatsApp Web library (npm) and belongs to the "PhantomSub" family described by OX Security in September 2026: the publisher injected code that, without the installer asking, uses the installer's own authenticated WhatsApp session to subscribe that account to WhatsApp Channels (newsletters) the publisher chose, by sending the WhatsApp `w:mex` FOLLOW query (query_id 7871414976211147) for each target channel JID. `package/lib/Defaults/index.js` lines 78-80 ship the defaults `autoFollowNewsletterOnConnect: true`, `autoFollowNewsletterDelayMs: 90000` and `autoFollowNewsletterJid: "120363400911374213@newsletter"`. `package/lib/Socket/newsletter.js` lines 12-30 additionally fetch `https://raw.githubusercontent.com/iyedahruss/all-public-db/refs/heads/main/newsletter.json` at runtime and add every `@newsletter` id in it to the follow list, so the targets can change without a new npm release. `package/lib/Socket/index.js` line 11 calls `triggerAutoFollow` (`newsletter.js` line 484) on every socket; 90 seconds after the connection opens, `runAutoFollow` (line 108) sends a raw `w:mex` IQ with `query_id: QueryIds.FOLLOW` (line 139) for each target, retrying up to three times. On 2026-10-01 the remote list contained `120363418964199743@newsletter`, `120363410316899314@newsletter`, `120363429190136593@newsletter` and `120363429068662026@newsletter` (under the key `saurus`). The README lists "Auto-follow" only as a feature in a comparison table; it does not say that the library follows the publisher's channels by default. Line numbers refer to version 7.1.3; the same code is present in every published version listed under `affected`. Static review of the published tarball(s) found no code that sends WhatsApp credentials or session keys off-host, no install-time payload (the only install hook is Baileys' stock Node.js version check in `engine-requirements.js`), and no persistence; the payload runs when an application creates a WhatsApp socket with the library. The harm is the covert use of the victim's account to inflate the publisher's channel subscribers. SHA-256 of the published npm tarball(s): 7.1.1: `37550f81f18467c3378bd7c402813841f2696372fba50a03a22fff0e21115984`; 7.1.2: `139dddeb58e8a04b9c6f4def85f759768b27de217cde6b577b262b5fe297fed3`; 7.1.3: `6adfeb716809fa59638b6476fca8cc6ef8c8a0fdb7fc9a54390d403879bb111e`. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (04ce355b05eb705838b671992fa04458058a3f6c098b03acc077e7abd63dee3b) luoxy-baileys is a fork of the Baileys WhatsApp library. Its default export makeWASocket unconditionally invokes triggerAutoFollow, which — 90 seconds after a successful WhatsApp connection — issues FOLLOW iq stanzas from the installer's connected WhatsApp account. The targets are a hardcoded newsletter JID (120363400911374213@newsletter) plus a mutable list of JIDs fetched at runtime from https://raw.githubusercontent.com/iyedahruss/all-public-db/refs/heads/main/newsletter.json. The behavior is enabled by default (DEFAULT_CONNECTION_CONFIG.autoFollowNewsletterOnConnect: true) and is not documented; an opt-out exists via autoFollowNewsletterOnConnect:false. Because the followed-JID list is fetched at runtime from an author-controlled GitHub raw URL, the set of channels the installer's account subscribes to can be changed by the author after install. No installer credentials, filesystem data, or environment variables are read; no remote code is fetched or executed; no persistence or backdoor is installed. The static match on lib/Utils/generics.js referencing ping/GET is a standard HTTP GET performing the newsletter.json fetch, not exfiltration. The ping static hit relates to a generic keepalive/utility, not command execution against the installer.

Source published

11 Oct 2026 16:54:06 UTC

Source modified

11 Oct 2026 17:30:48 UTC

Observed here

24 Oct 2026 13:17:17 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.