TheMetaBucks Discord Hacked

From Quadriga Initiative Cryptocurrency Hacks, Scams, and Frauds Repository
Jump to navigation Jump to search

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!

TheMetaBucks Discord Hack

Meta Bucks U.M.I. introduced "The Meta Bucks UMI" as their version of an NFT, providing lifetime access to opportunities within their ecosystem and ensuring secure identification in web3. The initiative aims to build trust within global communities. Leveraging the Ethereum Blockchain, the project deploys solutions for travelers, renters, homeowners, and lenders, utilizing smart contracts for real estate transactions. The platform focuses on entering markets, starting with Los Angeles county, to create bespoke communities. Unfortunately, Meta Bucks faced a compromise, specifically mentioning a compromised account (jayy#5346) causing problems and urging users not to click any links associated with it. There's an acknowledgment of a similar HTML layout being used in an attack against Meta Bucks the previous day.

This is a global/international case not involving a specific country.[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15]

About None

""GOOD FORTUNES BAKED INSIDE" The Meta Bucks the meta bucks U.M.I. is here... mint yours today"

"Unique Membership Identifiers Know Your Company "The Meta Bucks UMI" is our version of an "NFT". It grants lifetime access to opportunities in our ecosystem, while enabling you to be safely identified in web3. Build trust inside your global community like never before. Know your company..."

"YOUR PLACE Your Contract Leveraging the Ethereum Blockchain, we deploy solutions for travelers, renters, homeowners and lenders. Smart Contracts for real estate, that actualize ownership of real life assets. Sales settled on the blockchain make way for faster transaction speeds, exciting new ways to own a home, & vacations like never before."

"Los Angeles county is the first of many markets we will enter to build our bespoke communities. We hope that you can join us on this journey. By working with us to get to know you as a person, you can harness this opportunity to transition from a renter to an owner, Building equity every time you pay rent.*"

"Metabucks was compromised due to Giveaway boat we are currently working on restoring everything. Please do not click any links! The account in question that has caused the problems is jayy#5346, discord id# is 321694601360572416 Please make sure you ban this account to stay safe!"

"Very interesting that the same HTML layout was being used in an attack against Meta Bucks yesterday"

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.

Key Event Timeline - TheMetaBucks Discord Hacked
Date Event Description
May 21st, 2022 8:23:00 PM MDT Twitter Warning Twitter user xLordofSimpsx warns that the META Buckes discord is hacked and users should not click any links.
May 21st, 2022 9:19:00 PM MDT JoshBusd Announcement A community leader JoshBusd posts that they are aware of the attack and working on resolving the discord.
May 22nd, 2022 10:02:00 AM MDT Same Layout Reused Twitter user Erfie mentions that the same layout has been reused in an attack where the Beeple Twitter was taken over.

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?

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