Pixel-Track Hex Tokens Stolen

From Quadriga Initiative Cryptocurrency Hacks, Scams, and Frauds Repository
Revision as of 12:28, 3 May 2023 by Azoundria (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
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' and 'General Prevention' sections 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!

MetaMask

Reddit user Pixel-Track introduces themselves as someone from an older generation who is not experienced with cryptocurrency. They reported that they did not share their seed phrase or private key with anyone, however they were attempting to stake their HEX tokens and this was not successful. They report that their funds were taken without authorization. Their wallet shows a transfer of 812,058.73040511 HEX tokens (worth $120,952.02 USD at the time) on April 13th, just prior to their reported post.

Their Reddit post was removed due to a lack of comment karma before they could be helped in any way by the cryptocurrency community.


This is a global/international case not involving a specific country.[1][2][3][4][5][6]

About MetaMask

"I am a little bit older and new." "I am new and older generation." "It was 10 years that I collect the money for my future and for my friend and old mother." "I have been collecting this money for 10 years for retirement."

"90k of HEX." "I send ETH to my Metamask wallet and by HEX, than I try to stake HEX in 365 day some HEX but nothing happens 7 days."

"[T]han all HEX gone." "[M]y Metamask vas hacked and it is gone." "I can see transaction from my account to some another account. I didnt do this, and I have phrases and pass[words]. That day my computer was turned off all day. I dont know what to do, what is happened."

"I tried to stake HEX but all is gone. I never ever [I] never gave keys or data and [I] don't know if this happened." "How can I contact Metamask or HEX? Am I currently steaking some HEX are they can take that away from me as well?"

"I can see the wallet but how can I send it back the last 3 transactions I didn['t] do. I am new in crypto I dont know what to do. 1 day ago I was on travel and my compute[r] wasn[']t [even] turned on. [In] my Metamask wallet you can see last 4 transactions."

"Hello, your post was removed because your account is less than 60 days old or you do not have the required 500 comment karma to make post submissions."

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 - Pixel-Track Hex Tokens Stolen
Date Event Description
August 13th, 2021 2:40:13 PM MDT 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 $121,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?

General Prevention Policies

While the exact method is unknown, it seems very likely that their method of storing their seed phrase was not secure. They may also have interacted with an attack website and provided this information, and forgotten the specific details.

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