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
- resolvedcritical
Malicious code in rust-testing-utils (npm)
The npm package rust-testing-utils contained malicious code that impersonates the pino logger and executes remotely-fetched code with arbitrary privileges. The package spawns a child process that decodes a hardcoded URL, fetches attacker-controlled content, and executes it via Function constructor with full module-loading capability.
npmCompromised packageMalicious commit - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malware in hydration-dim-kit
Malware was discovered in the npm package hydration-dim-kit. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package