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.

Claimed 2014 origin of a JavaScript RNG weakness

julianor-2085162138956374408

https://x.com/julianor/status/2085162138956374408

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

Juliano Rizzo posts the line "Introduced in 2014, wallet drain exploit detected in 2026:" over a screenshot of a discussion dated 25 April 2014, addressed to @daviddahl, about JavaScript entropy: it offers a custom generator built on Knuth's linear congruential PRNG, seeded in part from Math.random, and closes by noting the result is still predictable if you control all the parameters. The post names neither the library nor the 2026 drain it has in mind, and the code shown is JavaScript library code rather than COLDCARD firmware. Held because a security researcher is dating a second, separate entropy failure to 2014 and tying it to a 2026 drain, a parallel MAGS draws explicitly a few hours later at crypto_mags-2085586783803453912. The identification and the connection are the poster's own and are not verified here.

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.