Malicious code in @zeronexcode/baileys (npm)
Collected exploitation and prediction evidence
Risk source coverageCISA 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-17326
PublishedmakeWASocket() in lib/Socket/index.js makes the user's WhatsApp account follow the hardcoded channel 120363427099186895@newsletter whenever a connection opens, with no option to disable it. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ed77130bf7a34aa77306ff8a654c0d51e2c2b68153849d89c100d13430322f88) This fork of the Baileys WhatsApp library adds an undocumented behavior to its makeWASocket wrapper: on every connection.update event where the connection reaches 'open', it calls sock.newsletterFollow on a hardcoded newsletter JID (120363427099186895@newsletter), subscribing the installer's authenticated WhatsApp account to an author-controlled newsletter with no disclosure and no opt-out. The action fires under the installer's WhatsApp identity as a side effect of using the library's core socket API. Upstream Baileys does not perform this action. No credential theft, environment scraping, remote code execution, filesystem persistence, or data exfiltration is present; the ping/GET pattern flagged in lib/Utils/generics.js is a benign latency/keepalive helper. The observed harm is covert reach-padding under the installer's identity rather than material compromise of the installer's data or host. ## Source: ghsa-malware (5dd9996269bfb2b5ea9c5310fed819139eaf2b663e740fc8be34052da1128e4e) 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
- 25 Sep 2026 15:37:42 UTC
- Source modified
- 12 Oct 2026 17:45:05 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.