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 06:51 UTC Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in zero-baileys (npm)

Exact source revision recorded 29 Oct 2026 15:12:22 UTC. It does not establish the source's current position. Latest evidence.

osv · MAL-2026-16280

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (6f7a8aa73b2a3a5a61a45cc6f0ebeff58bfb23f8589895065fa30849421f4471) zero-baileys is a fork of the Baileys WhatsApp Web library. Static keyword co-occurrence fired on lib/Utils/messages-media.js where require('child_process'), https.request, hostname, and POST all appear in the same file. In Baileys and its forks, messages-media.js handles media encryption/decryption and HTTP(S) uploads/downloads to WhatsApp's own media endpoints; child_process is used for optional ffmpeg/imagemagick invocation for media conversion. The keyword pattern is consistent with that documented functionality rather than with exfiltration: no specific installer-side data read (env, ~/.aws, ~/.ssh, ~/.npmrc, browser stores) is identified being sent to a non-first-party destination, and no install-time lifecycle hook or top-level side effect is present. No hardcoded attacker C2, no obfuscated destination, no credential-database or wallet enumeration, and no persistence artifact is observed. As a Baileys fork the package does carry the category-level concerns of that ecosystem (some forks have added covert side-effects such as auto-follow of author channels using the caller's session), but nothing of that shape is corroborated here. ## Source: ghsa-malware (e18ff0786d183c3327cf8291eac1d72b1fa8379e834e367c2341da1e87ab9e32) 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
18 Sep 2026 02:54:59 UTC
Source modified
29 Oct 2026 14:30:43 UTC
Observed here
29 Oct 2026 15:12:22 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 7 Nov 06:51 UTC · 275 of 275 readable · 274 fully read · documentation 469/469 current