# MAL-2026-17308: Malicious code in mfahelper (npm)


- **Type:** Malicious package
- **Package:** `mfahelper` (npm)
- **Published:** 30 Sep 2026
- **Also known as:** GHSA-9f55-6cf9-3pgw

## What is MAL-2026-17308?

MAL-2026-17308 is a malicious package in mfahelper, published on 30 Sep 2026. 

### Official description

package.json declares its only runtime dependency, `node-net-pool`, as an https tarball pointing at the `main` branch of an unrelated GitHub account (`https://github.com/trktgq0wbre1/node-net-pool/archive/refs/heads/main.tar.gz`) — no version pin, no commit SHA, no integrity hash. `npm install` fetches whatever bytes currently live at that mutable URL and executes any lifecycle scripts they contain on the installer's machine. In addition, lib/cache.js runs `module.require('node-net-pool')` inside a swallowed try/catch at top level, so the third-party payload also loads when a consumer `require()`s the package, extending the code-execution surface beyond install time to any downstream import. The account owning the tarball URL is unrelated to the package publisher, so whoever controls that branch controls arbitrary code delivered to every installer.

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

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

## Sources

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

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