Azuki Beanz The Other Side Mfer NFT Thefts Rijet

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!

Azuki Beanz Phishing Site

After interacting with thwat they thought was the real site for the Azuki Beanz NFT project, Twitter user rijet found that their wallet had been emptied of two NFTs. Mfer #6135 and TheOtherSide #1981 were both taken. Mfer #6135 has been resold multiple times, while TheOtherSide #1981 is still remaining in the thief's wallet. While the theft has been reported to the NFT creators and OpenSea, no recovery has occurred.

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][16][17][18][19][20][21][22][23][24]

About None

"@ryandisdier I mistakenly click on this link and my @sartoshi_nft NFT Mfer #6135 was mistakenly transfered. I thought this was a legit link for Azuki. The other side @theothersideNFT nft #1981 was transfered to address 0xe69c778fa0a7a12bb0bfbd04d1fe4c9e8ebb9303 please help."

"@sartoshi_nft please help retrieve my mfer #6315. I did not sell the mfers. I bought this for 5eth two months ago. I clicked ib th link in the attached image Please help! #mfers please help retrieve my #mfer."

"@theothersideNFT please help retrieve nft #1981. I did not sell the mfers. I bought this for 0.5eth two months ago. I clicked ib th link http://beanz-azuki.org . Please help! #tos please help retrieve my #Theotherside"

"Winning this will surely make my day. My Mfer #6135 and The other side nft #1981 was just illegally transfered from my account. Reported this to opensea and the projects. Hopefully I hear back from them."

"I don't think you'll be getting those back. I got two NFTs stolen last month and still couldn't get it back. Even if @opensea tag the NFT as scam, the perpetrator can transfer to @LooksRareNFT worst marketplace ever. It promotes sale of stolen NFTs."

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 - Azuki Beanz The Other Side Mfer NFT Thefts Rijet
Date Event Description
April 14th, 2022 1:38:27 PM MDT Transfer Mfer 6315 The blockchain transfers stealing Mfer 6135 and The Other Side 1981 happen.
April 14th, 2022 1:49:57 PM MDT Request For Help Rijet posts another request for help on Twitter.
April 14th, 2022 1:59:00 PM MDT The Other Side Help Rijet is asking the creators of The Other Side NFT to help get him back his stolen NFT #1981.
April 14th, 2022 5:59:28 PM MDT Mfer NFT Resold The stolen Mfer NFT is resold on OpenSea for 3.02 ETH.
April 20th, 2022 8:56:57 AM MDT Mfer NFT Resold The stolen Mfer NFT is resold on LooksRare for 2.62 ETH.
May 18th, 2022 3:29:00 AM MDT Seth Green Reply Rijet replies to Seth Green to express pessimism at his prospects of him recovering his stolen NFT.

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

~0.5 ETH + 3.02 ETH = 3.52 ETH x $3,019.91 = 10630.0832

The total amount lost has been estimated at $11,000 USD.

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