babyyodaa (npm): malicious package compromises any machine where it is installed; no safe version exists
Severity: critical · Patch status: no-fix-needed · Since 2026-11-17
GitHub published advisory GHSA-pph8-xw8c-ffc5 on 2026-11-17 flagging the npm package babyyodaa as malware (CWE-506, embedded malicious code). All versions (= 0) are affected and no patched version exists. GitHub's guidance states that any computer with the package installed or running should be considered fully compromised, with full control potentially handed to an outside entity, and that removing the package does not guarantee removal of all malicious software it installed. The package sees roughly 3 downloads per month and has 3 GitHub stars, so reach is limited, but any installation is treated as an active compromise. There is no fix; remediation is incident response, not upgrading.
What to do
- Treat any machine where babyyodaa was installed or executed as fully compromised; isolate and rebuild from trusted media
- Rotate all secrets, keys, tokens and credentials stored on affected machines, from a clean computer
- Hunt for persistence and follow-on malware on affected hosts; removal of the package alone is insufficient
- Block/remove babyyodaa from registries, lockfiles and CI caches; audit dependencies for it
Sources
All live incidents on Threat Watch