Malicious npm package abiba-avbai-ayub — full machine compromise for installers (no CVE)
Severity: critical · Patch status: no-fix-needed · Since 2026-11-18
GitHub's malware advisory database published GHSA-xr82-65pq-hwqf on 2026-11-18 flagging the npm package abiba-avbai-ayub version 1.0.0 as embedded malicious code (CWE-506). Any machine with the package installed or running must be considered fully compromised, with control potentially handed to an outside actor; secrets and keys on affected systems are at risk. The package sees roughly 128 downloads per month and has no patched versions — removal of the package alone cannot be assumed to remove all malicious software it may have deployed. No CVE is assigned, no source code exists, and no fix will be issued since the package is malware. Developers and CI systems that installed it should treat credentials as stolen and remediate accordingly.
What to do
- Rotate all secrets, keys, and credentials stored on any machine where the package was installed, using a clean machine
- Remove abiba-avbai-ayub@1.0.0 from all projects, lockfiles, and CI caches
- Rebuild or reimage affected machines; do not assume removal cleans the system
- Audit systems for signs of compromise and unexpected outbound connections
- Block the package in npm registries, proxies, and dependency scanning policies
Sources
All live incidents on Threat Watch