# MAL-2026-5690: Malicious code in ecto-spectral-leak-8d4e2 (npm)


- **Type:** Malicious package
- **Package:** `ecto-spectral-leak-8d4e2` (npm)
- **Published:** 12 Jun 2026
- **Also known as:** GHSA-jmpq-jp85-ggf3

## What is MAL-2026-5690?

MAL-2026-5690 is a malicious package in ecto-spectral-leak-8d4e2, published on 12 Jun 2026. 

### Official description

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.

## What should I do about MAL-2026-5690?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5690 is a malicious package: ecto-spectral-leak-8d4e2 (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-5690/ (Markdown: https://insights.sbomify.com/MAL-2026-5690/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5690

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5690/
Summaries are generated and may contain mistakes; the official description above is the record.