luoxy-baileys

GHSA-rhcf-fwmc-3cm3

Malicious code in luoxy-baileys (npm)

Details

**Severity:** Critical

**Affected versions:** `> 0`

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 […]

**References:**
- https://github.com/ossf/malicious-packages/blob/d69382a194448ad0562ad4d9e4380c1c6a673841/osv/malicious/npm/luoxy-baileys/MAL-2026-17446.json
- https://www.npmjs.com/package/luoxy-baileys
- https://www.ox.security/blog/phantomsub-malicious-npm-campaign-secretly-adds-users-to-whatsapp-spam-channels
- https://github.com/ossf/malicious-packages/blob/2bb9370d891283643f919e860abea2cc197b0b3b/osv/malicious/npm/luoxy-baileys/MAL-2026-17446.json
- https://www.npmjs.com/package/luoxy-baileys/v/7.1.1
- https://www.npmjs.com/package/luoxy-baileys/v/7.1.2
- https://www.npmjs.com/package/luoxy-baileys/v/7.1.3
- https://github.com/advisories/GHSA-rhcf-fwmc-3cm3

Compromised versions (1)

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.