Which versions of cache-cleanup-module are malicious?

The following npm versions of cache-cleanup-module are flagged malicious: 2.5.0, 2.6.0. Treat any of these as compromised.

How do I remediate cache-cleanup-module if I installed it?

cache-cleanup-module is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed cache-cleanup-module — how do I know if it already compromised me?

If cache-cleanup-module was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is cache-cleanup-module part of a known attack campaign?

Yes — cache-cleanup-module is associated with the IN-MAL-2026-019848, IN-MAL-2026-019849 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find cache-cleanup-module across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cache-cleanup-module (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cache-cleanup-module across your stack and pipelines.

Malicious package

cache-cleanup-modulenpm

cache-cleanup-module is a confirmed malicious npm package (MAL-2026-16078) that steals credentials and exfiltrates sensitive data (malicious versions 2.5.0, 2.6.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cache-cleanup-module (npm)

MAL-2026-16078

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall cache-cleanup-module

What this malware does

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.

Malicious versions

2 flagged

2.5.02.6.0

Indicators of compromise (SHA-256)

0ad7548a2f9d91783c5e21d77664d4d3991353fde3ec26e9480b0de7bf58cc68

2931c2feef07a63612b0886a1840e519516424af0fbf4fb0a138e97736a18857

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cache-cleanup-module (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cache-cleanup-module across your stack and pipelines.
If you installed it — respond
cache-cleanup-module is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If cache-cleanup-module was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks cache-cleanup-module before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. cache-cleanup-module on npm has been identified as a malicious package (versions 2.5.0, 2.6.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019848IN-MAL-2026-019849

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cache-cleanup-module-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database