A hardware wallet flaw let thieves guess $38M in Bitcoin — what a 'seed phrase' really protects

Coinkite, the maker of the popular Coldcard hardware wallet, has warned owners that a flaw in how some of its devices created their secret recovery phrase left funds guessable. About 594 bitcoin — roughly $38 million — was swept from around 500 wallets in about 25 minutes early Friday, with most of it later funneled into a single address.

To see why this matters, it helps to know what a hardware wallet actually does. Its job is to keep your private key offline, away from any internet-connected computer. That key is born from a "seed phrase," a list of words generated from randomness, known as entropy. If the randomness is weak, the pool of possible seeds shrinks — small enough that an attacker can guess candidate phrases, check the addresses they produce, and drain any that happen to hold coins.

That is what Coinkite says happened. A build error made affected Coldcards draw their randomness from a weak software fallback instead of the dedicated hardware generator, a mistake that had been in the code since a change in March 2021. The company estimates an affected Mk3 seed had only about 40 bits of real randomness instead of the intended 128. Newer Mk4, Q and Mk5 models were stronger, around 72 bits, but still short of target; its Tapsigner, Opendime and Satscard products are unaffected. Coinkite believes an attacker used AI to comb through its open-source code, and noted that its own AI review weeks earlier had missed the bug.

The most important lesson sits in one detail: updating the firmware does not fix a seed that was already created. Coinkite shipped an emergency update, but says an affected wallet needs a brand-new seed generated on patched hardware. A weak seed stays weak even if you move it onto another company's device. A strong, separate passphrase — an extra word you set yourself, which is not the same as the device PIN — or additional entropy from dice rolls can add a layer of protection.

For a beginner, the takeaway is not panic but perspective: self-custody is ongoing maintenance, not a one-time setup. If you are affected, follow the maker's official migration steps in order — generate a new seed on a patched device, verify the backup and a receiving address, send a small test amount first, and only then move the rest. Rushing a transfer to a mistyped address or a hastily made temporary wallet can cost more than the original bug ever would. And trust security advisories only from the manufacturer's official channels, never from a stranger's urgent message.