Which versions of aedes_clusters are malicious?

The following npm versions of aedes_clusters are flagged malicious: 1.0.1, 1.1.1. Treat any of these as compromised.

How do I remediate aedes_clusters if I installed it?

aedes_clusters is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed aedes_clusters — how do I know if it already compromised me?

If aedes_clusters was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is aedes_clusters part of a known attack campaign?

Yes — aedes_clusters is associated with the IN-MAL-2026-011492, GHSA-8m4c-fp49-4pw5, IN-MAL-2026-019764 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find aedes_clusters across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aedes_clusters (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aedes_clusters across your stack and pipelines.

Malicious package

aedes_clustersnpm

aedes_clusters is a confirmed malicious npm package (MAL-2026-12033) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aedes_clusters (npm)

MAL-2026-12033

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall aedes_clusters

What this malware does

The package's package.json declares a preinstall: node index.js hook that fires automatically on npm install. index.js collects host reconnaissance data (os.hostname(), os.userInfo().username, home directory, DNS server configuration) and reads local system files including /etc/passwd and /etc/hosts, then HTTPS-POSTs the collected data to the hardcoded Burp Collaborator subdomain b5hv16nakzo45px5ga4ukkum8de52vqk.oastify.com. oastify.com is Burp Suite's out-of-band interaction service, commonly used as an attacker-controlled exfiltration sink. There is no legitimate functionality; the package's sole install-time behavior is host recon and data exfiltration.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

1.0.11.1.1

Indicators of compromise (SHA-256)

6f0750fab7cca2996255b57d6fa98107b2d6b710fc8ab62f30345158ff3b7560

5565c48664cc492f92e8c0cf8b877af2e14076c6538b0b13216ee4e079616266

578f5b6800c67bc33d7db7439eb052b21973c473556c44f1e3b0ff78fb5287d7

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aedes_clusters (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aedes_clusters across your stack and pipelines.
If you installed it — respond
aedes_clusters is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If aedes_clusters was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks aedes_clusters before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. aedes_clusters on npm has been identified as a malicious package (versions 1.0.1, 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011492GHSA-8m4c-fp49-4pw5IN-MAL-2026-019764

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks aedes_clusters-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database