Security Practices for Prevention
Published 8/2/2026, 12:15:14 PM
The $88.6M Coldcard seed compromise attack (July–August 2026) was caused by a critical firmware build error that disabled the hardware random number generator (RNG), forcing devices to use a predictable software pseudo-random number generator (PRNG). This reduced the entropy of generated seeds from 128 bits to approximately 40 bits, allowing attackers to brute-force private keys offline [Source: https://thehackernews.com/2026/08/coldcard-hardware-wallet-flaw-linked-to.html, https://engineering.block.xyz/blog/predictable-rng-fallback-and-32-bit-reseed-in-coldcard-firmware].
Security Practices for Prevention
While the firmware bug was a manufacturer-level failure, several advanced security practices would have protected user funds by removing the single point of failure (the device's internal RNG).
| Practice | Prevention Mechanism |
|---|---|
| User-Provided Entropy (Dice Rolls) | Using the Coldcard's "Dice Rolls" feature to provide at least 50 fair, independent rolls bypasses the internal RNG. Coinkite stated that seeds generated this way were unaffected [Note: not independently confirmed]. |
| BIP-39 Passphrase | Adding a strong, unique "thirteenth/twenty-fifth word" creates a completely different wallet. Even if an attacker brute-forced the weak 24-word seed, they would find an empty wallet without the passphrase. |
| Multi-Vendor Multisig | A 2-of-3 multisig setup using different hardware vendors (e.g., Coldcard + Ledger + Trezor) ensures that a firmware bug in one device cannot lead to a total loss of funds. |
| External Seed Generation | Generating a seed phrase on an air-gapped, trusted system (like Tails OS) and importing it into the Coldcard removes reliance on the device's internal entropy generation. |
| Seed Migration Discipline | Recognizing that a firmware update does not fix an already compromised seed. Users on vulnerable versions needed to generate a new seed and migrate funds immediately [Source: https://thehackernews.com/2026/08/coldcard-hardware-wallet-flaw-linked-to.html]. |
Technical Root Cause
The vulnerability stemmed from a build configuration error where MICROPY_HW_ENABLE_RNG was set to zero. This caused the libngu library to fall back to the Yasmarang software PRNG, which relied on predictable states like Device UID and timer values [Source: https://engineering.block.xyz/blog/predictable-rng-fallback-and-32-bit-reseed-in-coldcard-firmware].
Affected Devices and Firmware
The following table outlines the versions affected by the entropy degradation:
| Model | Vulnerable Firmware Versions | Fixed Version |
|---|---|---|
| Mk2 / Mk3 | 4.0.0 – 4.1.9 | 4.2.0+ |
| Mk4 / Mk5 | Before 5.6.0 | 5.6.0+ |
| Q | Before 1.5.0Q | 1.5.0Q+ |
Conclusion: The attack was preventable through the use of external entropy (dice rolls) or multisig configurations. While the $88.6M loss figure is widely cited in reports linking the flaw to recent thefts, the exact total value of stolen funds remains difficult to verify independently across all affected addresses. Users who generated seeds on the vulnerable versions listed above remain at risk until they migrate to a new seed generated on patched firmware.