npm typosquat malware wave: astam-ifst-* packages fully compromise installed machines (no CVE)
Severity: critical · Patch status: no-fix-needed · Since 2026-11-16
On 2026-11-16 GitHub added four malware advisories for related npm packages astam-ifst-dia, astam-ifst-diakav, astam-ifst-diakavgya and astam-ifut-dakiula, all at version 1.2.2. The packages are classified as embedded malicious code (CWE-506) with no patched versions; GitHub states any machine with them installed or running should be considered fully compromised, implying attacker control, secret/key theft and possible persistence beyond simple removal. Download volumes are small (2-242/month), suggesting a typosquatting-style campaign against a narrow set of victims, but any dependent project or CI system that pulled these versions is affected. No fix exists; remediation is removal plus credential rotation and host forensics.
What to do
- Check lockfiles and CI caches for astam-ifst-dia, astam-ifst-diakav, astam-ifst-diakavgya or astam-ifut-dakiula at 1.2.2 and remove them
- Treat any machine or runner that installed them as fully compromised: rotate all secrets and keys from a clean machine
- Rebuild affected hosts/containers from trusted images and audit for persistence
- Block the package names in npm registries, proxies and dependency firewalls
- Review npm install logs to determine exposure window and what credentials were accessible
Sources
All live incidents on Threat Watch