DIN Twitter Account Breach Ransom Attempt
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!
DIN stands for Data Intelligence Network. The DIN network allows participants to get paid for providing computation for AI to use. On September 19th, 2024, a phishing link was posted on the DIN Twitter after their account was breached. Multiple users have reported potential losses. It is unclear if the DIN team will be doing anything to assist those users.[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21][22]
About DIN Lol
"DIN is the First Modular AI-Native Data Pre-Processing Layer. Created from the foundation of the Data Intelligence Network, DIN is designed to empower everyone to cook data for AI and get paid."
"DIN Is Finally There For Everyone! Total supply is 5 billion DIN tokens, with 10% set aside for the first airdrop. Finally all our community is invited to claim their $DIN tokens, based on wallets allocation. Check your allocation here!"
The Reality
"Upon clicking to connect wallet I get the dreaded red warning screen calling the page a phishin site, come on din you're better than that!Earn rewards by powering the DIN ecosystem with your Chipper Node. Join the AI data revolution. @din_lol_ GODIN"
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 |
|---|---|---|
| September 19th, 2024 6:00:00 AM MDT | Estimated Time Of Breach | The estimated time of the breach, according to the DIN team. |
| September 19th, 2024 8:26:00 AM MDT | Announcement About Hack | DIN founder Harold posts on his X account to warn about the breach and that users should not click on any links in the Twitter account for now. |
| September 19th, 2024 3:15:00 PM MDT | User Reports Being Scammed | One user reports being scammed and losing their funds, along with a screenshot of the phishing links. |
| September 19th, 2024 11:29:00 PM MDT | Community Poll Announcement | They have reached the hacker and he has offered $20k to return the account. They run a poll with the community, where 80% say not to pay the ransom demand. |
| September 20th, 2024 6:55:00 AM MDT | Recovery Announcement Tweet | The DIN team announces the recovery of their Twitter account. |
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
"The official X account of AI Modular Data Preprocessing Layer DIN was hacked, and a large number of phishing posts and links were sent."
"Our offcial account is hacked, please DO NOT click any link sent by the @din_lol_ for now"
Ultimate Outcome
"24 hours ago, at around 8 PM (UTC+8) on September 19th, our official X account @din_lol_ was hacked due to an external attack by a phishing group and sent numerous phishing posts and links, but the issue has now been ✨resolved. #DIN team has regained full control of the account!
A huge thank you to our community members, partners, investors, and all our friends in the industry for your collective effort!
The past 24 hours have been intense, and we want to make sure all of you know what happened during this time.
We informed the community and partners right away through Discord, Telegram, and the founder’s X account @Harold_DINlol
An appeal was immediately submitted to @X official support team, and we worked tirelessly through every possible channel to expedite the process.
We eventually succeeded in contacting @X official support team, providing them with our company’s relevant information. After verification, they helped freeze the account, and with their assistance, we were able to successfully regain full ownership of it.
At the same time, we also contacted the hacker, who demanded at least $20k from us. However, we couldn’t be sure that paying the ransom would result in the account being returned.
As a result, our founder @Harold_DINlol started a poll, and 80% of respondents encouraged us not to give in to the hacker’s demands. Our community also supported us to keep #fighting, and in the end, we prevailed and regained control of our official #X account!
We apologize for the losses some users may have experienced due to the hacker attack. This incident has made us realize the critical importance of social media account security, which is why we’re taking steps to strengthen it across the board. We also want to remind everyone in the industry to stay vigilant against phishing content and links
If you come across any suspicious information, please verify its authenticity with our community immediately.
Thank you to our community members, partners, and investors for your incredible support during the challenging last 24 hours. Please be sure to use our official links, which you can find in our Linktree.
As the crypto market begins to recover, we have more exciting news on the way, stay tuned!"
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
- ↑ @din_lol_ Twitter (Accessed Oct 22, 2024)
- ↑ @Harold_DINlol Twitter (Accessed Oct 22, 2024)
- ↑ @Harold_DINlol Twitter (Accessed Oct 22, 2024)
- ↑ @Harold_DINlol Twitter (Accessed Oct 22, 2024)
- ↑ @0xmrjack Twitter (Accessed Oct 22, 2024)
- ↑ DIN (Accessed Oct 22, 2024)
- ↑ ⏳ Overview | DIN: Cook Data for AI (Accessed Oct 22, 2024)
- ↑ ️ Our Journey | DIN: Cook Data for AI (Accessed Oct 22, 2024)
- ↑ @0xmrjack Twitter (Accessed Oct 22, 2024)
- ↑ @CFHGoreGrinder Twitter (Accessed Oct 22, 2024)
- ↑ @snwdnnn Twitter (Accessed Oct 22, 2024)
- ↑ @0xmrjack Twitter (Accessed Oct 22, 2024)
- ↑ @Brunosamz Twitter (Accessed Oct 22, 2024)
- ↑ @0xmrjack Twitter (Accessed Oct 22, 2024)
- ↑ @snwdnnn Twitter (Accessed Oct 22, 2024)
- ↑ @snwdnnn Twitter (Accessed Oct 22, 2024)
- ↑ @CricFeroz Twitter (Accessed Oct 22, 2024)
- ↑ @snwdnnn Twitter (Accessed Oct 22, 2024)
- ↑ @hussam_hindawi Twitter (Accessed Oct 22, 2024)
- ↑ @zhunzhun168 Twitter (Accessed Oct 22, 2024)
- ↑ @Web3catalyst01 Twitter (Accessed Oct 22, 2024)
- ↑ @lone2k00 Twitter (Accessed Oct 22, 2024)