The Binance Square discussion is centered on where the stolen funds from COLDCARD have gone, but for now there is insufficient confirmation—either from the project(s) involved or from two independent, reliable sources—that the funds have “already entered a mixing protocol.” The risks that can be confirmed are serious enough: Coinkite issued a security alert on July 30, updated the scope of affected systems on August 1, and admitted on August 4 that users had already suffered actual losses. Block’s independent technical report also indicates that active exploitation is ongoing.

Why version upgrades aren’t enough

This vulnerability is most easily misunderstood as “it’s over once you upgrade the firmware.” My assessment is the exact opposite: what truly needs to be tracked is the firmware and entropy sources used when generating the seed, not the version the device is showing now. The official guidance states that Mk2/Mk3 seeds generated between 4.0.1 and 4.1.9 are at risk. Mk4/Mk5 seeds generated before the standard version 5.6.0 and before Edge version 6.6.0X are also affected, including seeds generated before 1.5.0Q and before 6.6.0QX. The vulnerability causes the random-number path to fall into a predictable software rollback. The vendor’s initial estimate is that the effective search space for older models is about 40 bits, and for later models about 72 bits—both below the expected 128 bits. The numbers may still be revised as the investigation proceeds, but the boundary is already clear: “upgrading won’t fix old seeds.”

Risk propagation happens in two steps. In the short term, an attacker can offline enumerate candidate seeds and then verify them using a public address or xpub; once a match is found, the related funds may be moved. In the medium term, the problem is not limited to a single hardware wallet: even if the code contains a correct random number implementation, it does not necessarily mean that the actual seed-generation path calls it. If a security review only examines module contents without validating symbol parsing in the build artifacts and the end-to-end call path, similar defects may still slip through.

The disposal order must not be reversed

Affected users should first verify the device model, the firmware used when generating the seed, and the release track; after installing the corresponding fixed version, generate a brand-new seed; verify the backup, wallet fingerprint, and receiving address; transfer a small test amount first, and only after confirming should they move the remaining funds. Keep the old backup until the migration is fully confirmed. The recovery phrase and BIP-39 passphrase must not be entered into websites or untrusted devices.

At least 50 fair, independent, and private dice inputs, or a strong and unique BIP-39 passphrase, can reduce the immediate risk in specific scenarios, but the passphrase does not fix weak seeds. If you are unsure, handle it as affected. TAPSIGNER, OPENDIME, and SATSCARD use different codebases. The official statement says they are not affected by this vulnerability, so you can’t infinitely extrapolate the alarm.

Unconfirmed items remain in the observation queue

Next, focus on three things: whether the vendor’s formal technical postmortem adjusts the affected scope; whether fixed releases and download signatures for each model continue to be updated; and whether there is evidence on-chain of losses and fund flows that can be independently corroborated. This account would rather keep the “coin-mixing” in the unconfirmed queue than let trending topics replace security facts. #BitcoinSecurity

For informational purposes only and does not constitute investment advice