Summary
Attackers exploited a firmware flaw in Coldcard hardware wallets to reconstruct private keys without physical access, draining over $88 million in bitcoin from more than 4,500 addresses. The incident has sparked widespread questions about self-custody security.
Attack Scope Continues to Expand
According to the latest data from Galaxy Research, the attack on Coldcard hardware wallets has unfolded in three distinct waves, collectively draining 1,367 bitcoin from 4,585 addresses—approximately $89 million at current prices. This figure represents nearly double the initially reported losses, underscoring the severity of this security incident.
The first wave occurred on July 30, when attackers swept 1,083 bitcoin from 1,196 addresses within a 41-minute window, averaging nearly one full bitcoin per victim. Galaxy Research found these transactions concentrated across six blocks between 01:10 and 01:51 UTC, with three intervening empty blocks, suggesting the transactions were broadcast in batches rather than continuously.
While the second wave was relatively smaller in scale, the third wave exhibited new characteristics. Between Friday midday and Saturday morning UTC, attackers drained approximately 208 bitcoin from 1,912 addresses, averaging just 0.1 bitcoin per victim. This shift indicates the attacker has begun targeting smaller-balance wallets and employing more complex, harder-to-trace onchain transfer patterns.
Technical Vulnerability Explained
At the heart of this attack lies a critical flaw in Coldcard's March 2021 firmware release. The vulnerability involves the device's pseudo-random number generator (PRNG) and seed generation mechanism, rendering what should be computationally unguessable recovery seed phrases enumerable.
Galaxy Research noted that attackers were able to reconstruct private keys entirely offline, without ever physically accessing the devices. This attack method proves highly insidious because the traditional hardware wallet security model assumes private keys never leave the device—an assumption this attack fundamentally violated.
Security experts warn that additional wallets may remain at risk, as users cannot reliably determine whether their seeds were generated on vulnerable firmware. Even users who have upgraded to the latest firmware remain exposed if their seeds were originally created on the flawed version.
Coinkite CEO NVK issued an urgent advisory: If you generated a seed using a Coldcard wallet, move your funds now, using our updated best practices, before reading further. This recommendation emphasizes that affected users must generate entirely new wallets and transfer their funds—merely updating firmware does not eliminate the risk.
Attacker Behavior Analysis
Galaxy Research believes each wave represents the work of a single operator but cannot determine whether the same attacker orchestrated all three waves, as blockchain data cannot reveal whether separate sweeps are coordinated.
Notably, all stolen funds currently remain in four addresses and have not moved. This may indicate the attacker is waiting for an opportune moment for the next phase of operations or assessing law enforcement tracking capabilities.
The strategic shift in the third wave also merits attention. Unlike the previous two waves, the attacker began targeting smaller-balance wallets and sending each victim's coins to separate destination addresses rather than consolidating to a handful of collector addresses. This more distributed transfer pattern increases tracking difficulty, demonstrating the attacker's evolving tactics to evade detection.
Industry Reflection and Impact
This incident has prompted deep reflection across the cryptocurrency industry regarding self-custody security. For years, one of Bitcoin's primary selling points has been that investors need not trust banks and exchanges to safeguard their funds, but this massive hardware wallet breach has shaken that core promise.
Binance founder Changpeng Zhao (CZ) commented following the incident, urging cryptocurrency holders to diversify their storage: Even hardware wallets can have bugs. Even old wallets (with long history) can have bugs. How to mitigate? Split your funds in a few wallets maybe? This has a different set of risks. Nothing is 100%. Stay informed. Stay SAFU. CZ's advice reflects that even the most trusted self-custody solutions are not absolutely secure.
Security experts note this attack highlights the growing operational risks around self-custody, particularly as cyber threats continue to evolve. For everyday investors, the complexity and risks of managing private keys may have exceeded their capabilities.
Some industry observers believe this incident may accelerate investor migration toward third-party regulated custody services and spot Bitcoin ETFs. While these options mean relinquishing direct control over private keys, they offer professional security measures and regulatory protections that may prove more suitable for investors with lower risk tolerance.
The Value of Institutional-Grade Solutions
From an institutional perspective, this incident again demonstrates the importance of professional-grade security infrastructure. Institutional wallet solutions typically employ multi-layered security architectures, including multi-signature schemes, hardware security modules (HSMs), regular security audits, and bug bounty programs—measures that more effectively mitigate single points of failure.
For users and institutions managing substantial assets, adopting rigorously audited custody solutions with established security track records may prove more prudent than relying on a single hardware wallet. Simultaneously, implementing asset diversification strategies—avoiding concentration of all funds in a single wallet type or with a single service provider—represents an effective risk mitigation approach.
Lessons for the Broader Ecosystem
The Coldcard incident serves as a stark reminder that security vulnerabilities can emerge even in well-established products with strong reputations. Hardware wallets have long been considered among the most secure options for cryptocurrency storage, making this breach particularly concerning for the self-custody narrative.
The attack method—exploiting weak randomness in seed generation—highlights a fundamental challenge in cryptographic systems: the quality of entropy sources. True randomness is notoriously difficult to achieve in computing systems, and any weakness in random number generation can have catastrophic consequences for cryptographic security.
For wallet manufacturers, this incident underscores the critical importance of rigorous security testing, particularly around cryptographic primitives. The vulnerability existed in firmware released in March 2021, meaning affected wallets potentially remained at risk for over five years before the flaw was exploited and discovered. This timeline raises questions about the adequacy of security review processes and the need for ongoing vulnerability assessments even in mature products.
Implications for Self-Custody Practices
This event forces a reassessment of best practices for self-custody. The traditional advice of not your keys, not your coins remains valid, but must be balanced against the operational security challenges that everyday users face. Managing private keys securely requires not only choosing the right tools but also understanding their limitations and staying informed about potential vulnerabilities.
For individual users, the incident highlights several important considerations. First, firmware updates matter—but they are not a panacea if the vulnerability lies in how keys were originally generated. Second, diversification applies not just to asset allocation but also to custody solutions. Third, staying informed about security advisories from wallet providers is essential, as is acting promptly when vulnerabilities are disclosed.
The recommendation to generate new wallets and transfer funds, rather than simply updating firmware, may seem extreme but reflects the severity of the underlying vulnerability. When the randomness used to generate a seed is compromised, the only safe remedy is to abandon that seed entirely and start fresh with properly generated keys.
Looking Forward
As the cryptocurrency ecosystem matures, security standards must evolve accordingly. This incident may catalyze improvements in hardware wallet design, testing protocols, and transparency around security practices. It may also drive greater adoption of multi-signature schemes and other approaches that distribute trust rather than concentrating it in a single device or key.
For the industry as a whole, the Coldcard attack reinforces that security is not a one-time achievement but an ongoing process requiring constant vigilance, regular audits, and willingness to acknowledge and address vulnerabilities when they emerge. Whether users choose self-custody or third-party services, understanding the security model and its limitations remains essential for protecting digital assets in an environment where threats continue to evolve.
Source: link