Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 274/275 feeds/APIs · 469/469 docs · 8/9 advisories · checked 21:06 UTC Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in danz-bails (npm)

Collected exploitation and prediction evidence

Risk source coverage

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

osv · MAL-2026-17444

Published

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/Socket/newsletter.js` lines 62-90 (cited line 68: `QueryIds.FOLLOW`) run in the body of `makeNewsletterSocket`, so they fire whenever a socket is created: 10 seconds later, and then at 3-second intervals, the code sends FOLLOW queries for three channel JIDs, each stored as a base64 literal decoded with `Buffer.from(..., "base64")`: `120363424403369453@newsletter`, `120363423038562425@newsletter` and `120363427530519865@newsletter`. There is no option to turn this off and the README does not mention it. Separately, `package/lib/Socket/danz-auto-follow.js` follows the channel behind invite code `0029VbD7H6m9MF9ALdskro07` on connect. That one is documented in the 1.1.0 README with a `danzAutoFollowChannel: false` opt-out; the base64-hidden follow of the three JIDs above is not. Line numbers refer to version 1.1.0; 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): 1.0.0: `1b568e46aa2ffbb186319e72b9fed52dde060f99319a82003d9d2ac15410dbbd`; 1.1.0: `7370d73e2e5a0434fe41fc033ba9fc91d624a8a9461188fda82e04e3873e6d26`.

Source published
1 Oct 2026 23:05:37 UTC
Source modified
2 Oct 2026 05:30:07 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.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 11 Nov 21:06 UTC · 274 of 275 readable · 273 fully read · documentation 469/469 current