ecto-flag-read-m7p2npm
ecto-flag-read-m7p2 is a confirmed malicious npm package (MAL-2026-5687) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ecto-flag-read-m7p2 (npm)
What this malware does
The package's postinstall.js imports child_process and references HTTP GET calls and hostname lookups during the install lifecycle. The co-occurrence of these primitives in an install-time script is a known shape for both legitimate behavior (CTF/flag-read demos, hostname reporting, telemetry) and exfiltration/dropper attacks, but the available evidence does not show the destination URL, the data being sent, or whether fetched content is executed. The package name ("ecto-flag-read") and small file count are consistent with a CTF or test artifact rather than a recognized library, but intent cannot be confirmed from the current evidence alone. A human reviewer should inspect postinstall.js to determine whether it exfiltrates installer data or executes remote content before this version is allowed in production installs.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ecto-flag-read-m7p2 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ecto-flag-read-m7p2 across your stack and pipelines.
If you installed it — respond
ecto-flag-read-m7p2 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-flag-read-m7p2 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-flag-read-m7p2 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks ecto-flag-read-m7p2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.