Malware in awaitly-analyze
The npm package awaitly-analyze was found to contain malware that grants full system compromise to attackers. Any system with this package installed should be considered fully compromised and all credentials rotated immediately from a different machine.
- Disclosed
- Last updated
- Blast radius
- Any system with awaitly-analyze installed
- Ecosystems
- Attack vectors
- Affected entities
- awaitly-analyzenpm package
The npm package awaitly-analyze was identified as containing malware. According to the GitHub Security Advisory (GHSA-hv34-4pjp-j28h), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised computer. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, given that the attacker may have gained full control of the system.\n\nUsers should treat any system that has had awaitly-analyze installed as potentially containing persistent malware and take appropriate incident response measures.
Indicators of compromise
- Packages
- awaitly-analyze
Remediation
- Immediately remove the awaitly-analyze package from all affected systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Perform a full security audit and malware scan of any system that had awaitly-analyze installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) as potentially compromised and plan for full reimaging if critical systems are involved
- Monitor for any suspicious activity on accounts that may have been accessed from compromised systems
Sources
- GitHub Advisory GHSA-hv34-4pjp-j28h · GitHub Advisory Database
Cite this entry
"Malware in awaitly-analyze." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 30, 2026; last updated June 30, 2026. https://supplychainattack.org/incident/malware-in-awaitly-analyze-in5v7w
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in autotel-subscribers
The npm package autotel-subscribers was found to contain malware that grants full system compromise to an outside entity. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
npmCompromised package - activecritical
Malware in ai-sdk-ollama
Malware discovered in the ai-sdk-ollama npm package. Systems with this package installed are considered fully compromised and require immediate remediation.
npmAI agents & skillsCompromised package - activecritical
Malware in autotel-eventcatalog
Malware was discovered in the npm package autotel-eventcatalog. Systems with this package installed or running should be considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in autotel-hono
Malware was discovered in the npm package autotel-hono. Systems with this package installed or running should be considered fully compromised and require immediate remediation.
npmCompromised package