@axo_cuy/baileys (npm) · Malicious Code
Affects @axo_cuy/baileysSource GCVE Database
Malicious package : remove @axo_cuy/baileys and rotate any secrets on hosts that installed it.
Data as of 2 Nov 2026, 04:31 UTC
Malicious package
Published to npm · OSV MAL-2026-18440
What to do
Remove @axo_cuy/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 |
|---|---|---|
| npm@axo_cuy/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 npm package @axo_cuy/baileys version 1.0.0 declares a hard dependency on an off-registry GitHub repository (github:tenka-san/libsignal-node) without version pinning or integrity checks. This allows the third-party repository owner to change the code at any time, potentially introducing malicious code during installation. The dependency bypasses npm registry review and dependency pinning, increasing the risk of supply chain compromise.