@fyxzpediaa/baileys and @fyxzpediaa/libsignal npm packages are malware — full host compromise
Severity: critical · Patch status: no-fix-needed · Since 2026-11-04
GitHub's advisory database published two malware advisories on 2026-11-04 for the npm packages @fyxzpediaa/baileys and @fyxzpediaa/libsignal, typosquat-style imitations of the popular Baileys WhatsApp library and libsignal. Every published version (= 0) is flagged as containing embedded malicious code (CWE-506) with no patched versions available. GitHub's guidance states that any computer with these packages installed or running should be considered fully compromised, implying the malware grants outside attackers full control of the host. The baileys package shows roughly 2,945 downloads per month, indicating real-world exposure. Affected users must remove the packages, rotate all secrets and keys from a clean machine, and reimage/rebuild compromised hosts, since removal alone cannot guarantee the malicious software is gone.
What to do
- Remove @fyxzpediaa/baileys and @fyxzpediaa/libsignal from all projects and lockfiles and block them in your dependency allowlist
- Rotate all secrets, API keys, tokens and credentials stored on any machine where the packages were installed, using a clean computer
- Rebuild or reimage affected machines; removal of the package does not guarantee removal of the malware
- Audit CI/CD pipelines and developer workstations for installs of these packages and review logs for signs of compromise
- Switch to the legitimate, well-known upstream packages (e.g. official Baileys/libsignal forks) if WhatsApp automation is required
Sources
All live incidents on Threat Watch
