Ledger Upgrade Phishing Success _Scorpic_
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!
Details are limited, but it appears that a user was tricked during the Ledger upgrade process into doing an action which compromised their wallet.
While the user insists they did not enter their seed phrase, they may have been tricked into running a malicious transaction that gave the attacker access to the fund in their wallet.
This is a global/international case not involving a specific country.[1][2][3][4][5][6]
About Ledger
"Based in France, Ledger is the largest cryptocurrency hardware wallet company." "Ledger is a hardware cryptocurrency wallet that is used to store, manage, and sell cryptocurrency. The funds held in these wallets are secured using a 24-word recovery phrase and an optional secret passphrase that only the owner knows."
"Ledger offers two products, the Nano S and Nano X, that can store the digital keys used to secure crypto wallets. The devices can be used with a variety of cryptocurrencies, are compatible with numerous apps, and are supposed to offer a safe way to manage crypto without compromising too much on convenience. Ledger says on its website that it has sold 1.5 million products to customers in 165 countries to date."
"I am get Ledger Live 2.10.0 and install. After login and see new firmware 1.6.1 make upgrade. Ledger is upgarded ok. After install new app in Ledger and see outbound transaction, but i am not make it transaction, sure!!!! I am not crazy!!!! You can help me? what happened?"
"I am open Ledger Live (without connect Ledger) and see that have new Ledger Live 2.10.0 update. Click upgrade. Install it."
"Open new Ledger Live 2.10.0, Manager mode and connect Ledger see message NEW Firrmware 1.6.1 click update Firmware. Ledger Live download firmware. Get message about 24 word, what you need to know 24 words. Confirm it. After get message with code ID message 1-4 on Live Ledger in on Ledger, check it and confirm." "I am not enter 24 words!!!"
"After start firmware upgrade Ledger, Boot and firmware."
"After reboot Ledger enter PIN. Ledger Live inform me about reinstall App on Ledger. Confirm it. App download and install."
"See Outboard transaction in ETH."
"I am not open App ETH on Ledger and not make confirm it. SURE!!!"
"[T]here are 4 transactions made to the address to the same adress, if you look at the other adresses all 4 have transactions from Ethermine (0xEA674fdDe714fd979de3EdF0F56AA9716B898ec8) in their previous transactions." "I do not think it is linked to the ledger device, but possibly to some malicious software you have installed is possibly the problem."
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 |
|---|---|---|
| August 20th, 2020 11:52:34 AM MDT | 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 has been estimated at $2,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
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
Always download updates from the official website of Ledger. Store the majority of your funds in a fully offline wallet, which you don't typically interact with.
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
- ↑ Ledger Live 2.10.0 + Upgrade firmware 1.6.1 = outbound transaction : ledgerwallet (Mar 30, 2022)
- ↑ Ledger Live : Most trusted & secure crypto wallet | Ledger (Feb 13, 2022)
- ↑ Ledger Refuses Refunds, Tells Clients “Bank Vault Is More Secure” | Financegates (Mar 19, 2022)
- ↑ Physical Addresses of 270K Ledger Owners Leaked On Hacker Forum - Slashdot (Mar 19, 2022)
- ↑ Scammers Are Using Fake Devices to Steal Cryptocurrency Wallets | PCMag (Mar 6, 2022)
- ↑ https://etherscan.io/tx/0xdee62fe2dfce359070d8857b553029d6d743a41c7ba3f9e133cbb151bb07d8b7 (May 20, 2022)