arshadahmed: malicious npm package can fully compromise hosts and secrets
Severity: critical · Patch status: no-fix-needed · Since 2026-11-20
GitHub Advisory Database published GHSA-9qcw-jqhm-rpg5 on 2026-11-20 for the npm package arshadahmed version 1.0.0, classifying it as malware with CWE-506 Embedded Malicious Code and critical severity. The advisory states that any computer with the package installed or running should be considered fully compromised, that an outside entity may have obtained full control, and that all secrets and keys should be rotated from a different computer. The package has about 19 downloads per month and no patched versions; removal is recommended, but the advisory warns it may not eliminate all malicious software. No CVE, CVSS, EPSS, or exploitation details were provided. Organizations that installed or depend on arshadahmed should isolate affected hosts, rotate credentials, and rebuild from clean sources.
What to do
- Immediately isolate any host where arshadahmed 1.0.0 was installed or run and treat it as fully compromised.
- From a different, clean computer, rotate all secrets, API keys, npm tokens, SSH keys, cloud credentials, and passwords that were accessible to affected hosts.
- Remove the package and rebuild affected environments from clean sources; do not rely on uninstall alone to remove persistence.
- Audit lockfiles, CI/CD logs, and npm install history for arshadahmed; scan for malicious persistence and unauthorized access.
- Review npm publish/install credentials and monitor for anomalous package activity; consider blocking the package in registries/proxies.
Sources
All live incidents on Threat Watch