COLDCARD RNG incident the public record, collected and explained
Informational only, and this site never asks for your seed words. details

Informational only. This is an open source collection of what others have published about the incident, together with an explanation of it. It is not financial, security or legal advice, and not a substitute for professional advice about your own situation. It is not affiliated with, endorsed by, or speaking for Coinkite. Material is attributed and quoted as published; where sources disagree their scenarios are kept separate with their assumptions rather than reconciled into one answer. Everything is meant to be checked against the linked evidence rather than taken on trust. Act on your own judgement about a particular situation. Editorial standards and corrections.

Do not disclose recovery material to a website, form, message or support account. This site never asks for it, and contributions containing recovery words or private keys are not accepted.

Tail risk of a further undisclosed COLDCARD exploit

w_s_bitcoin-undisclosed-exploit-tail-risk

https://x.com/w_s_bitcoin/status/2086971108071285190

Captured screenshot of the post by @w_s_bitcoin, posted 11 Aug 2026, 00:21 UTC
@w_s_bitcoin posted captured full-size capture → original post →
Author
@w_s_bitcoin
Organisation
independent
Evidence role
social statement
Posted
Capture status
capture held

Wicked says he is not ruling out the possibility of another yet-to-be-discovered COLDCARD exploit, gives nonce exfiltration in shipped firmware as an example, and lists precautions such as flashing verified firmware, generating own entropy and multivendor multisig. Held as a reported tail-risk warning and mitigation advice from a commentator. The existence of another exploit is unverified.

This post is registered as evidence and has a locally held capture. The original remains the canonical publication.

How to check this yourself

Compare the screenshot or a quotation against the original while it is available.