zero-baileys (npm) · Malicious Code
Affects zero-baileysSource GCVE Database
Malicious package : remove zero-baileys and rotate any secrets on hosts that installed it.
Data as of 29 Oct 2026, 18:10 UTC
Malicious package
Published to npm · OSV MAL-2026-16280
What to do
Remove zero-baileys from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmzero-baileys | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The zero-baileys npm package, a fork of the Baileys WhatsApp Web library, has been identified as malicious. Although static analysis shows typical usage of child_process and HTTPS requests consistent with media handling functionality, no direct evidence of exfiltration or credential theft was found. However, the package is considered fully compromising to any system where it is installed or running, with recommendations to rotate all secrets and keys from a separate machine and remove the package. There is no guarantee that removal will eliminate all malicious artifacts due to potential full system compromise.
References
- npmjs.com/package/zero-baileys/v/2.7.0 (opens in a new tab)
- github.com/advisories/GHSA-v486-jrrq-rhwx (opens in a new tab)
- npmjs.com/package/zero-baileys/v/3.2.0 (opens in a new tab)
- npmjs.com/package/zero-baileys/v/3.3.0 (opens in a new tab)
- npmjs.com/package/zero-baileys/v/3.3.5 (opens in a new tab)
- npmjs.com/package/zero-baileys/v/3.5.0 (opens in a new tab)
- npmjs.com/package/zero-baileys/v/2.5.5 (opens in a new tab)
- npmjs.com/package/zero-baileys/v/2.6.0 (opens in a new tab)
- npmjs.com/package/zero-baileys/v/3.6.0 (opens in a new tab)
- npmjs.com/package/zero-baileys/v/3.4.6 (opens in a new tab)