How a Five-Year Firmware Bug Let Attackers Drain $70 Million From Bitcoin Hardware Wallets
A firmware integration error in Coldcard hardware wallets allowed attackers to generate and steal private keys remotely, draining roughly $70 million in Bitcoin from approximately 1,196 addresses in just 41 minutes on July 30, 2026. The vulnerability, which affected devices since March 2021, represents one of the most significant self-custody security failures in cryptocurrency history and raises urgent questions about how hardware wallet manufacturers test their code.
What Exactly Went Wrong With Coldcard's Firmware?
The root cause traces back to a subtle but catastrophic configuration error. Coldcard's firmware was supposed to use the STM32 hardware random number generator, a specialized chip designed to produce cryptographically secure randomness. However, a firmware integration error routed seed generation through Yasmarang, a non-cryptographic pseudorandom algorithm instead. The mistake happened because the cryptographic support library checked only whether a randomness macro existed, not whether its value was actually enabled. Since the macro was defined (even though set to zero), the library incorrectly assumed hardware randomness was active.
This seemingly minor oversight had enormous consequences. Every private key generated on affected Coldcard devices for five years relied on an entropy source with only about 40 bits of effective randomness, compared to the 128-bit minimum required by BIP-39, the standard underlying more than 90 percent of self-custody cryptocurrency wallets. An attacker who understood the timing distributions of a Coldcard device could narrow the search space enough to enumerate candidate keys offline, without ever physically accessing the wallet.
How Did the Attack Actually Happen?
On July 31, 2026, an attacker executed a highly automated sweep that drained 1,082.65 Bitcoin, worth approximately $70.2 million, from 1,196 addresses in just 41 minutes. The transactions all carried identical 30 satoshi-per-byte fees with no change outputs, and they clustered across blocks 960,183 to 960,191, indicating full automation rather than manual execution. The attacker never needed to access a physical Coldcard device; they simply reproduced candidate seeds offline by constraining the device UID, timer state, and prior random number generator call history, then validated the keys against public blockchain data.
The stolen Bitcoin currently sits in four addresses and has not been liquidated, according to security researchers. The lack of immediate selling limits the direct price impact on Bitcoin but represents a potential overhang for the market.
Which Coldcard Models Were Affected?
The confirmed exploit targeted Coldcard Mk2 and Mk3 devices where wallet seeds were generated on firmware versions 4.0.0 through 5.0.3, a window spanning March 2021 through the final Mk3 firmware release. Coinkite, the Canadian manufacturer, has published device-specific advisories and released emergency firmware updates for every affected model: version 4.2.0 or later for Mk3, 5.6.0 or later for Mk4 and Mk5, and 1.5.0Q or later for the Coldcard Q.
However, updating firmware alone does not secure existing funds. The private keys derived from a compromised seed remain unchanged even after a firmware update. Affected users must generate an entirely new recovery phrase on the corrected firmware and migrate their Bitcoin to a fresh address. Galaxy Research further warned that future attacks remain possible against any Coldcard-generated address, and such attacks need not match the transaction pattern observed on July 31.
Steps to Protect Your Self-Custody Bitcoin After the Coldcard Exploit
- Check Your Device Model: Determine whether you own a Coldcard Mk2, Mk3, Mk4, Mk5, or Q, and verify which firmware version you are currently running through the device settings menu.
- Update Firmware Immediately: Download and install the latest emergency firmware from Coinkite's official website, ensuring you use version 4.2.0 or later for Mk3, 5.6.0 or later for Mk4 and Mk5, or 1.5.0Q or later for Coldcard Q.
- Generate a New Recovery Phrase: After updating firmware, create an entirely new BIP-39 recovery phrase on the corrected device, never reusing any seed previously generated on vulnerable firmware versions.
- Migrate Your Bitcoin: Transfer all Bitcoin from addresses derived from old seeds to new addresses generated from the fresh recovery phrase on updated firmware.
- Consider Alternative Hardware Wallets: Evaluate other hardware wallet manufacturers and compare their security practices, code review processes, and incident response protocols before deciding where to store significant amounts of Bitcoin.
Why Did Coinkite's Review Process Miss This Bug?
Coinkite CEO Rodolfo Novak issued an apology and stated that the company took full accountability for the firmware bug, conceding that its review process had failed to identify it. The incident highlights a critical vulnerability in hardware wallet security: even devices marketed as the gold standard for self-custody can harbor subtle configuration errors that persist for years without detection.
"The company took full accountability for the firmware bug, conceding that its review process had failed to identify it," acknowledged Rodolfo Novak, CEO of Coinkite.
Rodolfo Novak, CEO, Coinkite
The Coldcard exploit is the third major documented failure of this class in recent years, following the 2023 Milk Sad PRNG vulnerability and the 2026 Ill Bloom mobile wallet breach. In each case, the failure occurred at the point of wallet creation, a moment the user had no way to independently verify regardless of how carefully they followed security best practices.
What Does This Mean for the Broader Hardware Wallet Industry?
The incident lands in an already difficult year for security. Blockchain security firm Blockaid reported that crypto projects lost more than $1 billion to hacks in the first half of 2026. The Coldcard exploit demonstrates that even hardware wallets, which are supposed to isolate private keys from internet-connected devices, can fail at the cryptographic level if firmware contains subtle errors.
The timing compounds the damage. Bitcoin closed July 2026 up roughly 7 percent, its best monthly finish since the current bear-recovery cycle began, but immediately walked into August facing additional macro headwinds. The Federal Reserve voted 9-3 to hold rates on July 29, but three regional presidents dissented in favor of a hike, lifting September tightening odds above 60 percent. For Bitcoin holders already processing the Coldcard breach, the combination of security concerns and rising rate expectations creates a challenging environment for confidence in self-custody.
The exploit underscores a fundamental tension in cryptocurrency security: hardware wallets can protect private keys from remote attackers, but they cannot protect users from flawed randomness generation or other firmware-level errors that compromise the keys themselves. As self-custody becomes more common among institutional and retail investors, the security bar for hardware wallet manufacturers continues to rise, and the cost of failure grows exponentially.