deposit-limit-fe@100.100.102
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 12d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-17769 confirms this npm version as malicious.
Advisory
MAL-2026-17769
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in deposit-limit-fe (npm)
Details
deposit-limit-fe@100.100.101 is published as a 'Deposit limit frontend utilities' library but its main entry (index.js) exports an empty object and ships no real functionality. package.json declares `postinstall: node postinstall.js`, which require()s a bundled Linux x64 native addon at `prebuilds/linux-x64/addon.node` inside a silenced try/catch. The addon has no corresponding C/C++ source or binding.gyp in the tarball. On load it reads the environment variables HOSTNAME, USER, npm_package_name, and npm_config_registry, forks, opens a TCP socket to the hardcoded bare IP 64.181.165.115, and sends `POST /dc HTTP/1.0` with a form-encoded body `h=<hostname>&p=<package>&u=<user>&r=<registry>`. The anomalous 100.100.101 version and the explicit exfiltration of `npm_config_registry` are the fingerprint of a dependency-confusion reconnaissance beacon targeting an internal/private npm registry package name. Installing this package automatically leaks the installer's hostname, OS username, and private npm registry URL to an attacker-controlled endpoint and executes opaque native code on the installer's machine.
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 deposit-limit-fe@100.100.102.
The same advisory and Firewall decision cover 3 recorded versions
100.100.101, 100.100.102, 100.100.106
See all versions of deposit-limit-fe for other recorded verdicts.
- Avoid installing deposit-limit-fe@100.100.102. 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.