Which versions of cache-swipper are malicious?

The following npm versions of cache-swipper are flagged malicious: 3.5.0, 3.6.0. Treat any of these as compromised.

How do I remediate cache-swipper if I installed it?

cache-swipper carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.

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

If cache-swipper 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-swipper part of a known attack campaign?

Yes — cache-swipper is associated with the IN-MAL-2026-020514, IN-MAL-2026-020515 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-swipper 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-swipper (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-swipper across your stack and pipelines.

Malicious package

cache-swippernpm

cache-swipper is a confirmed malicious npm package (MAL-2026-17166) that runs destructive / sabotage code (malicious versions 3.5.0, 3.6.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cache-swipper (npm)

MAL-2026-17166

Immediate action

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

npm uninstall cache-swipper

What this malware does

cache-swipper advertises itself as a safe cache and build-artifact cleanup utility, but the exported runOperation() function performs an unbounded recursive deletion of the caller's current working directory. On invocation the module makes an HTTPS request to the hardcoded endpoint https://testback-2aqe.onrender.com/can-cleanup and, if the remote response indicates the operation is allowed, iterates every entry under process.cwd() and calls fs.rmSync(target, {recursive:true, force:true}) on each one, excluding only index.js itself. No cache-specific paths, patterns, or allowlists are consulted. Identifiers are genericized (baseProcess, baseRemove, baseEntries, runOperation) and all console.log/console.error diagnostic output is commented out, so the destructive action produces no visible signal. The combination of a hardcoded remote kill-switch, indiscriminate recursive delete of the caller's working tree, and a misleading self-description gives the operator of testback-2aqe.onrender.com on-demand destructive control over any host that invokes this package.

Malicious versions

2 flagged

3.5.03.6.0

Indicators of compromise (SHA-256)

50cb98e5f107fe5bd1cd9434505219880014742674def9c64a8ce8552e04a626

54dd3ed65508b6cd4ee92edf62700a09abc1e742575661d1a8705efd62829c4e

Detection & response playbook

Destructive / sabotage

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cache-swipper (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-swipper across your stack and pipelines.
If you installed it — respond
cache-swipper carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.
Did it already run?
If cache-swipper 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-swipper 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-swipper on npm has been identified as a malicious package (versions 3.5.0, 3.6.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020514IN-MAL-2026-020515

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cache-swipper-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database