- Organisation
- Milk Sad research team
- Evidence role
- Primary technical research
- Published
- 2023-08-08
- Source changes
- 0
- Detected differences
- 0
- Unreviewed
- 0
- Copies held
- 1
Primary disclosure for CVE-2023-39910, including the 32-bit MT19937 seed funnel, partial impact accounting and comparison with the Trust Wallet incident.
Every check is recorded, including checks that found no text change. A detected edit is therefore bounded between two checks. The publisher's exact save time is not observable from this record. Last checked 2 Aug 2026, 00:59 UTC.
Snapshot and diff bodies for this chain monitor are held in the local evidence archive but withheld from the public site because they can contain victim addresses. Integrity hashes, capture times and reviewed change summaries remain available below.
-
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 0 lines
Extracted text as captured
Milk Sad /home /updates /bx summary /bx full write-up /38c3 /faq Technical write-up for CVE-2023-31290 This is the story of a wallet theft enabled by bad cryptography. It covers our research on problems with Libbitcoin Explorer 3.x (CVE-2023-39910), outlines how it is related to the Trust Wallet vulnerability (CVE-2023-31290), and shows some of the real-world impact that we were able to confirm. Additionally, it has some early research on problems with bx 2.x that we became aware of late in the disclosure process. If you’re looking for a less-technical summary, head over to the summary page and the FAQs. Table of Contents Part I - Tracing the Issue to the Source Dude, Where’s my Cryptocurrency? Dude, Where’s my Friend’s Cryptocurrency? Our Cryptocurrency is Gone, But How!?!? Part II - Context and Impact Codename “Milk Sad” Not the First Hack: Weak entropy in Cake Wallet Not even the second Hack: Mersenne Twister use in Trust Wallet Ongoing On-Chain Thefts - Some Facts Searching for Wallets - Motivation and Limits Searching for Wallets - Implementation Other Confirmed Victims of this Theft Basic Timeline of Thefts and Our Disclosure Libbitcoin Team Response and Context Suspected RNG Problems in Older bx Versions Part III - Summary and Outlook Basic Lessons Learned Summary Future Work Additional References Commercial Work Other Notes Credits Part I - Tracing the Issue to the Source Please note that throughout this article, minor details relating to the victims have been omitted or changed. Dude, Where’s my Cryptocurrency? Our story starts on Friday, 21 July 2023. Upon attempting to use a well-protected cryptocurrency wallet, the wallet owner realizes that all of their funds stored in their wallet are gone. This was no accident – they were the victim of a sophisticated theft. The funds were sent to the attacker’s addresses on July 12th, at a time when the hardware wallet wasn’t in use for several days. (Details below) The generation and use of the affected wallet was unusually strict:Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
Each copy above is identified by the SHA-256 of its extracted text, shown beside it, and the diffs are plain unified diffs. To verify a quotation, compare it against the page itself or against the Internet Archive's copies, which are independent of this project.
Complete captures are held offline rather than mirrored here, so this page shows diffs and excerpts. If a quotation is ever disputed, the full copy can be produced. Ask.
The SHA-256 prefixes above identify each held copy without turning this page into a mirror of somebody else's post. Compare a quotation against the original. If the post has since been edited or deleted, ask and the held copy can be produced.