Which versions of cursed-ecto-d3ab00 are malicious?

The following npm versions of cursed-ecto-d3ab00 are flagged malicious: 1.0.0, 1.0.1, 2.0.0, 2.0.1. Treat any of these as compromised.

How do I remediate cursed-ecto-d3ab00 if I installed it?

cursed-ecto-d3ab00 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 cursed-ecto-d3ab00 — how do I know if it already compromised me?

If cursed-ecto-d3ab00 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 cursed-ecto-d3ab00 part of a known attack campaign?

Yes — cursed-ecto-d3ab00 is associated with the IN-MAL-2026-009278, IN-MAL-2026-009279, IN-MAL-2026-009280, IN-MAL-2026-009281 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 cursed-ecto-d3ab00 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 cursed-ecto-d3ab00 (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cursed-ecto-d3ab00 across your stack and pipelines.

Malicious package

cursed-ecto-d3ab00npm

Malicious code in cursed-ecto-d3ab00 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10061

Immediate action

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

npm uninstall cursed-ecto-d3ab00

What this malware does

The package has no legitimate functionality (index.js is an empty module) and exists solely to run an install-time attack payload. All four lifecycle hooks (preinstall.js, install.js, postinstall.js, prepare.js) execute the same shell command via child_process.execSync that recursively scans host filesystem paths (/app, /opt, /root, /home, /srv, /data, /var, /etc, /tmp, /flag*, /) for HTB{...} flag patterns, enumerates flag-named files with their contents, captures env, hostname, id, and pwd, base64-encodes the collected data, and exfiltrates it via HTTPS GET to a hardcoded Cloudflare quick-tunnel endpoint at forward-amber-prairie-ruled.trycloudflare.com. In addition, each lifecycle script fans out HTTP PUT requests to internal hostnames and loopback ports (127.0.0.1:3000/8080/80/5000/4000 and hostnames app, web, frontend, console, ecto, registry, backend, nginx) targeting path /api/modules/ECT-839201 with a crafted ecto_module manifest named PWNED, attempting to register a malicious module on adjacent services reachable from the install environment. Behavior fires unconditionally on npm install.

Malicious versions

4 flagged

1.0.01.0.12.0.02.0.1

Indicators of compromise (SHA-256)

49348969de68b56d680a46f67f817053621fa41a5220d8cd0bc1da720e77a5a1

8b4c0c2a6e248fa594cf8df22a4d044dd1f7095ba8ce192696873dfd09e6988b

902284e51be8fd0017a0abe54daab11809653f3709fa641026ac865874934724

a14bae59a1f2886a17e3e4d3779514b06a895a224c1f196c9af83c81ebfd107c

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 cursed-ecto-d3ab00 (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cursed-ecto-d3ab00 across your stack and pipelines.
If you installed it — respond
cursed-ecto-d3ab00 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 cursed-ecto-d3ab00 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 cursed-ecto-d3ab00 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. cursed-ecto-d3ab00 on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 2.0.0, 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009278IN-MAL-2026-009279IN-MAL-2026-009280IN-MAL-2026-009281

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cursed-ecto-d3ab00-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