Coldcard Drain Watch: 1,000+ BTC at Risk as Seed Flaw Spreads Beyond Mk3

Coldcard is a key-rotation event, not a Bitcoin protocol failure

This is a custody and key-rotation crisis, not a Bitcoin protocol failure. Reported losses have moved from roughly $38 million to more than $70 million, and data cited in coverage tracks 1,082.65 Bitcoins moved across affected addresses. That is large enough to matter now.

The distinction matters for market reaction

One clear read from the early reaction is that "Bitcoin didn't fail. Security did." That keeps the broader Bitcoin narrative intact while still leaving an urgent task for exposed users: rotate weak seeds, restored wallets, and derived keys before the easy window closes.

The split in reaction is understandable, but the scope is still narrowing

Bulls can argue this remains a contained custody issue. Bears are treating it as broader crypto stress, with sentiment described as bearish, stress-on, de-risking. The evidence supports the view that this is not a Bitcoin-layer failure, but it also shows why the market is nervous: about 1,000 BTC has been seen moving on-chain in connection with the vulnerability, and the exposure spreads beyond Mk3 into Mk4, Mk5, and Q wallets.

Which Coldcard funds are actually exposed

The more useful question is not just how much has moved, but which wallets are still at risk. A practical split is three layers: confirmed drain activity, likely exposure, and broader derived-key exposure.

Confirmed drain activity

The clearest signal is the early burst of movement: an attacker reportedly drained 594 BTC from around 500 wallets in under 30 minutes. That is actual loss activity, not abstract risk.

For risk tagging, the most important group is Mk3 funds created on firmware 4.0.1 through 5.0.3. Movement from wallets in that bucket should be treated as active loss rather than theoretical exposure.

Likely exposure: who still needs to move

Not every affected wallet has been emptied. A larger group may still hold vulnerable funds that have not yet been drained. The practical filter is whether the seed was created without at least 50 independent, private dice rolls. Coinkite says users who added that entropy are not at risk from this RNG issue alone.

Likely exposure therefore includes:

• Mk3 users on the affected firmware range who did not use sufficient dice entropy
• Users restoring old backups instead of generating fresh seeds on patched firmware
• Anyone relying on derived or cloned access paths tied to a compromised parent seed

Those funds are not safe simply because they have not been touched yet.

Broader exposure through derived keys

The exposure net is wider than the original wallets. The issue also extends to ephemeral keys and session keys for Clone Coldcard or Key Teleport, as well as BIP 85 seeds generated from a compromised seed. Users can therefore still be exposed through helper devices, cloned access, or child seeds even if the main wallet looks untouched.

What fixes the vulnerability and what does not

The urgent point is straightforward: fixed firmware is now available for every affected model and release track. But Firmware updates do not fix existing seeds; they only prevent new weak seeds from being created. That makes wallet rotation the real action item, not a passive firmware install.

The practical migration steps

Coinkite's guidance points to a careful sequence:

1. Update to the fixed firmware for your model and release track before generating a new seed.
2. Generate a completely new seed on the patched device.
3. Record and verify the new backup, wallet fingerprint, and a receive address.
4. Send a small test transaction before moving the remaining funds.
5. Keep the old backup until the migration is complete and confirmed.

A patch protects future seeds; it does not rescue an old weak seed.

What would stabilize the situation

The clearest stabilization signal is rotation outpacing further drains. That outlook is not baseless, because seeds generated after this firmware update should be secure.

If affected users migrate quickly and on-chain movement slows, this can reasonably be framed as a contained custody fix. If sweeping continues well after the patch is widely available, the self-custody stress signal will likely persist.