Malicious code in aedes_clusters (npm)
The npm package aedes_clusters contained malicious code in a preinstall hook that performed host reconnaissance and exfiltrated system data to an attacker-controlled Burp Collaborator endpoint. The package had no legitimate functionality and was designed solely for data collection and exfiltration.
- Disclosed
- Last updated
- Blast radius
- Any developer or system that installed the malicious aedes_clusters package from npm
- Ecosystems
- Attack vectors
- Affected entities
- aedes_clustersnpm package containing malicious preinstall hook
The npm package aedes_clusters was found to contain malicious code executed via a preinstall hook in package.json. Upon installation, the hook automatically runs node index.js, which performs host reconnaissance and data exfiltration without user consent or knowledge.\n\nThe malicious index.js script collects sensitive host information including hostname, username, home directory path, and DNS server configuration. It also reads local system files such as /etc/passwd and /etc/hosts. All collected data is then exfiltrated via HTTPS POST requests to a hardcoded Burp Collaborator subdomain (b5hv16nakzo45px5ga4ukkum8de52vqk.oastify.com), which is an attacker-controlled out-of-band interaction service commonly used for data exfiltration.\n\nThe package contained no legitimate functionality; its sole purpose was host reconnaissance and data exfiltration at install time. The incident was identified and credited to the OpenSSF malicious-packages repository.
Indicators of compromise
- Packages
- aedes_clusters
- Domains
- b5hv16nakzo45px5ga4ukkum8de52vqk.oastify.com
Remediation
- Immediately uninstall aedes_clusters from all systems where it was installed
- Audit npm install logs to identify all systems that may have installed this package
- Assume compromise of any system that installed aedes_clusters; review for unauthorized access and data exfiltration
- Change credentials and SSH keys on affected systems
- Monitor network traffic for connections to b5hv16nakzo45px5ga4ukkum8de52vqk.oastify.com and related Burp Collaborator domains
- Review /etc/passwd, /etc/hosts, and DNS configuration files for unauthorized modifications
- Use npm audit to check for other malicious packages in your dependency tree
- Consider implementing package signature verification and allowlisting for npm dependencies
Sources
- GitHub Advisory GHSA-ccmc-q8x3-v382 · GitHub Advisory Database
Cite this entry
"Malicious code in aedes_clusters (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malicious-code-in-aedes-clusters-npm-mqhaya
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 svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - 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
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 - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package