Malicious code in dependencyfsdsfdsfg (npm)
A malicious npm package named dependencyfsdsfdsfg (version 99.9.0) was published as a dependency-confusion probe. The package contained a postinstall script that collected system information (username, hostname, working directory, and IPv4 addresses) and exfiltrated it to a Burp Collaborator out-of-band interaction domain.
- Disclosed
- Last updated
- Blast radius
- Any developer or CI/CD system that installed the malicious package version 99.9.0
- Ecosystems
- Attack vectors
- Affected entities
- dependencyfsdsfdsfg · 99.9.0
The npm package dependencyfsdsfdsfg version 99.9.0 contained malicious code designed to execute automatically upon installation. The package.json file declared a postinstall script that ran node index.js, which would execute without user interaction during npm install.
The index.js script performed reconnaissance by collecting sensitive system information: the installer's username (via whoami), system hostname, current working directory, and non-internal IPv4 addresses from network interfaces. This data was then exfiltrated via HTTPS GET requests to the hardcoded endpoint https://xghhv5sajm33m7krgi4n8my0mrsig84x.oastify.com, a Burp Collaborator out-of-band interaction domain used for testing and data exfiltration.
The package metadata strongly suggests this was a dependency-confusion probe: the name is gibberish, the version is suspiciously high (99.9.0), and the author, description, and keywords fields were empty. This pattern is typical of reconnaissance attacks designed to test whether internal package managers or development environments would install a malicious package with a similar name to legitimate dependencies.
The incident was identified and credited to the OpenSSF's malicious-packages repository, indicating it was detected and cataloged as part of ongoing supply chain security monitoring.
Indicators of compromise
- Packages
- dependencyfsdsfdsfg@99.9.0
- Domains
- xghhv5sajm33m7krgi4n8my0mrsig84x.oastify.com
Remediation
- Immediately uninstall dependencyfsdsfdsfg version 99.9.0 from all development machines and CI/CD systems
- Audit npm install logs to identify which systems or developers may have installed this package
- Review network logs for outbound HTTPS connections to xghhv5sajm33m7krgi4n8my0mrsig84x.oastify.com or similar Burp Collaborator domains
- Assume any system that installed this package may have had credentials or sensitive data exposed; consider rotating credentials and reviewing system access logs
- Implement npm package pinning and lock files to prevent accidental installation of unexpected versions
- Use npm audit and supply chain security tools to detect similar malicious packages
- Consider using private npm registries or package allowlists to prevent dependency-confusion attacks
Sources
- GitHub Advisory GHSA-5928-vc2p-hrqj · GitHub Advisory Database
Cite this entry
"Malicious code in dependencyfsdsfdsfg (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 11, 2026; last updated August 11, 2026. https://supplychainattack.org/incident/malicious-code-in-dependencyfsdsfdsfg-npm-7mt3mx
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in depcruise-wrap-stream-in-html (npm)
depcruise-wrap-stream-in-html@99.9.1 is a malicious npm package that mimics an internal helper of dependency-cruiser. It is a hollow package that downloads and executes arbitrary code from a Google Cloud Storage bucket during installation.
npmCompromised packageDependency confusionTyposquatting - resolvedcritical
Malicious code in fastly-vcl-language-client (npm)
The npm package fastly-vcl-language-client contained malicious code in a preinstall script that collected system information and CI environment variables, exfiltrating data to an external webhook endpoint. The package appears to be a dependency-confusion attack targeting internal Fastly tooling.
npmCompromised packageDependency confusion - containedcritical
Malicious code in @mexc/shared-utils (npm)
Malicious package @mexc/shared-utils published to npm without scope ownership, exploiting dependency-confusion to execute arbitrary code via postinstall hook. The payload collects host metadata and demonstrates install-time code execution against CI/build systems.
npmDependency confusionCompromised package - containedcritical
Malicious code in @polymarkets/clob-client-v2 (npm)
@polymarkets/clob-client-v2 (npm) is a malicious package that typosquats the legitimate @polymarket scope and redirects its inquirer dependency to a lookalike npm registry (registrynpmjs.to) to deliver arbitrary code execution during installation and on first require.
npmTyposquattingCompromised packageDependency confusion