Which versions of ecto_module are malicious?

The following npm versions of ecto_module are flagged malicious: 100.0.0. Treat any of these as compromised.

How do I remediate ecto_module if I installed it?

Remove ecto_module from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If ecto_module 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_module part of a known attack campaign?

Yes — ecto_module is associated with the IN-MAL-2026-006280, IN-MAL-2026-006279, GHSA-qj3m-j6gv-53pg 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_module 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_module (version 100.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ecto_module across your stack and pipelines.

Malicious package

ecto_modulenpm

ecto_module is a confirmed malicious npm package (MAL-2026-5726) that executes malicious code on install (malicious version 100.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ecto_module (npm)

MAL-2026-5726

Immediate action

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

npm uninstall ecto_module

What this malware does

On npm install, the package's preinstall hook (node index.js) reads /flag.txt (falling back to execSync('cat /flag*')) and transmits the captured contents in a JSON manifest field via HTTP PUT to a hardcoded endpoint at 127.0.0.1:3000/api/modules/ECT-987654. The package has no legitimate functionality — its description is simply 'Probe', it ships only index.js plus package.json, and the sole effect of installation is to read an installer-side file and ship it to whatever process is listening on the loopback port. This is a CTF/supply-chain probe payload: filesystem read + shell command execution + outbound HTTP, all auto-fired at install time.

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

1 flagged

100.0.0

Indicators of compromise (SHA-256)

581a4f4b080d517bbbebca62de5ce3f08b1bed05b57622132799f61b26389076

7e66c690abd94ee498cd359eb076451c0f6ea3956d8221616bbf8990d35a38c5

716a53c6e4c2c8319f2c08fc591f762c635e45684f35fb0c0f10e68bb95025ee

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ecto_module (version 100.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ecto_module across your stack and pipelines.
If you installed it — respond
Remove ecto_module from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If ecto_module 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_module 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_module on npm has been identified as a malicious package (version 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006280IN-MAL-2026-006279GHSA-qj3m-j6gv-53pg

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ecto_module-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database