Which versions of ecto-corsair-flag-7kq3mz are malicious?

The following npm versions of ecto-corsair-flag-7kq3mz are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate ecto-corsair-flag-7kq3mz if I installed it?

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

If ecto-corsair-flag-7kq3mz 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 ecto-corsair-flag-7kq3mz part of a known attack campaign?

Yes — ecto-corsair-flag-7kq3mz is associated with the IN-MAL-2026-007821, IN-MAL-2026-007822, IN-MAL-2026-007823 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 ecto-corsair-flag-7kq3mz 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 ecto-corsair-flag-7kq3mz (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ecto-corsair-flag-7kq3mz across your stack and pipelines.

Malicious package

ecto-corsair-flag-7kq3mznpm

Malicious code in ecto-corsair-flag-7kq3mz (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6699

Immediate action

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

npm uninstall ecto-corsair-flag-7kq3mz

What this malware does

Package wires preinstall, install, and postinstall lifecycle hooks to run postinstall.js, which executes unconditionally on npm install. The script collects hostname, cwd, uid, and environment variables matching FLAG/CTF/NPM/REGISTRY/CI/GITHUB/RUNNER, reads candidate flag files, and uses child_process.execSync to recursively grep installer-side directories (/app, /workspace, /challenge, /home/runner/work/repo/repo,.,..,../..) for flag-shaped strings. The collected manifest is base64-encoded and PUT to http://154.57.164.76:30728/api/modules/<id>, with an additional GET beacon to webhook.site/755defab-ea42-4c1f-9804-43ec567439f5. postinstall.js also tests npm_config_registry against /verdaccio/i to detect successful dependency-confusion landings, and the shipped publish-and-arm.sh and README self-describe the package as an 'armed' dependency-confusion probe. Regardless of the CTF/probe framing, installing this package causes unconsented exfiltration of installer environment and filesystem contents to an attacker-controlled IP.

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

2a4dfa9f4805e5b44c7ccf3e4c3859abf8e9f0388f11e3daf6065f43c49e09ed

54d9460656276821368471252c6a7b1c42dc2fdfd89432aa796d71d5463a1fc7

b18aadaf5087b19b63d12456642141e5bfff9146bf1bf4fcfb11eed833b8c78c

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

Campaign

IN-MAL-2026-007821IN-MAL-2026-007822IN-MAL-2026-007823

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ecto-corsair-flag-7kq3mz-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