MetaMask Removed On Google Play
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!
The MetaMask extension was pulled from the Google Chrome web store by mistake, which also listed multiple fake versions of MetaMask. While there is a strong possibility that users may have downloaded one of the fake versions during this time, there are no specific reports of any lost funds. The proper MetaMask extension was restored roughly 5 hours later.
This is a global/international case not involving a specific country.[1][2][3][4][5][6]
About MetaMask
MetaMask is a "crypto wallet & gateway to blockchain apps. Start exploring blockchain applications in seconds. Trusted by over 21 million users worldwide." "Available as a browser extension and as a mobile app, MetaMask equips you with a key vault, secure login, token wallet, and token exchange—everything you need to manage your digital assets."
"In July [of 2018], Google developers pulled the app from Google Play altogether, leaving only fake impersonations." "MetaMask was pulled from the Google Chrome Web Store, it announced in a tweet Wednesday, July 25."
"PSA: MetaMask has been delisted from the Chrome Web Store. We are unsure of why this is the case and we will update everyone as we get more information. All other browsers are unaffected."
"While @googlechrome has taken MetaMask down from their @ChromeDev store without notice or explanation, users can still install MetaMask manually on Chrome by following this guide. Note: @brave, @firefox, and @opera stores are all working fine!"
"The company stated that users who already have the extension installed on their Chrome browsers “should be unaffected” in the short term, but new installs would be unavailable for some time."
"If you already have the Chrome extension installed, you should be unaffected in the short term and your extension should work (knocks on wood). We hope to resolve this quickly, but future installs are still available on @brave, @firefox, and @opera."
"While the app was delisted, Augur, an Ethereum-based prediction market protocol, tweeted a warning to its users to not download the MetaMask extension that was actually present in Google Chrome’s store, as it was a fake, phishing application."
"The @metamask_io currently listed in the @googlechrome app store is a fake, phishing app. Do NOT download. The real MetaMask extension has been removed this morning without explanation. Follow @metamask_io for updates."
"A subsequent report from MetaMask revealed the [removal] action had occurred by mistake."
"The app has since been listed again, the company confirmed in a post five hours later."
"PSA2: We are back on the chrome webstore. Stay tuned for a formal retrospective from the team."
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.
| Date | Event | Description |
|---|---|---|
| July 25th, 2018 8:24:00 AM 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 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
- ↑ Fake MetaMask Crypto Malware Pulled From Google Play After Tipoff (Mar 6, 2022)
- ↑ MetaMask Browser Extension Pulled From Google Chrome Store for 5 Hours, ‘Unsure’ of Cause (Mar 15, 2022)
- ↑ @MetaMask Twitter (Mar 15, 2022)
- ↑ @MetaMask Twitter (Mar 16, 2022)
- ↑ @AugurProject Twitter (Mar 16, 2022)
- ↑ @MetaMask Twitter (Mar 16, 2022)