MAL-2026-14376 Malicious code in stillm4ddpocs-demo-sprocket (npm)
Malicious package
Published
MAL-2026-14376 is a malicious package: stillm4ddpocs-demo-sprocket (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-14376/ (Markdown: https://insights.sbomify.com/MAL-2026-14376/index.md)
- Package
- stillm4ddpocs-demo-sprocket
- Registry
- npm
What is MAL-2026-14376?
MAL-2026-14376 is a malicious package in stillm4ddpocs-demo-sprocket, published on 23 Aug 2026.
Official description
package.json declares scripts.preinstall = 'node index.js'. On install, index.js collects hostname, username, home directory, cwd, local IPv4, public IP (via api.ipify.org, icanhazip.com, ifconfig.me), DNS resolver information, and the consuming project's package.json fields (name, author, repository, homepage), then transmits the payload to the hardcoded callback host da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun. Transport uses HTTPS POST and HTTP POST to /poc/<uuid>, plus a covert DNS channel that hex-encodes the payload and issues chunked dns.resolve() queries embedding data in subdomain labels under the same host, explicitly to bypass egress filtering that blocks outbound HTTP. The package is published at version 999.9.12 and the README states this high version was chosen so npm resolves the public copy over any internal package of the same name — the canonical dependency-confusion attack shape. Any installer whose resolver falls through to the public registry has host identity and internal project metadata beaconed to a third-party callback with no opt-in.
What should I do about MAL-2026-14376?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.