ecto-spectral-leak-8d4e2npm
ecto-spectral-leak-8d4e2 is a confirmed malicious npm package (MAL-2026-5690) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ecto-spectral-leak-8d4e2 (npm)
What this malware does
On npm install, postinstall.js executes shell commands that enumerate AWS Secrets Manager across regions (aws secretsmanager list-secrets followed by get-secret-value for each secret), captures STS caller identity and S3 listings, reads /app/.env and /app/flag.txt, and dumps the full environment via env | sort. The collected JSON payload is PUT to http://154.57.164.71:31289/api/modules/ECT-472839 (line 9, line 89). An isRealTarget() gate (lines 40-48) suppresses execution under /tmp/, EC2 internal hostnames, hetzner hosts, and the username nijin, only firing for docker-style 12-hex hostnames inside /app/ or registries containing nexus.local/verdaccio — targeted evasion of analysis sandboxes while triggering on real CI environments and internal registries. This is a supply-chain credential-theft attack: installing the package surrenders the installer's AWS secrets and CI environment to attacker-controlled infrastructure.
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-spectral-leak-8d4e2 (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-spectral-leak-8d4e2 across your stack and pipelines.
If you installed it — respond
ecto-spectral-leak-8d4e2 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-spectral-leak-8d4e2 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-spectral-leak-8d4e2 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-spectral-leak-8d4e2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.