Which versions of stillm4ddpocs-demo-sprocket are malicious?

The following npm versions of stillm4ddpocs-demo-sprocket are flagged malicious: 999.9.12. Treat any of these as compromised.

How do I remediate stillm4ddpocs-demo-sprocket if I installed it?

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.

I already installed stillm4ddpocs-demo-sprocket — how do I know if it already compromised me?

If stillm4ddpocs-demo-sprocket was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is stillm4ddpocs-demo-sprocket part of a known attack campaign?

Yes — stillm4ddpocs-demo-sprocket is associated with the IN-MAL-2026-018560 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find stillm4ddpocs-demo-sprocket across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for stillm4ddpocs-demo-sprocket (version 999.9.12). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stillm4ddpocs-demo-sprocket across your stack and pipelines.

Malicious package

stillm4ddpocs-demo-sprocketnpm

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)

MAL-2026-14376

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall stillm4ddpocs-demo-sprocket

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

1 flagged

999.9.12

Indicators of compromise (SHA-256)

ced86462ad99b91f0f3e3d344e008ca911a1dccdad5c928cee5da5c651756f1d

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for stillm4ddpocs-demo-sprocket (version 999.9.12). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stillm4ddpocs-demo-sprocket across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks stillm4ddpocs-demo-sprocket before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. stillm4ddpocs-demo-sprocket on npm has been identified as a malicious package (version 999.9.12 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018560

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database