The recent incident with Coldcard hardware wallets is not just another hacker attack, but a systemic failure in the security paradigm of the entire industry. The problem, uncovered during the vulnerability analysis, demonstrates that existing methods of independent testing of crypto asset storage devices have a critical flaw.
As I have repeatedly emphasized in my analytical reviews, trust in a hardware wallet is built on the assumption that the manufacturer correctly implements all cryptographic functions. However, as the Coldcard case showed, auditors often only check for the presence of a certified random number generator (TRNG) in the specifications, without delving into whether the actual firmware uses it. Kraken's Chief Security Officer Nick Percoco is absolutely right: users are asked to trust the implementation of a critical function without independent verification of the actual entropy generation path.
The Root of the Problem: Mismatch Between Code and Reality
Let me recall the timeline. The manufacturer Coinkite admitted that an error introduced back in 2021 led to the use of MicroPython's pseudo-random generator (PRNG) instead of the hardware TRNG. A technical analysis showed that the build configuration incorrectly defined a macro, causing the library to use the fallback, predictable Yasmarang generator. This led to a catastrophic reduction in entropy: for Mk2 and Mk3 — down to ~40 bits, for newer models — down to ~72 bits instead of the required 128.
The situation is compounded by the fact that a firmware update does not help those who have already created a seed phrase on a vulnerable version. Users have to manually migrate funds by creating new wallets, which in itself is a risky process.
The Scale of the Disaster and Market Reaction
Damage estimates have already exceeded $90 million. The attacks were carried out in waves: the first large-scale one on July 30, when 1082.65 BTC was withdrawn from 1196 addresses in 41 minutes. Later, new waves followed, affecting hundreds more addresses and approximately 448.7 BTC. Coinkite was forced to halt shipments and destroy devices with vulnerable firmware, and the company's lawyers began interacting with law enforcement agencies.
Analyst's View: Time to Implement Mandatory Standards
This incident is a vivid illustration that self-regulation and "manufacturer-paid audits" do not work. While in the payment industry devices undergo mandatory laboratory testing, and cryptographic modules for US government agencies are verified for compliance with standards such as NIST SP 800-90B, the hardware wallet market remains "wild." It is time to implement mandatory standards for verifying the full cycle: from the source of randomness to the executable code in the actual firmware. Without this, trust in "cold storage" as absolute protection will be finally undermined, and we will see more than one such precedent.