Which versions of anthropic-claude-latest are malicious?

The following npm versions of anthropic-claude-latest are flagged malicious: 4.7.1, 4.7.2, 4.7.3. Treat any of these as compromised.

How do I remediate anthropic-claude-latest if I installed it?

anthropic-claude-latest 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 anthropic-claude-latest — how do I know if it already compromised me?

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

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

Malicious package

anthropic-claude-latestnpm

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

MAL-2026-6415

Immediate action

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

npm uninstall anthropic-claude-latest

What this malware does

Package anthropic-claude-latest claims to be an 'Official Anthropic Claude SDK wrapper' but ships no Anthropic SDK code; the README is for an unrelated package cachesync-helper. On construction of the exported CacheSync / createCache, a _warmup routine schedules _prefetch after a 3-7 second random delay. _prefetch opens a TLS connection (with rejectUnauthorized: false) to one of four hardcoded IPs (104.194.134.33, 104.194.133.89, 107.189.20.82, 107.189.20.146:8443), receives base64-encoded files, and writes them to OS-camouflaged directories (~/Library/Application Support/com.apple.security, ~/.local/share/prometheus, %LOCALAPPDATA%\Microsoft\Windows Security\Health). The package then runs pip install --quiet --disable-pip-version-check for wallet/seed-phrase libraries (bip-utils, mnemonic, eth-account) and spawns python3 main.py detached with Object.assign({}, process.env, { _INTERNAL: '1' }) — handing the entire installer environment (AWS/GCP/NPM/SSH credentials, etc.) to the attacker-controlled payload. A .cs_v2 marker file is written for persistence gating. All sensitive identifiers (child_process, execFileSync, spawn, module.constructor._load, base64, python3, main.py) are split into [...].join('') arrays at lib/index.js to evade static scanners. This is a typosquat-lure remote code execution dropper targeting developers searching for Anthropic Claude SDKs.

Malicious versions

3 flagged

4.7.14.7.24.7.3

Indicators of compromise (SHA-256)

0409a90789c287d47e5345fc538401de2ff5ae005869658cfd13e7689430ac8a

39eab369e2498da827d3bbd331effdf24b99ab28961e62da7328e4476e328876

f30b9269e6c907bd609a185f87cb47c1acba2ef2712421766ca15ac16bf403f1

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 anthropic-claude-latest (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging anthropic-claude-latest across your stack and pipelines.
If you installed it — respond
anthropic-claude-latest 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 anthropic-claude-latest 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 anthropic-claude-latest 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. anthropic-claude-latest on npm has been identified as a malicious package (versions 4.7.1, 4.7.2, 4.7.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007457IN-MAL-2026-007456IN-MAL-2026-007455

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks anthropic-claude-latest-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