MAL-2026-17769 Malicious code in deposit-limit-fe (npm)
Malicious package
Published
MAL-2026-17769 is a malicious package: deposit-limit-fe (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-17769/ (Markdown: https://insights.sbomify.com/MAL-2026-17769/index.md)
- Package
- deposit-limit-fe
- Registry
- npm
What is MAL-2026-17769?
MAL-2026-17769 is a malicious package in deposit-limit-fe, published on 11 Oct 2026.
Official description
[email protected] 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.What should I do about MAL-2026-17769?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.