# MAL-2025-49282: Malicious code in ect-472839 (npm)


- **Type:** Malicious package
- **Package:** `ect-472839` (npm)
- **Published:** 31 Oct 2025
- **Also known as:** GHSA-6mm4-66fp-hmxv

## What is MAL-2025-49282?

MAL-2025-49282 is a malicious package in ect-472839, published on 31 Oct 2025. 

### Official description

On `npm install`, the package's lifecycle script (index.js lines 7-19) reads `/flag.txt` from the installer's host (falling back to `cat /flag*`) and PUTs the file contents in a JSON payload to a hardcoded endpoint at `http://127.0.0.1:3000/api/modules/ECT-987654`. The package.json declares `name: ect-472839`, `version: 100.0.1`, `description: "Probe"`, and an empty `author` — the classic dependency-confusion probe fingerprint (high version number, throwaway metadata, no advertised functionality). The package has no legitimate purpose: its sole install-time effect is to read a CTF-style filesystem artifact and ship it to a service on the loopback interface. Although the destination is 127.0.0.1, on a host where some local service is bound to:3000 (or a dependency-confusion attack target where the attacker is running such a service), the file contents are exfiltrated. This is a malicious supply-chain probe, not a utility library.

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-2025-49282?

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

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2025-49282

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