MAL-2026-17292 Malicious code in @selfpentest/bin-confusion (npm)
Malicious package
Published
MAL-2026-17292 is a malicious package: @selfpentest/bin-confusion (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-17292/ (Markdown: https://insights.sbomify.com/MAL-2026-17292/index.md)
- Package
- @selfpentest/bin-confusion
- Registry
- npm
What is MAL-2026-17292?
MAL-2026-17292 is a malicious package in @selfpentest/bin-confusion, published on 29 Sep 2026.
Official description
package.json registers a
bin entry named npm pointing at npm.js, deliberately colliding with the core npm CLI. Once this package is installed as a dependency, any npm... invocation in a consuming project's scripts resolves via node_modules/.bin to this shim, executing the shipped code before (or instead of) the real npm. npm.js contains a steal() routine that reads process.env.HOME, process.env.SECRET, and the first 30 bytes of ~/.ssh/known_hosts, concatenates them into a query string, and issues a fetch GET to http://localhost:1337/. The destination is loopback in this build, but the collected data (installer SSH known_hosts contents and environment secrets) is packaged into a functioning exfiltration primitive that fires whenever the shadow npm shim is invoked from the installer's build scripts. The scope name (@selfpentest) and README frame this as a demonstration, but the shipped tarball is a working bin-shadow + credential-read + network-send chain against installers who add it as a dependency.What should I do about MAL-2026-17292?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.