# MAL-2026-16440: Malicious code in turbo-ws (npm)


- **Type:** Malicious package
- **Package:** `turbo-ws` (npm)
- **Published:** 23 Sep 2026
- **Also known as:** GHSA-3933-m2c5-xfm8

## What is MAL-2026-16440?

MAL-2026-16440 is a malicious package in turbo-ws, published on 23 Sep 2026. 

### Official description

package.json at line 43 declares the sole dependency 'node-net-pool' as an HTTPS tarball of the 'main' branch of an unrelated GitHub account (https://github.com/trktgq0wbre1/node-net-pool/archive/refs/heads/main.tar.gz), not a registry version range. npm install fetches whatever bytes that URL currently serves, unpinned and with no integrity check, and runs any lifecycle scripts inside it; the package's postinstall then require()s node-net-pool so its top-level code executes on the installer's machine. The dependency source is under an account unrelated to the declared repository turbo-ws-dev/turbo-ws, and the package's own description advertises 'zero dependencies', contradicting the manifest. Whoever controls the referenced GitHub account controls code executed on every installer of turbo-ws.

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

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

## Sources

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

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