ecto_module
This report shows the evidence for ecto_module@100.0.0, the only known version.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-5726 confirms this npm version as malicious.
Advisory
MAL-2026-5726
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in ecto_module (npm)
Details
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.
## Source: ghsa-malware (716a53c6e4c2c8319f2c08fc591f762c635e45684f35fb0c0f10e68bb95025ee) 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.
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to ecto_module@100.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing ecto_module@100.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.