Malicious npm package apintergrationpost — full system compromise on install
Severity: critical · Patch status: no-fix-needed · Since 2026-11-18
GitHub's malware advisory database flagged the npm package apintergrationpost as containing embedded malicious code (CWE-506), published 2026-11-18. 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, implying the malware grants outside actors full control of the host. Developers or CI systems that installed the package should assume secrets and keys on those machines were exfiltrated. Removal of the package does not guarantee removal of all malicious software it deployed. No legitimate upstream project exists; the package appears to be a typosquat-style or outright malicious publish.
What to do
- Rotate all secrets, keys, tokens and credentials stored on or accessible from any machine that installed or ran the package, using a clean computer
- Quarantine and rebuild affected machines and CI runners rather than just uninstalling the package
- Audit npm lockfiles and dependency trees for apintergrationpost and remove it everywhere
- Review access logs and network egress for signs of exfiltration or attacker persistence
- Block the package name in internal registries and proxy caches
Sources
All live incidents on Threat Watch