Talos II RNG Exploit Theft Luke Dash Jr
Notice: This page is a freshly imported case study from the original repository. The original content was in a different format, and may not have relevant information for all sections. Please help restructure the content by moving information from the 'About' section to other sections, and add any missing information or sources you can find. If you are new here, please read General Tutorial on Wikis or Anatomy of a Case Study for help getting started.
Notice: This page contains sources which are not attributed to any text. The unattributed sources follow the initial description. Please assist by visiting each source, reviewing the content, and placing that reference next to any text it can be used to support. Feel free to add any information that you come across which isn't present already. Sources which don't contain any relevant information can be removed. Broken links can be replaced with versions from the Internet Archive. See General Tutorial on Wikis, Anatomy of a Case Study, and/or Citing Your Sources Guide for additional information. Thanks for your help!
Bitcoin core developer Luke Dashjr experienced a significant loss at the start of the new year, reportedly losing over 200 BTC in a hack. Dashjr revealed on Twitter that his PGP key was compromised, leading to the theft of many bitcoins. The stolen bitcoins were transferred to a wallet address using the Bitcoin mixer CoinJoin in four transactions, totaling approximately 216.93 BTC, equivalent to $3.6 million. In November, Dashjr's server was accessed by an unknown individual using new malware/backdoors, and on Christmas day, the server was reaccessed, resulting in the successful theft of over 200 Bitcoins. Binance CEO CZ expressed sympathy and pledged to freeze the funds if they come to Binance, sparking discussions in the crypto community about the risks and challenges of self-custody.
This exchange or platform is based in United States, or the incident targeted people primarily in United States.[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21][22][23][24][25][26][27][28][29][30][31]
About None
"Luke Dashjr, a developer who works on Bitcoin Core, the technology and security behind the cryptocurrency, has lost over 200 Bitcoins in an apparent hack."
It's well known that I run Gentoo on a Talos II with everything self compiled
they got it all, including a brand new 2FA I made the same day.
(Besides, as someone already pointed out, the wallets weren't on my main system.)
It's well known that I run Gentoo on a Talos II with everything self compiled
Talos II? It seems likely you were a victim of CVE-2019-15847 : The random number generator of Power9 (DARN instruction) was broken with GCC ->
If your main system (Talos II) was using a weak RNG then your private ssh keys could be compromised relatively easy, allowing the bad guys to get access to any device where you had ssh access. Once they got access they could have installed any backdoor or malicious software.
This exchange or platform is based in United States, or the incident targeted people primarily in United States.
The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.
Include:
- Known history of when and how the service was started.
- What problems does the company or service claim to solve?
- What marketing materials were used by the firm or business?
- Audits performed, and excerpts that may have been included.
- Business registration documents shown (fake or legitimate).
- How were people recruited to participate?
- Public warnings and announcements prior to the event.
Don't Include:
- Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
- Anything that wasn't reasonably knowable at the time of the event.
There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.
The Reality
This sections is included if a case involved deception or information that was unknown at the time. Examples include:
- When the service was actually started (if different than the "official story").
- Who actually ran a service and their own personal history.
- How the service was structured behind the scenes. (For example, there was no "trading bot".)
- Details of what audits reported and how vulnerabilities were missed during auditing.
What Happened
The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.
| Date | Event | Description |
|---|---|---|
| November 17th, 2022 6:01:00 AM MST | Server Access Report | "My server was accessed this morning by an unknown person. Full analysis in progress, but take extra care that you PGP-verified any downloads." |
| December 24th, 2022 10:32:00 PM MST | Further Server Access | "Someone did this again tonight, about 2 hours ago." "Calling out @ColoCrossing for (AFAIK) dropping the ball on abuse investigation last time. Also going to call out my server provider for dropping the ball on an internal audit, but I need a replacement first." |
| December 31st, 2022 7:07:50 AM MST | Bitcoin Transaction | A bitcoin transaction occurs transfering 199.17944420 BTC from Luke Dashjr's bitcoin wallet. |
| December 31st, 2022 7:08:45 AM MST | Bitcoin Transaction | Another bitcoin transaction occurs transfering 9.65740737 BTC more from Luke Dashjr's bitcoin wallet. |
| December 31st, 2022 7:10:10 AM MST | Bitcoin Transaction | Another bitcoin transaction occurs transfering 5.59516508 BTC more from Luke Dashjr's bitcoin wallet. |
| December 31st, 2022 7:11:08 AM MST | Bitcoin Transaction | Another bitcoin transaction occurs transfering 2.50127534 BTC more from Luke Dashjr's bitcoin wallet. |
| January 1st, 2023 11:13:00 AM MST | Tweet About Incident | Luke Dashjr posts about the incident on Twitter, asking the bitcoin community for "[h]elp please" because his "PGP key [wa]s compromised, and at least many of my bitcoins stolen. [He has] no idea how." |
| January 1st, 2023 2:08:00 PM MST | Transactions Provided | Luke Dashjr provides transaction IDs about the transfer of funds via Twitter. |
| January 1st, 2023 2:32:00 PM MST | CZ Comment On Theft | Binance's CZ comments to mention if any of the funds come their way, they will be frozen and asks if there's anything else they can do to help. |
| January 2nd, 2023 4:03:13 AM MST | Crypto Times Article | The Crypto Times publishes an article about the loss. |
| January 5th, 2023 7:00:03 AM MST | CoinDesk Panel Weigh-In | The CoinDesk panel weighs in on the exploit in a published YouTube video. They are still awaiting more details and expect there iwll be a post-mortem. |
Technical Details
This section includes specific detailed technical analysis of any security breaches which happened. What specific software vulnerabilities contributed to the problem and how were they exploited?
Total Amount Lost
The total amount lost has been estimated at $3,590,000 USD.
How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?
Immediate Reactions
How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?
Ultimate Outcome
What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?
Total Amount Recovered
The total amount recovered is unknown.
What funds were recovered? What funds were reimbursed for those affected users?
Ongoing Developments
What parts of this case are still remaining to be concluded?
Individual Prevention Policies
No specific policies for individual prevention have yet been identified in this case.
For the full list of how to protect your funds as an individual, check our Prevention Policies for Individuals guide.
Platform Prevention Policies
Policies for platforms to take to prevent this situation have not yet been selected in this case.
For the full list of how to protect your funds as a financial service, check our Prevention Policies for Platforms guide.
Regulatory Prevention Policies
No specific regulatory policies have yet been identified in this case.
For the full list of regulatory policies that can prevent loss, check our Prevention Policies for Regulators guide.
References
- ↑ Bitcoin developer loses $3.3 million in massive hack - Dexerto (Jan 6, 2023)
- ↑ @LukeDashjr Twitter (Nov 15, 2023)
- ↑ @OurielOhayon Twitter (Nov 15, 2023)
- ↑ 91481 – (CVE-2019-15847) POWER9 "DARN" RNG intrinsic produces repeated output (CVE-2019-15847) (Nov 15, 2023)
- ↑ xkcd: Random Number (Nov 15, 2023)
- ↑ @LukeDashjr Twitter (Nov 15, 2023)
- ↑ @LukeDashjr Twitter (Nov 15, 2023)
- ↑ @LukeDashjr Twitter (Nov 15, 2023)
- ↑ @LukeDashjr Twitter (Nov 15, 2023)
- ↑ @mytechmix Twitter (Nov 15, 2023)
- ↑ @tryboeck Twitter (Nov 15, 2023)
- ↑ Luke Dashjr, Early Bitcoin Developer, Says Hack Took His BTC (Nov 15, 2023)
- ↑ Bitcoin / Address / 1YAR6opJCfDjBNdn5bV8b5Mcu84tv92fa — Blockchair (Nov 15, 2023)
- ↑ Bitcoin Core Dev Says His BTC Is ‘Basically All Gone’ After Hack - YouTube (Nov 15, 2023)
- ↑ Bitcoin core developer claims to have lost 200+ BTC in hack (Nov 15, 2023)
- ↑ Reddit - Dive into anything (Nov 15, 2023)
- ↑ @MichaelDunwort1 Twitter (Nov 15, 2023)
- ↑ @LukeDashjr Twitter (Nov 15, 2023)
- ↑ @LukeDashjr Twitter (Nov 15, 2023)
- ↑ @LukeDashjr Twitter (Nov 15, 2023)
- ↑ @PsychedelicBart Twitter (Nov 15, 2023)
- ↑ Who's Luke Dashjr? (Nov 15, 2023)
- ↑ @LukeDashjr Twitter (Nov 15, 2023)
- ↑ @LukeDashjr Twitter (Nov 15, 2023)
- ↑ luke-jr (Luke Dashjr) · GitHub (Nov 15, 2023)
- ↑ https://www.linkedin.com/in/lukedashjr/ (Nov 15, 2023)
- ↑ Bitcoin price today, BTC live marketcap, chart, and info | CoinMarketCap (May 16, 2021)
- ↑ Transaction: 432ded946431a9612f09d73bd15ded045d11d1095ffdfe8d68306ea9b2e78930 | Blockchain.com (Nov 15, 2023)
- ↑ Transaction: c38a3210fbb758cfc41d9a64b7534b83aecca96f051231f15545e8e5c7365190 | Blockchain.com (Nov 15, 2023)
- ↑ Transaction: 4b3cde50e2bce3d02e15b61957d2452e29f53d9a99e1ab14e83b6ec0f87fd851 | Blockchain.com (Nov 15, 2023)
- ↑ Transaction: 50df1eab0bf2bd01999cea4fc531a65c17e1a285823c9ae4eab0feb7e21a11b6 | Blockchain.com (Nov 15, 2023)