Which versions of checkmarx-claude-cache are malicious?

The following npm versions of checkmarx-claude-cache are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate checkmarx-claude-cache if I installed it?

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

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

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

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

Malicious package

checkmarx-claude-cachenpm

Malicious code in checkmarx-claude-cache (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6576

Immediate action

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

npm uninstall checkmarx-claude-cache

What this malware does

Package name and description impersonate the Checkmarx security vendor (checkmarx-claude-cache, "Checkmarx caching setup for Claude Fable access") but the package is not published under any Checkmarx-owned scope. bin/cli.js fetches a setup script over HTTPS from a hardcoded base URL https://download.east-1.us.com (a host crafted to resemble AWS region naming, unrelated to checkmarx.com) at /release/windows/install or /release/mac/install, then pipes the response body directly into an interpreter via execSync("powershell -NoProfile -NonInteractive -Command -", { input: script }) on Windows or execSync("bash", { input: script }) elsewhere. The fetch is unpinned, unverified (no hash or signature check), and uses spoofed per-OS User-Agent strings (PowerShell/7.4.0 on Windows, curl/8.4.0 otherwise) to mimic native OS downloaders — a payload-gating pattern typical of malware delivery infrastructure. Running the CLI executes arbitrary attacker-controlled code on the installer's machine.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4cbdcac8329a6ad9662ef7af8e0f68cd616f5451dc0a1fce9d2bcab5a7943c8a

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 checkmarx-claude-cache (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkmarx-claude-cache across your stack and pipelines.
If you installed it — respond
checkmarx-claude-cache is a typosquat — you almost certainly intended a legitimately-named package. Remove checkmarx-claude-cache, 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 checkmarx-claude-cache 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 checkmarx-claude-cache 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. checkmarx-claude-cache on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007761

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks checkmarx-claude-cache-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