Malicious npm packages @budetzz/baileys and @budetzz/libsignal-node flagged as malware
Severity: critical · Patch status: no-fix-needed · Since 2026-11-12
GitHub's advisory database published malware advisories on 2026-11-12 for two npm packages under the @budetzz scope: @budetzz/baileys (GHSA-qpp3-3mx8-62m7, ~2,895 downloads/month, 11K GitHub stars) and @budetzz/libsignal-node (GHSA-6wr3-c2pp-j3r6, ~319 downloads/month). Both are classified CWE-506 Embedded Malicious Code, affect all versions (= 0), and have no patched versions. GitHub warns that any computer with these packages installed or running should be considered fully compromised, with full control potentially given to an outside entity, and that removing the package may not remove all malicious software. Names mimic the legitimate Baileys WhatsApp library and libsignal, suggesting a typosquat/scope-squat distribution. All secrets and keys on affected machines must be rotated.
What to do
- Remove @budetzz/baileys and @budetzz/libsignal-node from all projects and lockfiles immediately
- Treat affected machines as fully compromised: rebuild/reimage hosts and containers
- Rotate all secrets, keys, tokens and credentials stored on or accessible from affected machines, from a clean computer
- Audit for persistence mechanisms and follow-on malware left after package removal
- Block the @budetzz npm scope in internal registries and CI, and scan dependency trees for it
Sources
All live incidents on Threat Watch
