TURBO BOBO GORILLA Phishing Inferno Drainer
Notice: This page is a freshly imported case study from an original repository. While the original content had a similar format, some sections may not have been fully completed. Please help fill in any empty sections or any missing information 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!
Gemini, Binance, Kraken customer with address 0x6435...1390 fell victim to a phishing website and lost a significant number of tokens including TURBO, BOBO, GORILLA, GROK, and SHRAP. There is limited information about what happened, or anything which was done about a recovery.[1][2][3][4][5][6][7]
About 0x6435...1390
Gemini, Binance, Kraken customer. tokens including TURBO, BOBO, GORILLA, GROK, and SHRAP.
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
"Address 0x6435...1390 fallen victim to a phishing scheme, and lost ~$1.55M worth of tokens."
| Date | Event | Description |
|---|---|---|
| June 1st, 2024 3:17:59 PM MDT | Blockchain Transaction | Blockchain transaction draining the wallet happens. |
| June 1st, 2024 9:40:00 PM MDT | ChainAegis Tweet | ChainAegis tweets about the loss. |
Technical Details
"In suspicious fund transfer, the victim's tokens are transferred to the attacker-controlled account. The attack is usually launched through social engineering, e.g., asking users to click a link to claim some rewards or AirDrop tokens."
"In this transaction, the TURBO token of the user (0x6435b) was transferred to the attacker (0xfc4ea). Since the attacker's account (0xfc4ea) was involved in several phishing scam incidents, we believe the user (0x6435b) was deceived into signing the approval transaction."
Total Amount Lost
"lost ~$1.55M worth of tokens."
The total amount lost has been estimated at $1,550,000 USD.
Immediate Reactions
"Address 0x6435...1390 fallen victim to a phishing scheme, and lost ~$1.55M worth of tokens.
The phishing address points to #InfernoDrainer"
"In suspicious fund transfer, the victim's tokens are transferred to the attacker-controlled account. The attack is usually launched through social engineering, e.g., asking users to click a link to claim some rewards or AirDrop tokens."
"In this transaction, the TURBO token of the user (0x6435b) was transferred to the attacker (0xfc4ea). Since the attacker's account (0xfc4ea) was involved in several phishing scam incidents, we believe the user (0x6435b) was deceived into signing the approval transaction."
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
- ↑ @ChainAegis Twitter (Accessed Jul 3, 2024)
- ↑ ChainAegis (Accessed Jul 3, 2024)
- ↑ Ethereum Transaction Hash (Txhash) Details | Etherscan (Accessed Jul 3, 2024)
- ↑ https://metasleuth.io/result/eth/0x6435b50861c5895c82a0789c6f91b80561ec1390 (Accessed Jul 3, 2024)
- ↑ List of Crypto Phishing Attacks - ImmuneBytes (Accessed Jul 3, 2024)
- ↑ https://metasleuth.io/report/d980a3f5a8870d74b6fd8facfbe5f08b (Accessed Jul 3, 2024)
- ↑ https://dexcheck.ai/app/wallet-analyzer/0x6435b50861c5895c82a0789c6f91b80561ec1390 (Accessed Jul 3, 2024)