Ledger CVHodl Theft
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' and 'General Prevention' sections 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!
CVHodl had his funds taken from his Ledger, and it appears he was unable to recover them. It is unclear how much was lost, and the exact nature of the attack. Generally, most cases involve the user being phished to provide their seed phrase.
This is a global/international case not involving a specific country.[1][2][3][4][5][6][7][8][9]
About Ledger
"On April 4th my ledger was connected to my computer and I logged in to metamask to do a transaction. When I was connected I was shocked to see all of my crypto missing. I went to Etherscan and traced the addresses and contacted iDEX and Binance as the crypto was sent to those exchanges and well ForkDelta (obviously gone as its a DEX). iDEX was able to freeze the person's exchange account bit I did not get back any of it, and well Binance support basically brushed me off and told me to contact my local law enforcement for assistance....really! I am really shocked at what has happened because no one has access to my ledger or phrase."
"I had a similar issue last year using chrome. Lost a significant amount of crypto on one of my Ledgers. @Ledger did respond, @idexio assisted and @binance brushed me off though I provided a significant amount of information showing the tokens sent to the exchange."
"@cz_binance Please improve your support. Some crypto was stolen from my wallet and sent to Binance & Idex. I sent all details (addresses, txs etc.) to support who kept replying to seek help from the police, yet @Aurora_dao was able to freeze their account with the info provided."
"This same thing happened to me last month with no recourse. Plugged on my ledger (bought directly from them) and immediately fell sick to see all my crypto gone. I'm not using those again. Would love to see @Ledger get involved."
"It's quite easy to brush off the issue and say, "go to the police," when it is clear that the most police services (depending on where you live) do not know anything about crypto or can help in any way. A little consideration can go a long way, but I am no whale so...I guess not."
This is a global/international case not involving a specific country.
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 |
|---|---|---|
| April 4th, 2019 | Main Event | Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here. |
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 is unknown.
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
There do not appear to have been any funds recovered in this case.
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?
General Prevention Policies
CVHodl himself provided some tips on his site at cvhodl.com/securebitcoin.
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
- ↑ @CVHodl Twitter (Mar 19, 2022)
- ↑ @CVHodl Twitter (Mar 25, 2022)
- ↑ @CVHodl Twitter (Mar 26, 2022)
- ↑ No refunds in ₿itcoin! Do you want to secure them? - CVHODL (Mar 26, 2022)
- ↑ @CVHodl Twitter (Apr 30, 2022)
- ↑ @CVHodl Twitter (Apr 30, 2022)
- ↑ @CVHodl Twitter (Apr 30, 2022)
- ↑ @CVHodl Twitter (Apr 30, 2022)
- ↑ @CVHodl Twitter (Apr 30, 2022)