Which versions of cache-manager are malicious?

The following npm versions of cache-manager are flagged malicious: 7.2.10. Treat any of these as compromised.

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

cache-manager is a typosquat — you almost certainly intended a legitimately-named package. Remove cache-manager, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

Yes — cache-manager is associated with the IN-MAL-2026-010973 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-manager 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-manager (version 7.2.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cache-manager across your stack and pipelines.

Malicious package

cache-managernpm

cache-manager is a confirmed malicious npm package (MAL-2026-11523) that typosquats a legitimate package to trick installs (malicious version 7.2.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cache-manager (npm)

MAL-2026-11523

Immediate action

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

npm uninstall cache-manager

What this malware does

This tarball, published under the popular cache-manager name, ships an obfuscated preinstall dropper that does not exist in the upstream project. package.json declares "preinstall": "node setup.mjs", and setup.mjs is a single-line obfuscator.io-style bundle (string-array + RC4-style per-call decoder at i['tXsWiG']) that hides every URL, filename, and command literal. Decoding reveals the loader detects the host platform, downloads a matching Bun runtime archive from github.com/oven-sh/bun/releases (e.g. bun-linux-x64-baseline, bun-windows-x64-baseline), extracts it to a temp directory, marks it executable, and then invokes that freshly downloaded runtime via execFileSync against the sibling file Math_Symbol.js. Math_Symbol.js is a 727 KB // @bun @bun-cjs-tagged opaque bundle with hex-obfuscated identifiers and its own string-array decoder; it is not referenced by the package's advertised entry point (dist/index.cjs) and is only reachable through the preinstall dropper. The alternate-runtime aspect (executing under Bun rather than Node) ensures the terminal payload is not observable to Node-based scanning of the tarball. The upstream cache-manager package ships no preinstall, no setup.mjs, and no Math_Symbol.js, so this version is a supply-chain compromise or lookalike rather than a legitimate release. Installing this version causes attacker-controlled code to execute on the installer's machine at npm install time.

Malicious versions

1 flagged

7.2.10

Indicators of compromise (SHA-256)

5a3d9e70c3e6f7e6c10d38a9f9e1d29bfea7c026fe7c5329c5817267bf4b759d

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cache-manager (version 7.2.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cache-manager across your stack and pipelines.
If you installed it — respond
cache-manager is a typosquat — you almost certainly intended a legitimately-named package. Remove cache-manager, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If cache-manager 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-manager 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-manager on npm has been identified as a malicious package (version 7.2.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010973

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cache-manager-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