Vulnerabilities

Vulnerability · MAL-2026-17439

Malicious code in @developmentyora/baileyss (npm)

Published Oct 16, 2026 · catalog updated Oct 16, 2026 · Malicious code in @developmentyora/baileyss

Open the advisory

Exploitation likelihood is not on this record for MAL-2026-17439. A missing EPSS score is not a low risk. Compare Malicious code in @developmentyora/baileyss with the linked advisory before you change production.

Severity

Unknown—

Known exploitation

Not in CISA/VulnCheck KEV

EPSS

Awaiting synchronization with FIRST

Remediation

Advisory link

Affected products

npm @developmentyora/baileyss

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 FOLLOW query (query_id 7871414976211147) for each target channel JID. lines 62-103 (cited line 68: ) run in the body of , so they fire whenever a socket is created: 90 seconds later, and then at 5-second intervals, the code sends FOLLOW queries for four channel JIDs, each stored as a base64 literal decoded with : , , and . 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 ), 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: . --- _-= Per source details. Do not edit below this line.=-_ ## Source: ghsa-malware (61d053d8d7d05715f1099bf3d620177886fda31a4c45f5c21d687b2fcd9abb39) 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.