← Feed
@sailor_sega_saturn@awful.systems
Post #4388438
2026-08-05 03:01 UTC
There was a cryptocurrency wallet hack the other day which has so far gone unremarked here because the popcorn is stale and we all pivoted to AI. And yet there are dozens of voices of bagholders crying out in pain wanting to be heard. This is their story.
For some reason the best explanation comes from a boring company that makes point of sale credit card readers …block.xyz/…/predictable-rng-fallback-and-32-bit-…
COLDCARD firmware contains an RNG integration error that causes ngu.random to use MicroPython’s deterministic Yasmarang fallback instead of the STM32 hardware RNG.
Oh hey they got the most important thing not to get wrong wrong in the regulation free money settlement layer of the future.
The bug? Well in one file they wrote #define MICROPY_HW_ENABLE_RNG 0, and a library they depended on had this code:
# ifndef MICROPY_HW_ENABLE_RNG
# error "get a HW TRNG plz"
# endif
This should have caused a build failure, but since MICROPY_HW_ENABLE_RNG was defined, to zero, it did not.
As a C++ programmer this isn’t an unheard of sort of mistake to make in the moment. Many libraries use undefined for preprocessor variables, but there are some people who prefer zero.
But it’s less excusable to not catch it when this is literally the most important thing to get right in a bitcoin wallet. Did they not trace the code path when writing the code? Did they have no integration tests or unit tests for RNG seed quality? Poor RNG seeding has come up a ton in literature, so is the sort of thing people writing cryptographic code should check for…
We’ll have to addend that old saying: “don’t roll your own crypto unless the other person’s crypto is from a blockchain developer in which case you’re probably better off rolling your own after all.”
I personally don’t want to sneer at the bagholders too much here. It’s 2026 and at this point it just feels kinda sad. But I’ll end this comment with this glowing review:
I thought I was secure because Cold Card was always praised as one of the best and most secure wallets. It’s open source, so anyone can verify.
“It’s open source, so anyone can verify” – unfortunately for them the verifier was also a hacker.
Replies (2)
-
I’ve been following it a bit, there’s a lot less comedy gold to mine nowadays
here are some links from another forum
coindesk.com/…/major-bitcoin-wallet-flaw-drains-5… (crypto shill outfit link)
bitcoinenthusiast.org/uploads/…/image.png
bitcoinenthusiast.org/uploads/…/image.png - this last is attributing to malice what’s clearly stupidity
Open ##4391988
-
I was gonna link someone else’s observations on it, but got sidetracked by a shiny object or something.
mastodon.catgirl.cloud/@49016/117021988214007605
They didn’t link the sources, but apparently the all-my-apes-gone twitter crowd are still breathtakingly ignorant of technology and statistics, despite how many years of bitcoin catastrophes have passed.
Quite a few people suggesting/using dice to mitigate the Coldcard vulnerability.
Note that common dice are not designed to be cryptographically secure.
If you are going to do this, you probably should buy precision casino dice. And even then, have another source of entropy.
Posted entirely unironically, apparently. Hard to say, but Poe’s law has yet t be repealed.
Open ##4408026