"Coldcard's Five-Year Bug Cost Over 1,000 Users $70 Million"

To investors,

Jonathan Goodman lost $1.6 million on July 29th. He did everything right. His bitcoin was in cold storage. His Coldcard device sat in a safety deposit box and never connected to the internet. Between 9:36 PM and 9:43 PM, every wallet he owned was emptied. 18.25 BTC gone.

He's not the only one.

The cold storage incident that started as one victim's story turned out to be a systemic collapse of trust in the hardware wallet market's most respected product. The numbers are staggering:

1,196 Bitcoin addresses were drained in 41 minutes, according to Galaxy Research.

Over 1,082.65 BTC worth about $70.2 million has been confirmed stolen.

The firmware bug has been live for 1,900 days, since March 2021.

Every Coldcard model - Mk2, Mk3, Mk4, Mk5, and Q - is affected.

This is not a phishing attack. This is not malware. This is not user error.

This is a hardware wallet that was supposed to generate 128 bits of cryptographic entropy - more possible combinations than atoms in the observable universe - but instead produced approximately 40 bits for its Mk3 model. That's roughly one trillion combinations. The difference is the gap between a vault door and a screen door.

The Bug That Ate Five Years of Trust

Here's what happened in technical terms.

Coldcard's firmware was supposed to use the device's dedicated hardware random number generator when creating wallet seeds - the 12 or 24 word recovery phrases that become the master key to your bitcoin. A build configuration error caused the firmware to silently fall back to a software pseudorandom number generator called Yasmarang, inherited from the embedded MicroPython runtime.

The worst part: Yasmarang was initialized once from three inputs - the chip's serial number, a timer register, and the real-time clock. On the Mk3, the real-time clock was even disabled, meaning those registers held static values on boot. Once those inputs are known, the generator is fully deterministic. An attacker with a single Coldcard device can characterize the pattern and reproduce it for every other device running the same firmware.

A preprocessor guard was supposed to select the hardware implementation. But the guard only checked whether a configuration flag was defined, not whether its value was correct. The flag was defined as zero. The build completed without warnings. The firmware generated seeds that appeared normal, produced valid addresses, and accepted deposits. There was no indication to the user that the underlying entropy was catastrophically weak.

Block's Bitcoin engineering team traced the entire chain of failures. Coinkite, the Toronto-based maker of Coldcard, confirmed it independently. Two independent audits, same result.

AI Found What Humans Missed

The most uncomfortable part of this story isn't the bug. It's how the bug was discovered.

Coinkite believes the attacker used AI to find a flaw that its own AI audit of the same code missed weeks earlier. A Coinkite co-founder, NVK, wrote a blunt assessment on the shift: AI-assisted code review can now find latent bugs at a speed that outpaces the industry's most seasoned experts. If your firmware is open-source or has ever been public, assume it's already being read by attackers and defenders alike.

Kevin Loaec, CEO of Bitcoin security firm Wizardsardine, didn't mince words. He said the situation for affected Coldcard users was "everything is fucked". He warned that every mnemonic generated since 2021 would be exposed publicly in days.

The attack used brute force, not cryptography. The attacker didn't need to break encryption. They just needed to enumerate the dramatically reduced search space - the trillion-or-so candidate seeds - derive the corresponding Bitcoin addresses, check the blockchain, and drain any wallet with coins in it. The sweep moved 594 BTC across 500 transactions in four consecutive blocks in under 25 minutes. Then more addresses fell as the process continued.

The Narrative Violation

The consensus narrative in bitcoin is clear: cold storage is safe. Self-custody is king. If you control your keys, you control your bitcoin. Hardware wallets are the trusted alternative to exchanges and custodians.

The data tells a different story.

The most respected, most audited, bitcoin-only hardware wallet in the industry - a product specifically marketed on the strength of its air-gapped, hardware-isolated key generation - shipped a firmware bug for five years that rendered its promise hollow. Not because of a supply chain compromise. Not because of a stolen device. Because a preprocessor guard checked the wrong thing, and nobody noticed.

Bitcoin itself is fine. The protocol didn't break. The blockchain worked exactly as designed.

But the custody layer - the bridge between the math of Bitcoin and the physical reality of human beings holding it - is more fragile than most people think.

The question this incident forces isn't "is bitcoin safe?" The question is "how much can any single hardware device be trusted when a single line of code, buried in a preprocessor conditional, can wipe out five years of assumed security?"

Updating Doesn't Fix It

This matters because Coinkite's emergency firmware update, released July 31st, does not repair existing seeds. Updating the device prevents future seeds from being generated with the same weakness. It does nothing for the keys you already hold.

Every Coldcard owner who generated a seed on affected firmware - which includes anyone who created a wallet between March 2021 and July 2026 on Mk2, Mk3, Mk4, Mk5, or Q models - must create a completely new seed on patched hardware and migrate their coins. If your seed was weak when it was born, it stays weak forever.

For Mk4, Mk5, and Q models, the entropy is estimated at roughly 72 bits - materially better than the Mk3's 40 bits, but still far below the 128-bit standard that makes brute-force attacks infeasible. A firmware update on its own changes nothing for the coins you hold today.

Users who added at least 50 independent, private dice rolls during seed generation or used a strong BIP-39 passphrase face lower risk, because those inputs add external entropy the device's broken RNG can't reduce. But Coinkite still recommends replacing those seeds and migrating.

The Abundance-Scarcity Shift

Here's the framework that matters going forward.

AI creates abundance of code analysis capability. Both defenders and attackers now have dramatically cheaper tools to audit, find, and exploit vulnerabilities in every open-source firmware project. What becomes scarce?

Not cold storage. Scarcity shifts toward custody architectures that don't depend on a single device, a single codebase, or a single point of failure.

That means multisig setups where no single quorum path relies on affected devices. It means distributed custody across different manufacturers - Trezor and Ledger have confirmed their products are unaffected. It means the old assumption that one air-gapped hardware wallet is sufficient for millions of dollars in bitcoin is under structural pressure.

Peter Todd, a Bitcoin Core contributor, flagged a specific edge case: even multisig users with a 2-of-3 setup using two Coldcards are at risk. When funds move, the transaction reveals the script and public keys, allowing an attacker with the compromised keys to race the legitimate transaction. The only protection in that scenario is private mempool mining services like MARA's Slipstream, which keeps transaction details secret until they're already in a block.

What Bitcoin Says

Bitcoin is trading at $63,070, up 0.44% on the day. The market cap sits at $1.265 trillion. The price is down 27.8% over the last 250 days and down 6.6% year-to-date, with the price roughly 50% below its 52-week high of $125,500.

The market hasn't punished bitcoin for this event. The protocol held. No coins were forged. The chain didn't halt. The infrastructure - the actual network of nodes and miners - functioned flawlessly.

But the custody anxiety is real. If you own a Coldcard and haven't checked your firmware version since 2021, this is the story that costs you everything.

The Bear Case

The strongest counterargument is straightforward: this is a Coldcard problem, not a bitcoin problem. One company shipped a buggy firmware. That happens in every industry. The response is to migrate funds and be more careful, not to abandon self-custody.

Fair. The protocol is sound. But dismissing this as "just one wallet" misses the structural shift. A five-year entropy bug in the most trusted bitcoin-only hardware wallet - a bug that AI found at the same time it was draining wallets - isn't a user education issue. It's a signal that the compute economics of code exploitation have changed. The barrier to discovering and weaponizing firmware vulnerabilities is lower than it was five years ago.

The old custody playbook needs updating.

What to Watch

The data shows three things that matter for how you hold bitcoin:

If you use a Coldcard, check your firmware and seed generation date immediately. The migration guidance from Coinkite is explicit, and wallets are still being drained.

No single hardware device should be treated as a standalone security layer for significant holdings. The most resilient setups don't put all their entropy trust in one manufacturer's firmware.

The AI-driven code audit race is accelerating. Open-source firmware - the kind that the bitcoin community trusts most - is being read by attackers at machine speed. The bugs that survived five years of human review are the ones AI finds in a weekend.

Bitcoin's scarcity isn't threatened. The custody layer's fragility is the story. And the narrative violation here is clear: the assumption that "air-gapped equals safe" held until AI made the math work against it.

The protocol is fine. Your wallet might not be. Check.