dust-helpers
This report shows the evidence for dust-helpers@9999.0.0, the only known version.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-12786 confirms this npm version as malicious.
Advisory
MAL-2026-12786
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in dust-helpers (npm)
Details
On `npm install`, the package's `preinstall` script runs `node callback.js`, which collects `os.hostname()`, `os.userInfo().username`, `process.cwd()`, `npm_config_registry`, and multiple CI repository-slug environment variables (GITHUB_REPOSITORY, CI_PROJECT_PATH, BUILD_REPOSITORY_NAME, and similar) and sends them as query-string parameters in an HTTP GET to the hardcoded endpoint `http://75.119.137.232:31337/depconfuse`. The package is published at version `9999.0.0` with a generic description and the exfil path is literally `/depconfuse`, matching the dependency-confusion reconnaissance pattern: publish a very-high-version squat of an internal-sounding name to the public registry so private builds that misresolve pick it up and identify themselves to the attacker. Installer identity, working directory, internal registry URL, and internal repository slugs leave the host to an attacker-controlled bare-IP endpoint at install time, enabling targeted follow-on supply-chain intrusion against the affected organization.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to dust-helpers@9999.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing dust-helpers@9999.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.