Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that executes during installation. It collects sensitive host and project metadata, including hostname, username, directory paths, IP addresses, DNS resolver info, and package.json fields, then exfiltrates this data to a hardcoded external server using HTTPS, HTTP, and covert DNS channels designed to bypass egress filtering. The package uses a high version number to facilitate a dependency confusion attack, causing npm to resolve the public malicious package over internal versions without user consent.
AI Analysis
Technical Summary
The stillm4ddpocs-demo-sprocket npm package at version 999.9.12 declares a preinstall script that runs index.js on installation. This script gathers detailed environment and project metadata and transmits it to a hardcoded callback domain via multiple channels, including HTTPS POST, HTTP POST, and a covert DNS exfiltration method that encodes data in DNS queries to evade network filtering. The package's README confirms the use of a high version number to exploit dependency confusion, causing unintended installation of this malicious package when internal resolvers fail. This results in unauthorized data leakage without user opt-in.
Potential Impact
Sensitive host identity and internal project metadata are exfiltrated to a third-party server without user consent. This can lead to privacy violations, information disclosure about internal projects, and potential reconnaissance for further attacks. The use of covert DNS channels indicates an attempt to bypass network egress controls, increasing the risk of unnoticed data leakage.
Mitigation Recommendations
No official patch or fix is available for this malicious package. The recommended mitigation is to avoid installing the stillm4ddpocs-demo-sprocket package at version 999.9.12 from public npm registries. Organizations should audit their dependency resolution configurations to prevent dependency confusion attacks by ensuring internal packages are properly scoped and prioritized. Monitoring and blocking outbound connections to suspicious domains such as da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun can help detect or prevent data exfiltration attempts.
Malicious code in stillm4ddpocs-demo-sprocket (npm)
Description
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that executes during installation. It collects sensitive host and project metadata, including hostname, username, directory paths, IP addresses, DNS resolver info, and package.json fields, then exfiltrates this data to a hardcoded external server using HTTPS, HTTP, and covert DNS channels designed to bypass egress filtering. The package uses a high version number to facilitate a dependency confusion attack, causing npm to resolve the public malicious package over internal versions without user consent.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The stillm4ddpocs-demo-sprocket npm package at version 999.9.12 declares a preinstall script that runs index.js on installation. This script gathers detailed environment and project metadata and transmits it to a hardcoded callback domain via multiple channels, including HTTPS POST, HTTP POST, and a covert DNS exfiltration method that encodes data in DNS queries to evade network filtering. The package's README confirms the use of a high version number to exploit dependency confusion, causing unintended installation of this malicious package when internal resolvers fail. This results in unauthorized data leakage without user opt-in.
Potential Impact
Sensitive host identity and internal project metadata are exfiltrated to a third-party server without user consent. This can lead to privacy violations, information disclosure about internal projects, and potential reconnaissance for further attacks. The use of covert DNS channels indicates an attempt to bypass network egress controls, increasing the risk of unnoticed data leakage.
Mitigation Recommendations
No official patch or fix is available for this malicious package. The recommended mitigation is to avoid installing the stillm4ddpocs-demo-sprocket package at version 999.9.12 from public npm registries. Organizations should audit their dependency resolution configurations to prevent dependency confusion attacks by ensuring internal packages are properly scoped and prioritized. Monitoring and blocking outbound connections to suspicious domains such as da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun can help detect or prevent data exfiltration attempts.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-14376
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8af9a3acd9273b49f32efd
Added to database: 08/23/2026, 13:46:11 UTC
Last enriched: 08/23/2026, 13:50:37 UTC
Last updated: 08/23/2026, 23:11:10 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.