Coldcard Wallet Exploit Spawns Malicious npm, PyPI Packages

Coldcard, the Bitcoin hardware wallet built by Coinkite, is at the center of the biggest crypto security event of the week. A firmware flaw weakened the randomness the device used to generate wallet seed phrases, and attackers turned that weakness into a way to drain bitcoin from thousands of addresses. Early reports put the losses near $38 million. By August 3 and 4 the figure had climbed toward $89 million. The part that matters for a supply chain catalog is what followed: malicious packages on PyPI and npm that impersonate Coldcard and BIP39 tooling, aimed squarely at the people now rushing to move their coins.

What happened with the Coldcard firmware flaw

Multiple outlets reported that a defect in Coldcard firmware made the seed phrases the wallet generated predictable rather than random. According to crypto.news, the problem stemmed from a build error in the firmware. Researchers quoted across the coverage described it more bluntly as a case where the random number generator was not actually random.

That distinction sounds academic. It is not. A Bitcoin seed phrase is only as strong as the entropy behind it. If that entropy is weak, the set of possible seeds shrinks from astronomically large to something an attacker can search.

The Hacker News linked the flaw to roughly $70 million in theft that happened in a 41 minute window. AMBCrypto later reported the total at about $88.6 million across 4,585 bitcoin addresses, and said the attacker was still holding the stolen coins. Coinpaprika put the haul at 1,082 bitcoin. The exact totals vary by source and have moved as more affected wallets were identified.

Timeline

The public account of the incident has shifted quickly, so treat these as reported milestones rather than a final record.

• Late July 2026: The first drains surface. CoinDesk described a roughly $38 million loss "so far" on July 31, and crypto.news reported an early $38 million theft carried out in about 25 minutes.
• Around August 1: Coldcard and third parties publish firmware fixes and migration guidance covering the seed generation flaw.
• August 2 to 3: Loss estimates rise to $70 million, then toward $88.6 million to $89 million, per TechSpot, AMBCrypto, PYMNTS, and Cryptobriefing. Bloomberg reported the attack as still ongoing on August 3.
• August 3 to 4: Malicious packages referencing Coldcard and BIP39 appear on PyPI and npm and are flagged as critical malware.

Who is affected

Anyone who generated a wallet seed on an affected version of Coldcard firmware should assume they are in scope until they confirm otherwise with Coinkite's official advisory. The risk is not limited to funds that have already moved. If your seed came from a weak entropy source, the seed itself is the problem, and every address derived from it is exposed regardless of how carefully you stored the device.

The exploit also reignited the self-custody debate. CoinDesk reported that the event shook confidence in self-custody and could push some investors toward exchange-traded products. That is a market reaction, not security advice, and it does not change the immediate task for affected holders.

How the seed generation flaw works

BIP39 is the standard that turns a block of random entropy into the familiar 12 or 24 word recovery phrase. Wallets derive every private key and address from that phrase. The security model assumes the entropy is unpredictable, so nobody can guess your phrase out of the enormous number of possibilities.

When the entropy source is broken, that assumption collapses. An attacker who knows the weakness can enumerate the reduced set of likely seeds, derive the addresses for each candidate, and check the public blockchain for balances. Any funded address gets swept. This is why the drains happened in minutes rather than over days. The attacker did not need to break into anyone's home or device, only to regenerate seeds that should never have been guessable, a pattern researchers have documented before in weak RNG incidents.

Whether the flaw was purely an accidental build mistake or something more is still being discussed. Cybernews reported speculation that attackers may have used AI to accelerate the exploitation. We have not seen that claim confirmed, and it should be treated as unverified.

Malicious Coldcard and BIP39 packages on PyPI and npm

Large, panic-inducing security events draw opportunists, and this one is no exception. Our catalog logged two packages tied to this theme, both flagged as critical malware and updated on 2026-08-04:

• coldcard-helpers on PyPI. See malicious code in coldcard-helpers.
• @zzzgenesis00/bip39-generator on npm. See malicious code in bip39-generator.

The naming is the whole trick. A user who just learned their Coldcard seed may be compromised goes looking for a helper script or a fresh seed generator, and finds a package that looks purpose built for the moment. Tooling that generates or handles a seed phrase is the worst possible place to run untrusted code. A single malicious line in a "BIP39 generator" can print a phrase to your screen while quietly sending the same words to an attacker's server, or hand you a seed the attacker already controls.

This class of attack is not new. In January 2026, ReversingLabs documented the BIPClip campaign, a set of malicious PyPI packages built to steal crypto wallet recovery phrases from developers. The Coldcard news gives the same playbook a fresh, high pressure hook. Detailed indicators for the two packages above were still limited at publication, so treat the package names themselves as the primary signal and check the linked catalog entries and your registry's advisories for updates.

How to check if you are affected by the Coldcard incident

For the wallet side, start with firmware. Check your Coldcard firmware version against Coinkite's advisory and assume any seed created on a vulnerable build is at risk. Do not wait to see whether funds move.

For the software supply chain side, audit any crypto or seed related packages you installed recently, especially anything you grabbed after the Coldcard news broke.

# PyPI / pip
pip list 2>/dev/null | grep -i "coldcard-helpers"
pip show coldcard-helpers

# npm (per project and global)
npm ls @zzzgenesis00/bip39-generator
npm ls -g @zzzgenesis00/bip39-generator

# Search lockfiles and source for the names
grep -R -n "coldcard-helpers" . 2>/dev/null
grep -R -n "bip39-generator" package-lock.json yarn.lock pnpm-lock.yaml 2>/dev/null

If any of these return a match, treat every seed phrase or private key that touched that machine as compromised.

Remediation

Handle the wallet first, because funds are the immediate target.

1. Update to the patched Coldcard firmware following Coinkite's official instructions, and verify the firmware signature before installing.
2. Generate a brand new wallet and seed on the patched device (or on a separate device you trust), then move funds to addresses from that new seed. Start with the largest balances.
3. Do not reuse any address derived from a seed created on affected firmware.

For the malicious packages:

# Remove the packages if present
pip uninstall -y coldcard-helpers
npm rm @zzzgenesis00/bip39-generator

# Then rotate anything the machine could have exposed:
#  - any wallet seed or private key entered or generated there
#  - API keys, SSH keys, and cloud credentials cached on that host

Never generate or type a real seed phrase on an internet connected machine, and never paste a recovery phrase into a package or website. A hardware wallet generates its seed on the device for exactly this reason. If a tool asks you to enter your existing phrase to "check" or "migrate" it, that tool is the attack.

FAQ

Is my Coldcard wallet safe to use right now

If your seed was generated on an affected firmware version, treat it as unsafe until you migrate to a new seed on patched firmware. Check Coinkite's official advisory for the exact affected versions, update the firmware, and move funds to a freshly generated wallet. A device that is physically fine can still hold a seed that is now guessable.

How do I know if I am affected by the Coldcard exploit

There is no way to tell from the balance alone, because a weak seed is exploitable whether or not it has been drained yet. Confirm your firmware version against Coinkite's guidance. If it falls in the affected range, assume the seed is compromised and migrate.

Are coldcard-helpers and bip39-generator safe to install

No. Both were flagged as critical malware in our catalog on 2026-08-04. Do not install them, and remove them if they are already present. Legitimate wallet setup does not require a random PyPI or npm package to generate or handle your seed.

Should I use a software package to generate a BIP39 seed phrase

For real funds, no. Let the hardware wallet generate the seed on the device, offline. Software seed generators, especially unknown ones surfacing during a panic, are a common cover for phrase stealing malware, as the BIPClip campaign showed earlier in 2026.