Coldcard Firmware Flaw Exposes Bitcoin Wallets to Mass Drain

The haul: about 594 BTC (~$38 million), with Chainalysis reporting the first $30M vanished in ten minutes flat. This was not a phishing campaign. It was not a clipboard-hijacking malware. It was a five-and-a-half-year-old flaw in the randomness that was supposed to make your seed phrase unguessable.

The vulnerability is both mechanical and unforgiving. According to technical analysis published by Block's Bitcoin engineering team, a build setting in affected Coldcard firmware instructed the device to skip its hardware random number generator (RNG). A check in a supporting library then verified only that the setting existed, not whether it was active. With no hardware source available and no error raised, key generation fell through to a basic software substitute, seeded from the device's serial number and internal clock registers. Neither input is secret. Both are deterministic. The result: a seed meant to be one candidate among an unimaginable number of possibilities became a solvable math problem.

Coinkite, the Canadian firm behind Coldcard, traced the bad commit to March 1, 2021, shipped in firmware 4.0.0. The flaw sat dormant in production for nearly five and a half years before someone weaponized it.

What Got Hit, and What Didn't

The attacker's target selection was brutally efficient. According to Chainalysis, automated tools identified wallets with substantial balances and prioritized them for immediate extraction. More than 1,300 individual UTXOs were moved across 500 transactions inside a three-block window, then 562 BTC was consolidated into a single address that has not moved since. That consolidation pattern is the tell: the attacker was not making decisions in real time. The targets were pre-determined by when each wallet was created.

Coinkite's advisory centers on Mk3 devices where the seed was generated on firmware 4.0.1 or later. Based on preliminary analysis, Mk4, Q, and Mk5 appear unaffected. This is the critical distinction: exposure depends on which firmware was running at the exact moment your wallet was created, not on what firmware you run today. Updating your device now does not retroactively fix a seed that was already generated with broken randomness. The key material is weak. The entropy is already compromised.

One exception: if you generated your seed by rolling dice and entering the entropy manually, a practice Coldcard has long supported, your randomness did not come from the broken code path. Your keys are likely intact.

What You Do Right Now

This is not a situation where you can wait for a clean disclosure cycle. If you hold any Bitcoin on a Coldcard Mk3 and your seed was generated on firmware 4.0.1 or later, treat the wallet as compromised. Move funds. Do not assume your model is on the safe list because reporting on the full range of affected firmware has not been consistent.

Verify your seed generation method. If you did not roll dice manually, your randomness is suspect. Isolate the device: do not connect it to an internet-enabled computer until you have confirmed your seed generation history. Audit your UTXOs: check your wallet balance against your expected holdings. If anything is missing, the attacker got there first.

Revoke and regenerate. Create a new wallet on fresh hardware, using a verified-secure method. Transfer funds only after confirming the new seed was generated with the hardware RNG active. If you hold life-changing amounts, adopt multi-signature cold storage. A single point of failure, whether software or hardware, is no longer acceptable.

What This Means for Anyone Storing Value

The Coldcard incident exposes a myth that has lingered in the crypto community for too long: that a hardware wallet is a fortress. It is not. It is a tool whose security depends entirely on the integrity of its entropy source. When that source is silently bypassed, the walls come down without warning, and the attacker does not need to touch your device, your computer, or your network.

Chainalysis's findings also reveal a harder truth: the attackers used cross-chain bridges and mixing services to launder the funds, complicating recovery and signaling that this was a well-financed operation, not a lone researcher. Law enforcement will likely follow, but for the victims, the funds are already in motion.

Your default setup is not secure. Verify every assumption about your wallet's key generation. Audit your cold storage. Assume that any device containing five-year-old firmware may carry five-year-old vulnerabilities. The next time someone tells you hardware wallets are unhackable, remember the 25 minutes of July 31, 2026, when 500 people learned otherwise.