# MAL-2026-5692: Malicious code in ecto-win-flag-q2m7 (npm)


- **Type:** Malicious package
- **Package:** `ecto-win-flag-q2m7` (npm)
- **Published:** 12 Jun 2026
- **Also known as:** GHSA-22wq-6mfh-69qv

## What is MAL-2026-5692?

MAL-2026-5692 is a malicious package in ecto-win-flag-q2m7, published on 12 Jun 2026. 

### Official description

On `npm install`, postinstall.js executes a harvest-and-exfiltrate chain against the installer's machine. It reads files under /app, /root, and /flag.txt, shells out via `execFileSync('/bin/sh', ['-c',...])` to recursively grep the filesystem for `HTB{...}` flag patterns and collect git history, gathers host identifiers (uid, cwd, hostname), and transmits the collected data via HTTP PUT to a hardcoded attacker endpoint at http://154.57.164.82:31250/api/modules/ECT-*. The script includes sandbox-evasion gating that exits cleanly when cwd contains `/tmp/npm-safe` or `/tmp/pkg`, or when hostname matches `nijin`, `hetzner`, or `ec2.internal` — ensuring the malicious path only fires on real installer machines. The combination of unconditional filesystem read, hardcoded non-registry IP destination, and scanner-evasion logic is an unambiguous supply-chain attack.

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-5692?

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-5692 is a malicious package: ecto-win-flag-q2m7 (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-5692/ (Markdown: https://insights.sbomify.com/MAL-2026-5692/index.md)
```

## Sources

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

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