nitro-bundled-dep@1.0.0
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 11d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-17774 confirms this npm version as malicious.
Advisory
MAL-2026-17774
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in nitro-bundled-dep (npm)
Details
The npm package nitro-bundled-dep@0.0.1 presents itself as a 'Compatibility shim' but ships a beacon that POSTs installer host metadata — hostname, install path, current working directory, and Node version — to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc over plain HTTP. The beacon in beacon.cjs is invoked from package.json's postinstall script, so it fires automatically on `npm install`, and is also invoked from index.js so it fires again whenever the module is required. The main module exports a Proxy that returns no-op functions for any property access, allowing a victim build that imports this name to continue without errors after the beacon has executed — the shape of a dependency-confusion / name-squat payload whose purpose is to confirm successful code execution inside a target build environment and report host identifiers to an attacker-controlled collector.
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 nitro-bundled-dep@1.0.0.
The same advisory and Firewall decision cover 5 recorded versions
1.1.0, 2.0.1, 99.0.1, 0.0.1, 1.0.0
See all versions of nitro-bundled-dep for other recorded verdicts.
- Avoid installing nitro-bundled-dep@1.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.