Why This Matters
Self-custody is the whole point of holding Bitcoin. "Not your keys, not your coins" only works if the keys themselves are generated correctly. On July 31, a flaw in the Coldcard Mk3 hardware wallet — one of the most trusted brands among serious long-term holders — showed that a hardware wallet can fail at the one job it exists to do: produce a truly random, unpredictable private key.
An attacker swept roughly 594 BTC (about $38 million) out of some 500 single-signature wallets in a single 25-minute window. The theft is a reminder that self-custody removes counterparty risk from exchanges and custodians, but it does not remove all risk. It shifts responsibility onto the device — and the user.
What Happened
Between 01:31 and 01:56 UTC on July 31, an attacker drained bitcoin from roughly 500 addresses across three consecutive blocks, consolidating the bulk of the haul — about 562 BTC — into a single address that has not moved since.
Coinkite, the company behind Coldcard, issued a security advisory the same day confirming a firmware defect affecting Mk3 devices. The root cause traces back to a build setting introduced in firmware version 4.0.0 in March 2021. That setting caused affected devices to skip the hardware's dedicated random number generator and fall back to a software-based substitute — one seeded from non-secret chip data, including the device's serial number and internal clock registers.
In plain terms: instead of generating a private key from true hardware randomness, vulnerable devices derived keys from information that was, in principle, guessable. Any wallet seed created on a Mk3 running firmware 4.0.1 through 5.0.3 is considered at risk.
According to Coinkite's preliminary analysis, the newer Mk4, Mk5, and Q models are not affected. Users who protected their Mk3 wallets with a BIP-39 passphrase face substantially lower risk, since the passphrase adds an additional secret that isn't derivable from chip data alone.
Coinkite has not formally confirmed that the July 31 theft is directly tied to this specific flaw, but the timing, attack pattern, and affected device class have led researchers to treat the two as connected pending further forensic detail.
What Affected Users Should Do
For anyone running an older Coldcard Mk3, the practical guidance from the advisory is straightforward:
- Treat any seed generated on affected firmware as potentially compromised.
- Move funds to a newly generated seed created on unaffected hardware, or a Mk3 updated to a patched firmware version generating a fresh seed.
- Use a BIP-39 passphrase on any wallet going forward — it is one of the few mitigations that would have limited exposure even under this flaw.
- Do not wait to "see if it's real." If the address list includes wallets you control, moving funds first and asking questions later is the correct order of operations.
How a Randomness Bug Becomes a Theft
The mechanics matter because they explain why this particular flaw sat undetected for roughly five years. A hardware wallet's entire security model rests on one property: the private key must be unpredictable to anyone but the owner. Dedicated hardware random number generators exist specifically because software-only randomness — drawing from things like a chip's serial number or clock state — can be reconstructed or narrowed down by an attacker who studies enough devices.
When Coldcard's Mk3 firmware quietly bypassed its hardware entropy source, it did not immediately break anything. The wallets worked exactly as expected for years — correct addresses, correct signing, correct balances. The defect only became exploitable once someone figured out how to reverse-engineer the reduced keyspace from publicly available chip characteristics, at which point every affected seed became a matter of computation rather than luck. That gap between "looks fine" and "is fine" is precisely why independent audits and reproducible builds matter for any device that holds real money.
Not the First, Won't Be the Last
Hardware wallet vulnerabilities are rare but not unprecedented — researchers have previously disclosed side-channel attacks and firmware issues across multiple vendors over the years, almost always patched before large-scale exploitation. What sets this incident apart is the scale of realized loss: $38 million taken in a single coordinated sweep is among the larger hardware-wallet-linked thefts reported to date, and it happened to a device widely recommended in Bitcoin self-custody circles precisely for its perceived rigor.
The Bigger Lesson on Self-Custody
This is not the first hardware wallet scare, and it will not be the last. Every device — no matter the manufacturer's reputation — is software running on physical hardware, and software has bugs. The lesson isn't "hardware wallets are unsafe." It's that self-custody requires the same due diligence as any other serious financial decision: verify firmware provenance, use passphrases where supported, consider multisig for larger holdings, and don't treat any single device as infallible.
Multisignature setups, where two or more independent devices must each approve a transaction, would have contained this specific failure: an attacker who compromised the randomness on one signer still could not move funds without the other keys. That is the core argument long-term holders keep coming back to as balances grow — single-signature convenience is fine for small, active amounts, but savings meant to last decades warrant the extra setup step.
Bitcoin Gate Take
A five-year-old build setting, quietly wrong the entire time, is a sharper argument for multisig and passphrase-protected wallets than any marketing pitch could be. Long-term holders sitting on meaningful balances in a single-signature wallet — regardless of brand — should treat this as the nudge to add a second layer of protection, not as a reason to distrust self-custody altogether. The alternative, leaving coins on an exchange, carries its own well-documented failure modes; this event just proves neither path is a "set it and forget it" decision.
If you're still working through the fundamentals of key management, our free self-custody course walks through seed generation, passphrases, and multisig step by step — no product to buy, just the mechanics explained plainly.