Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@chatclub/claude-codenpm

@chatclub/claude-code is a confirmed malicious npm package (MAL-2025-49379) that executes malicious code on install (malicious versions 0.0.1, 2.0.27, 2.0.28…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @chatclub/claude-code (npm)

MAL-2025-49379
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @chatclub/claude-code

What this malware does

The package @chatclub/claude-code was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

7 flagged
0.0.12.0.272.0.282.0.292.0.302.0.312.0.34

Indicators of compromise (SHA-256)

da13a60429421be7439a95fd58ec042a791155d10525b45dff395464f7ae851f
b6acfccb78a615c7f037fe5dbd1001d9a77ca4015c89c94122ba5dd78978b66b
04dd782a81b871234f2938c8a7ed44207d0a0e6bc80be6e8912766f843962fd6

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove @chatclub/claude-code from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @chatclub/claude-code 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.

  4. How O3 protects you

    O3 blocks @chatclub/claude-code 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. @chatclub/claude-code on npm has been identified as a malicious package (versions 0.0.1, 2.0.27, 2.0.28, 2.0.29, 2.0.30, 2.0.31, 2.0.34 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w7jq-xv2w-v96wRLMA-2025-06016

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @chatclub/claude-code-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.

Explore

@chatclub/claude-code (npm) malicious package — MAL-2025-49379 | O3 Security