Ledger Olusegun Alabi 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' 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!
On July 28th, 2019, the Ledger user Olusegun Alabi lost over 43 ETH, worth $8000 at the time. It's unclear how this compromise happened. Typically, this type of thing would happen through entering the seed phrase on a third party phishing website.
This is a global/international case not involving a specific country.[1][2][3][4][5][6]
About Ledger
"Over $8000 w[orth] of ETH and ETC vanishes from my Ledger and @Ledger turned me off."
"If you use @evernote and you have a @Huawei phone you can be compromised....Losing almost $20k has opened my eyes." "We believe the recent update that occurred on @binance and @Binance_DEX which added BEP8 to platform could have led to the compromise."
"Only if I could get back my 43ETH that stolen from me via hackers in 2019. At the time it was worth $8,000 today it's worth $70,000. I will overcome." "I was the second highest holder of CBM Coin with a little over 455million coins. And this individual began to sell of all my coins into BNB coin. @cz_binance @TrustWalletApp"
"We noticed the same individual could had previously hacked a different account before mine. I would appreciate if this could be looked into. @cz_binance @TrustWalletApp @Binance_DEX" "As we speak he still holds 217million of my CBM coins and has placed a sell order on those coins, see attached image for proof. @cz_binance @TrustWalletApp"
"This life, I got hacked should feel down, lost lots of cash but I hear a story of a friend not doing well, I still had compassion and sent him some money."
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 |
|---|---|---|
| July 28th, 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 has been estimated at $8,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?
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
- ↑ @segunalad Twitter (Mar 19, 2022)
- ↑ @segunalad Twitter (Mar 26, 2022)
- ↑ @segunalad Twitter (Mar 26, 2022)
- ↑ @segunalad Twitter (Mar 26, 2022)
- ↑ @segunalad Twitter (Mar 26, 2022)
- ↑ @segunalad Twitter (Mar 26, 2022)