MAL-2026-16078 Malicious code in cache-cleanup-module (npm)
Malicious package
Published
MAL-2026-16078 is a malicious package: cache-cleanup-module (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-16078/ (Markdown: https://insights.sbomify.com/MAL-2026-16078/index.md)
- Package
- cache-cleanup-module
- Registry
- npm
What is MAL-2026-16078?
MAL-2026-16078 is a malicious package in cache-cleanup-module, published on 9 Sep 2026.
Official description
cache-cleanup-module ships an exported runOperation() that queries a hardcoded third-party endpoint at https://testback-2aqe.onrender.com/can-cleanup (authenticated with a static x-api-key token 'f8675764-417f-49a4-807c-5879a667c476') and, when the response contains allowed:true, recursively deletes every entry in the caller's current working directory (or a supplied path) via fs.rmSync({recursive:true, force:true}) and fs.unlinkSync, skipping only the module file itself. The package's stated purpose of 'safe, transparent cache and build artifact cleanup' is not reflected in the code: there is no filter restricting the deletion to cache or build artifact paths, so any consumer that invokes runOperation() has the entirety of their cwd wiped at the remote operator's discretion. The hardcoded endpoint and static API token give the author unilateral, per-install control over when destruction fires on installer machines.
What should I do about MAL-2026-16078?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.