supply chain event / NVI-00011149 / Revision 1
Malicious code in mikuhostt-baileys (npm)
GitHub lists this malware advisory for mikuhostt-baileys, mikuhostt-baileys, mikuhostt-baileys, mikuhostt-baileys. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
mikuhostt-baileys
source listed> 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"` (a plain string literal, repeated as the fallback constant at `package/lib/Socket/newsletter.js` line 11). `package/lib/Socket/index.js` line 11 calls `triggerAutoFollow` (`newsletter.js` line 428) on every socket; 90 seconds after the connection opens, `runAutoFollow` (line 66) sends a raw `w:mex` IQ with `query_id: QueryIds.FOLLOW` (line 96) for that JID, retrying up to three times. The README lists "Auto-follow" only as a feature in a comparison table; it does not say that the library follows the publisher's channel by default. Line num
mikuhostt-baileys
source listed= 1.0.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"` (a plain string literal, repeated as the fallback constant at `package/lib/Socket/newsletter.js` line 11). `package/lib/Socket/index.js` line 11 calls `triggerAutoFollow` (`newsletter.js` line 428) on every socket; 90 seconds after the connection opens, `runAutoFollow` (line 66) sends a raw `w:mex` IQ with `query_id: QueryIds.FOLLOW` (line 96) for that JID, retrying up to three times. The README lists "Auto-follow" only as a feature in a comparison table; it does not say that the library follows the publisher's channel by default. Line num
mikuhostt-baileys
source listed= 1.0.1
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"` (a plain string literal, repeated as the fallback constant at `package/lib/Socket/newsletter.js` line 11). `package/lib/Socket/index.js` line 11 calls `triggerAutoFollow` (`newsletter.js` line 428) on every socket; 90 seconds after the connection opens, `runAutoFollow` (line 66) sends a raw `w:mex` IQ with `query_id: QueryIds.FOLLOW` (line 96) for that JID, retrying up to three times. The README lists "Auto-follow" only as a feature in a comparison table; it does not say that the library follows the publisher's channel by default. Line num
mikuhostt-baileys
source listed= 1.0.2
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"` (a plain string literal, repeated as the fallback constant at `package/lib/Socket/newsletter.js` line 11). `package/lib/Socket/index.js` line 11 calls `triggerAutoFollow` (`newsletter.js` line 428) on every socket; 90 seconds after the connection opens, `runAutoFollow` (line 66) sends a raw `w:mex` IQ with `query_id: QueryIds.FOLLOW` (line 96) for that JID, retrying up to three times. The README lists "Auto-follow" only as a feature in a comparison table; it does not say that the library follows the publisher's channel by default. Line num
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-p4xf-x6j2-mq3f ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.