MAL-2026-17773 Malicious code in nested-lib (npm)
Malicious package
Published
MAL-2026-17773 is a malicious package: nested-lib (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-17773/ (Markdown: https://insights.sbomify.com/MAL-2026-17773/index.md)
- Package
- nested-lib
- Registry
- npm
What is MAL-2026-17773?
MAL-2026-17773 is a malicious package in nested-lib, published on 11 Oct 2026.
Official description
The package declares
scripts.postinstall = "node beacon.cjs" and index.js also invokes require('./beacon.cjs').fire() at module load. beacon.cjs POSTs a JSON payload containing os.hostname(), __dirname, process.cwd(), and process.version over plain HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The destination is not a documented first-party service and the host identifiers are sent without any opt-in. index.js otherwise exports a Proxy that returns no-op functions for every property access, so the package provides no real functionality — its sole on-install and on-require effect is the beacon. The combination of a hollow Proxy shim, a bare-IP plain-HTTP destination, and automatic firing from both the npm lifecycle hook and the main module is consistent with a reconnaissance/confirmation beacon used to validate successful installation into target environments, typically preceding a second-stage payload.What should I do about MAL-2026-17773?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.