Coldcard Victims Lost 'Life Savings' - But the Real Threat Is Still Flowing

The Coldcard Drains Are Still Expanding

This was not a closed incident. On July 30, an attacker drained 1,196 Bitcoin addresses in 41 minutes, taking 1,082.65 BTC worth about $70.2 million. Galaxy Research tied that sweep to Coldcard wallets. The speed of the drain suggests an active cashout operation rather than isolated bad luck.

The scope has continued to grow. Galaxy's suspected Coldcard-linked estimate later reached 1,367.05 BTC, or about $88.6 million across 4,585 addresses. Users say the human toll is just as severe: some report losing their life savings, and one victim said ₹15 crore worth of Bitcoin disappeared in 7 minutes. The expanding flow of coins makes it harder to treat this as a one-off breach.

What makes the situation especially unsettling is that the exposure depends on the firmware that was running when a seed was created, not on what is installed today. If coins still sit behind a tainted seed, the risk has not passed.

Why "I Did Everything Right" No Longer Guarantees Safety

The blow to victims is not only financial; it is psychological. They did not lose funds by clicking a malicious link or leaving coins on an exchange. They lost coins while using a Bitcoin-only hardware wallet, and some say they lost their life savings. That is why this flaw cuts so deeply: it undermines the assumption that using a hardware wallet means doing everything right.

How the Coldcard flaw reduced seed randomness

The root cause was a March 2021 firmware integration error that routed seed generation to a software pseudorandom number generator instead of the STM32 hardware random number generator.

Block's analysis says an attacker who can determine or sufficiently constrain the device UID, timer state, and prior RNG-call history can reproduce candidate output streams offline. From there, the attacker derives addresses from those candidate seeds and compares them with public blockchain data. In practical terms, the attack does not require compromising the device directly; it requires narrowing the seed space enough to brute-force against onchain information.

There is still debate over how severe that reduction was. Coinkite and supporters note that this was not a clean 128-bit failure; estimated effective entropy was roughly 40 bits on the Mk3 and about 72 bits on the Mk4, Mk5 and Q, versus 128 bits for a 12-word BIP-39 seed. Even so, 72 bits is still far below what many holders assumed they had, especially if contextual variables further narrow the search space.

Patched firmware helps, but it does not fix old seeds

The main rebuttal is that patched firmware stops new weak seeds from being created. That matters, because Coinkite says installing the update does not repair an existing seed. It also says a seed created with at least 50 fair, independent, private dice rolls is not at risk from this bug alone.

But that only helps if you are confident in your seed-generation history. If that is uncertain, Coinkite still recommends migration. Restoring an old seed to updated firmware or to another wallet carries the weakness forward, which is why device updates alone are not enough.

The open question is no longer whether researchers understand the bug. It is how many wallets are still exposed. That depends on the firmware that was active when a seed was created, leaving a real blind spot for users who do not know their exact generation history.

What to Do if You Use Coldcard

If your coins still live on an original Coldcard seed created under affected firmware, the practical hedge is to generate a fresh seed on patched firmware and move the funds. Installing patched firmware does not repair an existing seed, and restoring the old seed carries the weakness forward.

The threat profile is also harder to dismiss. Galaxy said the latest wave involved targeting smaller balances across a broader address set, so the activity is not limited to headline-grabbing drains. That does not mean every Coldcard user has been compromised, but it does mean the attack surface still appears active.

What to watch next

• Continued sweeps of smaller balances would suggest the attack is still spreading rather than fading.
• Firmware adoption matters only if it leads to fewer new movements from known-exposure seeds.
• More users reporting losses would indicate that the problem is still reaching wallets that were not part of the initial large drains.