ckcc-protocol
Affected
- Versions:
1.0.0,1.0.1,1.0.2,1.0.3
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in ckcc-protocol (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (3ebcdc07616ec6ab418a9005e1486d05f3753dc4d37f6ce61c5daed495d31e25)
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.
Source: ossf-package-analysis (61a440517bf97875e91920faabc309da8fa1bfe264e510fa54e5ffa210bd1d15)
The OpenSSF Package Analysis project identified 'ckcc-protocol' @ 1.0.0 (npm) as malicious.
It is considered malicious because:
Not rated by the source.
1.0.0, 1.0.1, 1.0.2, 1.0.3None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0