Coldcard, made by the Canadian firm Coinkite, is one of the most established names in bitcoin-only hardware wallets. It's built specifically to keep private keys air-gapped and offline - the device never has to touch an internet-connected computer to sign a transaction. That design is the reason it earned trust in the self-custody community in the first place.
Late in July 2026, that trust was tested. Coinkite disclosed a firmware defect, present since March 2021, that in some cases replaced true hardware-generated randomness with a predictable substitute. Instead of drawing on the device's dedicated random number generator, affected firmware fell back to a software routine seeded with non-secret data - the chip's serial number and its internal clock. On certain devices, this reduced the effective entropy of a wallet seed from an expected 128 bits down toward levels a determined attacker can search computationally, rather than one that requires breaking real cryptography.
Coinkite says an internal review had not caught the issue. It became public only after an attacker found and used it.
What happened, in sequence
The exploitation played out in at least three distinct waves. An initial sweep on July 30 emptied hundreds of single-signature wallets in a window of roughly 25 to 40 minutes, moving several hundred BTC. Follow-up waves through July 31 and August 1 extended the pattern to thousands more addresses. Galaxy Research, one of several firms independently tracking the incident, has tied the activity to over 4,500 addresses and roughly 1,367 BTC - worth close to $89 million at the time of the sweeps. Coinkite and outside researchers, including engineers at Block, have described the losses as ongoing, and figures have been revised upward multiple times since the first disclosure.
The affected coins span the full life of the flaw: seeds created any time from 2021 through 2026 on vulnerable firmware are exposed, meaning both freshly funded wallets and long-dormant ones have been at risk.
Why a firmware update alone doesn't fix it
This is the detail that matters most for anyone holding an affected device. The vulnerability lived in how a seed was originally generated, not in the firmware currently running. Installing a patch prevents new seeds from being created insecurely - it does nothing to repair a seed that already exists. Coinkite's guidance, consistent with independent researchers, is that anyone who generated a seed on an exposed configuration needs to create an entirely new seed on patched firmware and migrate funds to it, rather than assume an update alone resolves the exposure.
Coinkite has named the affected configurations directly: Mk3 devices running firmware 4.0.1 or later, and Mk4, Mk5, and Q devices on versions prior to their respective fixed releases (5.6.0 and 1.5.0Q). Migration carries its own risk, since the transaction that moves funds off a compromised wallet still has to be broadcast from that same compromised key - a detail that has pushed some researchers to recommend private or out-of-band broadcasting services during the transition.
What this isn't
Every other major hardware wallet manufacturer - Ledger, Trezor, BitBox among them - has stated its products are not affected. This is not an industry-wide flaw in how hardware wallets work; it's specific to a build error in one company's firmware, where a check for whether the device's true hardware random number generator was enabled failed silently and fell through to a much weaker software fallback.
That distinction matters. Self-custody as a principle is not what failed here. A single implementation did.
The pattern behind the failure
Coinkite's firmware is open source, and has been the entire time this flaw existed. That fact deserves sitting with. Open availability of code is necessary for verifiability, but it is not sufficient for security - a defect can sit in plain sight for years without anyone auditing it closely enough to notice. Several researchers investigating the incident have suggested the attacker may have used automated tooling, including AI-assisted code review, to find the weakness faster than any human audit had. Coinkite has said its own AI-assisted review of the same codebase, conducted shortly before the exploit, missed it.
This is not the first time a security failure has reshaped how the bitcoin industry operates, and it likely won't be the last. Exchange collapses forced a rethink of custodial cold storage practice. Earlier key-management bugs forced better standards around seed generation and hardware entropy sourcing. The lesson each time has been the same: the companies that treat independent, adversarial auditing as a continuous baseline - not a one-time certification or a line in a pitch deck - are the ones that hold up. The ones that treat it as optional pay for that choice publicly, and their users pay first.
What Coldcard owners should do
- Do not assume a firmware update resolves your exposure. It only prevents new insecure seeds from being generated.
- If your seed was generated on an affected model and firmware version, generate a brand-new seed on patched firmware and move your funds to it.
- Consider multisignature setups going forward. A flaw in a single device's entropy source is far less catastrophic when no single device holds a complete, spendable key.
- Verify Coinkite's official advisory directly before acting, since exposure depends on your specific device model and the firmware version active when your seed was first created.
The broader point
Hardware wallets exist to remove trust in any single third party. This incident is a reminder that removing trust in an exchange or a custodian doesn't remove the need for trust somewhere - it moves that trust into the device, the firmware, and the audit process behind it. Evaluating a hardware wallet on those terms, rather than on marketing claims of being "unhackable," is the discipline this event should reinforce across the industry.
House of Bitcoin covers bitcoin infrastructure and security through evidence-based research. This piece will be updated if Coinkite or independent researchers revise the scope of the incident.
