A software flaw in the popular Coldcard hardware wallet is allowing attackers to reconstruct seed phrases, prompting an emergency response from the device’s maker, Coinkite. The vulnerability, disclosed publicly on August 1, 2024, affects every Coldcard model that generated a seed without the optional dice‑roll entropy method after the end of 2020, and it is already being exploited on the Bitcoin blockchain.
The bug stems from insufficient randomness in the device’s internal entropy pool when users rely on the default seed‑generation process. Without the recommended 50+ dice rolls, the resulting BIP‑39 seed can be brute‑forced by an attacker who has harvested subtle timing and power‑analysis data from the device. In practice, this means a malicious actor can derive the private keys that control a wallet’s funds without any user interaction.
Coinkite confirmed that roughly 1,000 BTC have been transferred in transactions linked to the flaw, underscoring the immediacy of the threat. The company released a firmware patch that forces the dice‑roll option for all new seeds and hardens the entropy source for existing wallets. However, the patch does not retroactively protect seeds already generated under the vulnerable conditions.
For users, the practical steps are clear: move any funds controlled by a potentially compromised seed to a new wallet. The fastest route is to transfer the balance to a different hardware device, such as a Ledger or Trezor, or to a reputable software wallet like Blockstream Green or BlueWallet. If no alternative hardware is available, Coinkite advises creating a pass‑phrase‑protected wallet using at least six BIP‑39 words selected by an automated guide, then moving the assets there while a new seed is generated on a patched Coldcard.
Beyond the immediate migration, the incident highlights a broader structural insight about hardware‑wallet security. The industry has long marketed these devices as “cold” and therefore immune to remote attacks, yet the security model still depends heavily on the quality of user‑generated entropy. When manufacturers streamline the onboarding experience, they may unintentionally lower the barrier to attack, especially for users who are unfamiliar with cryptographic best practices.
The episode also reverberates through the Bitcoin ecosystem. Large‑scale thefts can erode confidence in self‑custody solutions, nudging users toward custodial services that promise higher security but sacrifice decentralization. Moreover, the vulnerability demonstrates how a single code path can affect a wide array of downstream features, including Clone Coldcard, Key Teleport, and BIP‑85 hierarchical seed generation.
Stakeholders across the crypto space should take note. Developers must audit entropy‑generation routines and consider mandatory user‑participation steps for critical cryptographic operations. Exchanges and custodians should monitor on‑chain activity for patterns that match the reported drain, offering assistance to affected customers. Finally, educators and community leaders need to reinforce the importance of proper seed creation, especially for newcomers who might assume the default settings are sufficient.
Coldcard users who have already applied the firmware update and regenerated their seed with the dice‑roll method can consider their devices secure again. Those who cannot immediately upgrade should follow the outlined migration path and keep an eye on Coinkite’s official communications for any further guidance.
