stillm4ddpocs-demo-sprocketnpm
Advisory published Updated
stillm4ddpocs-demo-sprocket is a confirmed malicious npm package (MAL-2026-14376) that opens a backdoor for remote access (malicious version 999.9.12). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in stillm4ddpocs-demo-sprocket (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for stillm4ddpocs-demo-sprocket (version 999.9.12).
If you installed it — respond
stillm4ddpocs-demo-sprocket establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If stillm4ddpocs-demo-sprocket was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks stillm4ddpocs-demo-sprocket-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.