Which versions of ckcc-protocol are malicious?

The following npm versions of ckcc-protocol are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate ckcc-protocol if I installed it?

ckcc-protocol 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 ckcc-protocol — how do I know if it already compromised me?

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

Yes — ckcc-protocol is associated with the IN-MAL-2026-013408, IN-MAL-2026-013412, IN-MAL-2026-013428, IN-MAL-2026-013420 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 ckcc-protocol 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 ckcc-protocol (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ckcc-protocol across your stack and pipelines.

Malicious package

ckcc-protocolnpm

ckcc-protocol is a confirmed malicious npm package (MAL-2026-12064) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ckcc-protocol (npm)

MAL-2026-12064

Immediate action

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

npm uninstall ckcc-protocol

What this malware does

The npm package [email protected] typosquats the legitimate Coldcard ckcc-protocol tool and ships no functionality (index.js exports {}). Its package.json declares a postinstall script that runs automatically on npm install. The postinstall reads a fixed set of installer-side secret files, including ~/.env*, ~/.npmrc, ~/.aws/credentials, ~/.ssh/id_rsa, ~/.ssh/id_ed25519, ~/.ssh/id_ecdsa, ~/.config/solana/id.json, and ~/.ethereum/keystore, plus any dotfile whose name matches /wallet|key|secret|seed|mnemonic|keystore|private/i. It bundles the collected file contents together with os.hostname() and os.userInfo().username into a JSON payload and POSTs it via https.request to webhook.site/5c5ad6cb-62df-4ea5-9dfb-2c447920ddc4. The destination is an attacker-controlled request-capture endpoint, not the legitimate Coldcard project.

The OpenSSF Package Analysis project identified 'ckcc-protocol' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

4 flagged

1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

61a440517bf97875e91920faabc309da8fa1bfe264e510fa54e5ffa210bd1d15

36e22727edf29dcfea7bcbeae91ce73b87c89073920063f49ee0664cefd9b0da

3ebcdc07616ec6ab418a9005e1486d05f3753dc4d37f6ce61c5daed495d31e25

6ddec53c551e3ca016950072053c063175348cb02ddf7de2f447aa7f43fb96f3

ee0de5b6e85dca3a1e6ad106366f2c8e2b9b3262c548bc153ea2320702e2bee5

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

Campaign

IN-MAL-2026-013408IN-MAL-2026-013412IN-MAL-2026-013428IN-MAL-2026-013420

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks ckcc-protocol-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

Explore

All malware advisories How O3 detects malware Vulnerability database