The Scale of the Breach: Losses in BTC and Dollars

The attack unfolded in at least four escalating waves. The confirmed tally across the first three waves is 1,596 BTC stolen from roughly 7,300 addresses, with a suspected fourth wave that could push the total to approximately 2,000–2,055 BTC . Different blockchain analytics firms reported slightly different figures due to varying counting cutoffs and whether unconfirmed fourth-wave activity was included :

Galaxy Research identified at least 15 separate attackers exploiting the vulnerability simultaneously . Remarkably, 90% of the stolen BTC remained unmoved as of early August, with Galaxy providing attacker addresses to U.S. federal law enforcement .

Root Cause: A Firmware Bug from March 2021

The vulnerability was a preprocessor macro error introduced in Coldcard firmware v4.0.1, released in March 2021 . A C preprocessor guard tested whether a macro was defined rather than testing its value. This caused the linker to resolve seed generation against a deterministic software pseudorandom number generator (PRNG) instead of the STM32 hardware random number generator (TRNG) . The bug had sat unnoticed in open-source code for over five years .

Entropy collapse: On Mk2 and Mk3 devices (running firmware v4.0.1 through v4.1.9), effective entropy dropped from the intended 128 bits to roughly ~40 bits . On Mk4, Mk5, and Q models, the fallback yielded about 72 bits — also below spec . Seeds generated with ~40-bit entropy are brute-forceable without physical access to the device .

The Exploit Timeline

The attack progressed with alarming speed:

• July 30, 2026, ~01:10–01:56 UTC: The first attacker swept roughly 594 BTC (~$38M) from ~500 single-signature wallets within a three-block window (about 25 minutes) . The attacker had brute-forced the weak seeds in 41 minutes .
• By August 1: Losses reached ~1,082 BTC. A second attack wave drained ~284 BTC .
• August 2–4: A third wave hit, and Galaxy Research identified a suspected fourth wave .
• Total addresses affected: Over 5,200 (Forbes/TRM) to over 7,300 (Galaxy Research) .

All affected wallets were single-signature configurations. Multi-signature wallets were not impacted .

Coinkite's Firmware Patch — and Its Critical Limitation

Coinkite released a patched firmware that restored the correct hardware RNG path for future seed generation . However, the patch cannot retroactively fix seeds already generated by compromised firmware. Users whose wallets were created between March 2021 and the patch's release were advised to immediately sweep funds to new wallets with a freshly generated seed . The company emailed customers dating back to 2019 to warn them of the bug and destroyed its remaining vulnerable inventory .

Coinkite's Data-Deletion Policy Reversal

Before the breach, Coinkite had a strict privacy policy of automatically deleting customer data (emails, purchase records) after 90–120 days . After the hack, the company reversed this policy, announcing it would retain customer records in preparation for anticipated legal proceedings . This drew significant backlash from privacy-focused users who had chosen Coldcard partly for its data-minimization stance . Coinkite stated the data would be stored with restricted access and that customers could still request standard deletion . Thomas Braziel of 117 Partners is reportedly investigating product liability claims and a potential class-action lawsuit against Coinkite .

Industry Response: A Surge in Bitcoin ETF Inflows

The breach drove a surge in onchain activity to the highest level of 2026 as victims moved remaining funds and the broader market reassessed self-custody risk . Weekly net inflows into U.S. spot Bitcoin ETFs jumped to approximately $853 million in the week following the hack, as institutional investors rotated toward regulated custody solutions in response to the Coldcard failure .

Broader Security and Self-Custody Implications

The Coldcard hack crystallized several uncomfortable truths for the Bitcoin self-custody community:

• Single-signature risk amplified: The incident demonstrated that single-signature setups expose users to a single point of failure in key generation. Multi-signature or threshold schemes would have been unaffected even with the weak RNG .
• Open-source transparency cut both ways: The bug lived in public code for more than five years without being caught — underscoring the gap between "code is auditable" and "code is actually audited" .
• Hardware RNG vs. software fallback: The case showed that a build-configuration error silently defeating hardware entropy can turn a "cold" wallet into a hot wallet vulnerability .
• Shift toward regulated custody: The $853M weekly ETF inflow suggested a measurable flight from self-custody hardware wallets toward institutional-grade custody solutions among larger holders .
• Legal liability for hardware wallet makers: Coinkite's reversal of its data-retention policy and the expectation of user lawsuits signaled that hardware wallet manufacturers may face liability for firmware bugs, potentially reshaping warranty terms and insurance in the sector .

The Scale of the Breach: Losses in BTC and Dollars

The attack unfolded in at least four escalating waves. The confirmed tally across the first three waves is 1,596 BTC stolen from roughly 7,300 addresses, with a suspected fourth wave that could push the total to approximately 2,000–2,055 BTC . Different blockchain analytics firms reported slightly different figures due to varying counting cutoffs and whether unconfirmed fourth-wave activity was included :

Galaxy Research identified at least 15 separate attackers exploiting the vulnerability simultaneously . Remarkably, 90% of the stolen BTC remained unmoved as of early August, with Galaxy providing attacker addresses to U.S. federal law enforcement .

Root Cause: A Firmware Bug from March 2021

The vulnerability was a preprocessor macro error introduced in Coldcard firmware v4.0.1, released in March 2021 . A C preprocessor guard tested whether a macro was defined rather than testing its value. This caused the linker to resolve seed generation against a deterministic software pseudorandom number generator (PRNG) instead of the STM32 hardware random number generator (TRNG) . The bug had sat unnoticed in open-source code for over five years .

Entropy collapse: On Mk2 and Mk3 devices (running firmware v4.0.1 through v4.1.9), effective entropy dropped from the intended 128 bits to roughly ~40 bits . On Mk4, Mk5, and Q models, the fallback yielded about 72 bits — also below spec . Seeds generated with ~40-bit entropy are brute-forceable without physical access to the device .

The Exploit Timeline

The attack progressed with alarming speed:

• July 30, 2026, ~01:10–01:56 UTC: The first attacker swept roughly 594 BTC (~$38M) from ~500 single-signature wallets within a three-block window (about 25 minutes) . The attacker had brute-forced the weak seeds in 41 minutes .
• By August 1: Losses reached ~1,082 BTC. A second attack wave drained ~284 BTC .
• August 2–4: A third wave hit, and Galaxy Research identified a suspected fourth wave .
• Total addresses affected: Over 5,200 (Forbes/TRM) to over 7,300 (Galaxy Research) .

All affected wallets were single-signature configurations. Multi-signature wallets were not impacted .

Coinkite's Firmware Patch — and Its Critical Limitation

Coinkite released a patched firmware that restored the correct hardware RNG path for future seed generation . However, the patch cannot retroactively fix seeds already generated by compromised firmware. Users whose wallets were created between March 2021 and the patch's release were advised to immediately sweep funds to new wallets with a freshly generated seed . The company emailed customers dating back to 2019 to warn them of the bug and destroyed its remaining vulnerable inventory .

Coinkite's Data-Deletion Policy Reversal

Before the breach, Coinkite had a strict privacy policy of automatically deleting customer data (emails, purchase records) after 90–120 days . After the hack, the company reversed this policy, announcing it would retain customer records in preparation for anticipated legal proceedings . This drew significant backlash from privacy-focused users who had chosen Coldcard partly for its data-minimization stance . Coinkite stated the data would be stored with restricted access and that customers could still request standard deletion . Thomas Braziel of 117 Partners is reportedly investigating product liability claims and a potential class-action lawsuit against Coinkite .

Industry Response: A Surge in Bitcoin ETF Inflows

The breach drove a surge in onchain activity to the highest level of 2026 as victims moved remaining funds and the broader market reassessed self-custody risk . Weekly net inflows into U.S. spot Bitcoin ETFs jumped to approximately $853 million in the week following the hack, as institutional investors rotated toward regulated custody solutions in response to the Coldcard failure .

Broader Security and Self-Custody Implications

The Coldcard hack crystallized several uncomfortable truths for the Bitcoin self-custody community:

• Single-signature risk amplified: The incident demonstrated that single-signature setups expose users to a single point of failure in key generation. Multi-signature or threshold schemes would have been unaffected even with the weak RNG .
• Open-source transparency cut both ways: The bug lived in public code for more than five years without being caught — underscoring the gap between "code is auditable" and "code is actually audited" .
• Hardware RNG vs. software fallback: The case showed that a build-configuration error silently defeating hardware entropy can turn a "cold" wallet into a hot wallet vulnerability .
• Shift toward regulated custody: The $853M weekly ETF inflow suggested a measurable flight from self-custody hardware wallets toward institutional-grade custody solutions among larger holders .
• Legal liability for hardware wallet makers: Coinkite's reversal of its data-retention policy and the expectation of user lawsuits signaled that hardware wallet manufacturers may face liability for firmware bugs, potentially reshaping warranty terms and insurance in the sector .