MAL-2026-17775 Malicious code in nitro-cjs-requirer (npm)
Malicious package
Published
MAL-2026-17775 is a malicious package: nitro-cjs-requirer (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-17775/ (Markdown: https://insights.sbomify.com/MAL-2026-17775/index.md)
- Package
- nitro-cjs-requirer
- Registry
- npm
What is MAL-2026-17775?
MAL-2026-17775 is a malicious package in nitro-cjs-requirer, published on 11 Oct 2026.
Official description
The package is a beacon carrier with no real functionality. The declared postinstall script runs beacon.cjs, which POSTs the package name, os.hostname(), __dirname install path, process.cwd(), and node version to the hardcoded bare-IP, plain-HTTP endpoint http://185.158.107.175:8787/_ah/dc. The same fire() call is also invoked at module load from index.js, which otherwise exports a Proxy returning no-op functions for every property so the module appears to be a compatibility shim. Installer host identifiers are therefore sent unconditionally both at npm install (via the postinstall lifecycle hook) and on require(), to a bare-IP endpoint unrelated to any publisher, with no caller opt-in and no documented purpose. The shape — hollow stub module, dual install-time and require-time beacon trigger, hardcoded bare-IP over plain HTTP, host/path/cwd identifiers — is a dependency-confusion or build-pipeline reconnaissance probe.
What should I do about MAL-2026-17775?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.