# MAL-2026-15570: Malicious code in node-net-pool (npm)


- **Type:** Malicious package
- **Package:** `node-net-pool` (npm)
- **Published:** 29 Aug 2026
- **Also known as:** GHSA-vm9g-mp9v-6q5p

## What is MAL-2026-15570?

MAL-2026-15570 is a malicious package in node-net-pool, published on 29 Aug 2026. 

### Official description

package.json declares a postinstall hook (`node index.js`) that runs automatically on `npm install`. The shipped index.js contains no networking or connection-pool code — the entire file body is a ~6.3KB numeric byte array (`_s`) decoded by a custom LCG+XOR routine (`_d(a,k)` using state `p*0x41C64E6D+0x3039 & 0xFFFF` XORed byte-wise) and passed directly to `new Function(_d(_s,179))()`, dynamically evaluating the decoded payload on the installer's machine at install time. The manifest advertises the package as 'Node.js network connection pool utilities' with `main: index.js`, but index.js exports nothing and only runs the obfuscated executor — the stated purpose does not match the shipped contents. Install-time evaluation of an opaque, obfuscated payload with no legitimate build-step justification, combined with the cover-story metadata, is a supply-chain dropper/RCE pattern.

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

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-15570 is a malicious package: node-net-pool (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-15570/ (Markdown: https://insights.sbomify.com/MAL-2026-15570/index.md)
```

## Sources

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

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