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.

Afilini 2085021651918332071

afilini-2085021651918332071

https://x.com/afilini/status/2085021651918332071

Captured screenshot of the post by @afilini, posted 5 Aug 2026, 15:14 UTC
@afilini posted captured full-size capture → original post →
Author
@afilini
Organisation
independent
Evidence role
independent-technical-analysis
Posted
Capture status
capture held

Alekos Filini's first post on finding that the commit introducing libngu replaced only some RNG calls with the vulnerable version. The moment the selective-migration observation was first published, ahead of the full report; the gist is registered at afilini-seed-rng-migration-report and states the git commands the claim rests on.

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.