The $130 Million Coldcard Hack: How a 2021 Firmware Bug Drained 7,300 Bitcoin Wallets in Minutes

The promise of a hardware wallet is simple: your private keys never leave the secure chip, and no remote attacker can touch them. On July 30, 2026, that promise shattered for thousands of Coldcard users when attackers drained over $70 million in Bitcoin from 1,196 wallets in just 41 minutes — without ever touching a single device .

By early August 2026, the running total had climbed past 1,816 BTC stolen, worth $116–$130 million depending on Bitcoin's price at reporting, from more than 7,300 addresses . The root cause: a build configuration error in a firmware update shipped five years earlier.

How a Single Build Flag Broke Coldcard's Security

Coldcard, the Bitcoin-only hardware wallet made by Canadian manufacturer Coinkite, was widely considered one of the most secure cold-storage options available. The flaw traced back to firmware version 4.0.1, released in March 2021 .

During a code migration, Coldcard mistakenly routed wallet seed generation to MicroPython's Yasmarang software pseudorandom number generator (PRNG) instead of the device's STM32 hardware random number generator (RNG) . Normally, the hardware RNG provides 128 bits of true entropy, making it computationally infeasible to guess a seed phrase. The software fallback used a deterministic PRNG seeded by predictable values like the device UID and internal timer state .

On Mk3 devices, the effective entropy collapsed from 128 bits to as little as 40 bits — a search space small enough to brute-force with publicly available tools . On Mk4, Mk5, and Q models, the entropy dropped to approximately 72 bits, which was still far below the intended security level .

Coinkite acknowledged that the bug affected seeds generated on Mk2 and Mk3 devices with firmware versions 4.0.1 through 5.0.3 . The vulnerability was not a breach of the Bitcoin network or Coinkite's servers — it was a flaw in how the device itself generated randomness .

The Attack Waves: $70 Million in 41 Minutes

Once attackers understood the weakness, they moved fast.

• First wave (July 30, 2026): An attacker drained 1,196 addresses, taking 1,082.65 BTC worth approximately $70.2 million, in a tightly coordinated 41-minute burst . Galaxy Research later narrowed the core theft to about 25 minutes .
• Second and third waves: Approximately 207–284 BTC per wave, adding roughly $13–18 million each .
• Possible fourth wave: If confirmed, the running total across four waves would reach about 1,816 BTC .

By August 7, Galaxy Research had identified at least 15 separate attackers independently exploiting the vulnerability, up from an initial handful of coordinated operators . TRM Labs documented roughly 1,816 BTC ($116 million) stolen from over 5,200 addresses across four waves . Other sources, including Galaxy's later update and the CBC, reported approximately 1,596 BTC stolen from roughly 7,300 addresses across three confirmed waves plus 14 smaller incidents .

Immediate Impact: Panic, Record On-Chain Activity, and a Fundamental Reckoning

The hack triggered immediate, visible consequences across the Bitcoin ecosystem.

Record on-chain activity. Bitcoin active addresses spiked to approximately 980,000 per day — the highest since December 2024 — as users scrambled to move funds off compromised devices . Glassnode reported that the exploit was the direct driver of this surge . Over 330,000 new Bitcoin addresses were created in the aftermath .

The self-custody debate sharpened. For years, the crypto security mantra was "not your keys, not your coins." The Coldcard hack reframed that into a harder question: even proper self-custody is worthless if the implementation of the hardware security module is flawed . Users who did everything right — bought a reputable hardware wallet, stored their seed phrase offline, never clicked phishing links — still lost everything because of a build flag error made years before they even bought the device .

Renewed calls for firmware auditing and regulation. The fact that a single build configuration error could remain dormant for five years and then drain $130 million triggered widespread demands for mandatory firmware security audits and potential regulatory oversight of hardware wallet manufacturing . Blockchain security firm REKT reported that the Coldcard breach alone accounted for roughly 10% of total crypto hack losses in 2026 .

AI-assisted hacking concerns. Forbes and other outlets noted that attackers used AI-assisted brute-forcing tools to accelerate the seed-space search, lowering the barrier for executing the exploit and raising broader alarms about AI-augmented threat actors targeting crypto infrastructure .

The BTCPay Server Exploit: A Second Blow Days Later

Days after the Coldcard incident emerged, on August 7–8, 2026, a critical vulnerability in the open-source BTCPay Server was actively exploited .

Versions of BTCPay Server prior to 2.4.2 allowed an unauthenticated remote attacker to obtain LND (Lightning Network Daemon) .macaroon credential files — the bearer tokens that authorize commands against a Lightning node . Once an attacker held the macaroon, they could control the node and drain its Bitcoin without needing a password, session, or any other foothold on the machine .

Confirmed victims included hardware wallet maker Foundation and Bitcoin publication Citadel21, whose Lightning channels were force-closed and funds swept . BTCPay released version 2.4.2 as an emergency patch, urged all operators to update immediately or shut down their servers, and temporarily restricted remote Lightning access . Supporters later offered a recovery bounty of up to 3 BTC for assistance in recovering stolen funds .

The BTCPay exploit, though much smaller in scale, compounded the sense of crisis in Bitcoin's infrastructure security. As Forbes put it, the situation was "extremely bad" .

Broader 2026 Context: A Record Year for Crypto Hacks

The Coldcard incident did not occur in isolation. According to security trackers, 2026 was on pace to be one of the worst years for crypto hacking on record.

• REKT reported approximately $1.2 billion in losses across 276 incidents as of early August 2026 .
• Blockaid counted 212 verified exploits in H1 2026 alone, exceeding its full-year total for 2025, with losses surpassing $1.1 billion . North Korea-linked hackers (Lazarus Group) were responsible for roughly $577–600 million of that total .
• CertiK reported approximately $1.32 billion lost across 344 on-chain incidents in H1 2026 .
• TRM Labs tracked 207 hacks totaling $972 million in H1 2026, noting that while the number of incidents hit a record high, the total value stolen was less than half of H1 2025's $2.3 billion — partly because there was no single $1.5 billion event like the Bybit hack .

Despite differing methodologies, the consensus was clear: the frequency of attacks was at an all-time high, and the Coldcard hardware wallet breach — representing roughly 10% of the year's total losses in just a few days — was the most visible example of a broader infrastructure vulnerability .

What Coldcard Users Needed to Do

Coinkite released an emergency firmware patch for all affected models and issued urgent guidance . The critical caveat: installing the firmware update does not fix an already-compromised seed . Users who had generated seeds on vulnerable firmware (versions 4.0.1 through 5.0.3 on Mk2 and Mk3 devices) needed to:

1. Install the patched firmware.
2. Generate a completely new seed phrase on the updated device.
3. Move all funds from the old seed to the new one immediately .

Coinkite confirmed that seeds generated on Mk4, Q, and Mk5 models were not affected by the same flaw . However, the broader lesson applied universally: a hardware wallet is only as secure as its firmware implementation.

The Lasting Lesson: Implementation Risk Is the New Self-Custody Risk

The Coldcard hack was not a phishing attack, a server breach, or a social engineering campaign. It was a supply-chain and firmware implementation failure that rendered five years' worth of hardware wallets insecure against a determined attacker with a laptop and public brute-forcing tools.

For the Bitcoin community, the incident forced an uncomfortable evolution of the self-custody mantra: "Your keys, your coins" is only true if the device that generated those keys actually did so with true randomness. When a single build flag siphons 88 bits of entropy out of your wallet, neither a steel seed plate nor a multi-sig setup can save you.

As one affected user told Forbes: "I did everything right" — and still lost over $116 million worth of Bitcoin .