Public mode

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

Some sources or documents need attention: 275/275 feeds/APIs · 469/469 docs · 9/9 advisories · checked 22:08 UTC Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in prastzyy (npm)

Exact source revision recorded 24 Oct 2026 13:17:17 UTC. It does not establish the source's current position. Latest evidence.

osv · MAL-2026-17449

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-103 define `AUTO_FOLLOW_JIDS`, eight base64 strings decoded with `Buffer.from(..., "base64")`, and when the connection opens (line 102) schedule a FOLLOW query for each, 90 seconds apart (cited line 90: `await newsletterWMexQuery(jid, QueryIds.FOLLOW);`). Decoded JIDs: `120363430764800148@newsletter`, `120363400505489366@newsletter`, `120363427794786523@newsletter`, `120363428149518339@newsletter`, `120363411665168068@newsletter`, `120363410421978309@newsletter`, `120363426605069018@newsletter` and `120363425633124233@newsletter`. There is no opt-out and the behavior is not documented. Line numbers refer to version 1.0.0. 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: `9451d13f06ff94c6d627f7ba7d8a7ad7f73a6cfbb856c7f4c2e29c3b187484bb`. --- _-= Per source details. Do not edit below this line.=-_ ## Source: ghsa-malware (bf5b70083dc2338579dac55f7f321700cf098ccc3ac71d5506c8dca2b3855ddc) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Source published
19 Oct 2026 06:23:40 UTC
Source modified
19 Oct 2026 17:37:49 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 8 Nov 22:08 UTC · 275 of 275 readable · 273 fully read · documentation 469/469 current