MetaMask Wallet Profile: US Access and Key Risks

MetaMask is best understood as a self-custody software wallet, with optional services that have their own access rules and risk boundaries. This profile separates the core wallet from staking, the payment card and trading-related products, then places the operator, US access record, SEC case and September 2026 incident in their documented context.

Source snapshot: October 20, 2026. SEC source checks retained in the evidence record are dated September 26, 2026.

What MetaMask is and who operates it

MetaMask launched in 2016 and provides a self-custody wallet through a browser extension and mobile app. The product description comes from MetaMask's 10th-anniversary announcement 2.

The operator recorded in the evidence record is ConsenSys Software Inc., United States. Crunchbase records Fort Worth, Texas as the headquarters, while the evidence record does not identify a state of legal incorporation for the company 14. That distinction matters when reading corporate records: a headquarters location is not the same thing as a formation jurisdiction.

The wallet is one product layer under the MetaMask name. Its self-custody model means the profile should not automatically apply a statement about wallet access to staking infrastructure, the card or other optional services.

Wallet, staking and card: different product layers

A reader considering a MetaMask feature should first identify which layer is involved. The evidence record supports the following comparison:

Product layer	Custody or control described in evidence record	Platform or use	Scope supported by the evidence record
Core wallet	Self-custody	Browser extension and mobile app	US and New York wallet access 27
MetaMask Staking	Users retain withdrawal keys in the incident reports	Ethereum validator infrastructure	September 2026 infrastructure event; separate from wallet compromise 131415
MetaMask Card	Card issuer is a separate partner; no custody claim is made here	Payments	Dated US rollout and separate enrollment message 689

This table compares MetaMask's own product layers. It does not establish service quality, recovery support or the safety of one layer from the status of another.

US and New York availability

For the core wallet, the snapshot records US access with no state exclusions recorded. It also records US-NY access for the core wallet. The New York entry has no regulatory basis recorded in this dataset, which describes access rather than a documented New York license 267.

MetaMask's July 14, 2026 anniversary announcement described availability in approximately 190 countries. That global figure does not mean every optional service is available in every country 2. The prepared country record separately states that the Hyperliquid perpetual-futures product is unavailable in the United States 7. MetaMask's announcement for Ondo tokenized stocks, ETFs and commodities also says those products are unavailable to US persons 10.

The card has a separate timeline. MetaMask's February 26, 2026 launch announcement described US availability in 49 states, including New York, with Vermont excluded 6. A separate card-page capture in the evidence record says US and UK registration is temporarily closed; its original capture date is not stated 8. Those are separate statements, not a present-tense promise that enrollment is open.

The US card issuer is Cross River Bank, described in the card coverage as FDIC-insured 69. That description applies to the bank and card arrangement. It does not mean crypto held in the MetaMask wallet has FDIC protection.

Availability does not establish a license

The prepared snapshot contains an empty operator-specific license field. That is a description of the dataset, not proof that no license or registration exists anywhere, and it does not establish a universal legal conclusion about MetaMask or ConsenSys Software Inc.

The wallet's availability record therefore needs to be read separately from regulatory status. A person in New York can have access to a self-custody wallet without that access itself being evidence of a New York license. The same separation applies to the card: Cross River Bank's described FDIC-insured status belongs to the bank and card product, not to wallet balances.

This profile does not use a generic licensing guide to fill the empty field. It also does not treat the wallet's self-custody structure as a blanket answer for optional services.

The SEC case and the 2026 staking incident

The regulatory history has two dated events:

• On June 28, 2024, the SEC filed an action against ConsenSys Software Inc. involving allegations about registration requirements connected with MetaMask Staking and MetaMask Swaps 18.
• On March 27, 2025, the SEC announced that the case had been dismissed with prejudice. The evidence record records no fine and no admission of wrongdoing 19.

A dismissal is not a license entry or a blanket finding that every MetaMask product has regulatory approval. Its scope is the case and its disposition.

The September 30, 2026 event concerned part of the MetaMask Staking infrastructure, not a general compromise of the core wallet. Reports describe preventive validator exits by October 7. External researcher Kaden estimated that rewards from 18 of 19 affected Ethereum validators had been redirected, totaling approximately 0.36 ETH. That figure is a researcher estimate, not a number attributed to MetaMask 1314.

The company-attributed statement in the incident coverage said that user wallets were not threatened, while the reports state that users retained withdrawal keys. The event therefore belongs to the staking infrastructure layer. It should not be presented as evidence that every MetaMask wallet was hacked or that wallet balances were redirected 131415.

How to decide whether MetaMask fits

MetaMask is relevant to a reader seeking a self-custody software wallet. The decision changes when the feature under consideration is a card, staking infrastructure, perpetual futures or tokenized assets. Each has its own eligibility statement and incident history.

This profile is Not yet rated. It is a documentary profile rather than a scored recommendation, so popularity does not establish service quality or individual suitability.

Product-scope decision checklist

• Identify the feature being considered.
• Separate core-wallet access from that feature's eligibility.
• Apply the dated limitation recorded for that product layer: the wallet access record is distinct from the Hyperliquid, Ondo and card statements 26710.

For broader context, Compare wallet types and read How CoinReckon builds its profiles. You can also Browse crypto service profiles rather than treating this profile as a comparison score.

Incident-reading checklist

• Name the affected product, such as MetaMask Staking.
• Separate redirected rewards from wallet balances.
• Separate an attributed researcher estimate from a company statement 131415.

Frequently asked questions

Does using MetaMask mean I can use every feature in the US?

No. Core-wallet access is separate from the US restriction on Hyperliquid perpetuals and the restriction on Ondo tokenized stocks, ETFs and commodities 710. Eligibility has to be checked at the product layer involved.

Does the SEC dismissal mean MetaMask has a US license?

No. The SEC action filed on June 28, 2024 was dismissed with prejudice on March 27, 2025, but that disposition is not a license entry 1819. The snapshot's empty license field describes the dataset and does not prove the absence of any license.

Was the September 2026 incident a hack of everyone's wallet?

No. The September 2026 event involved staking infrastructure and validator operations rather than a general compromise of every user's wallet 131415. Kaden's approximately 0.36 ETH estimate concerned redirected rewards from 18 of 19 affected validators, while the company-attributed statement said user wallets were not threatened.

Compare wallet types and read how CoinReckon builds its profiles: Compare wallet types and How CoinReckon builds its profiles. If a source needs correction, Send an editorial correction.

Sources

• [1] Crunchbase, MetaMask company profile
• [2] MetaMask, 10th-anniversary announcement, published July 14, 2026; checked October 20, 2026.
• [4] Tracxn, MetaMask company profile
• [6] MetaMask, US card launch announcement, published February 26, 2026.
• [7] DataWallet, supported and restricted countries
• [8] MetaMask, card page
• [9] Cointelegraph via TradingView, US card launch, published February 26, 2026.
• [10] MetaMask, Ondo Global Markets announcement
• [13] CryptoTicker, staking incident and validator exits, published October 1, 2026.
• [14] Bitcoin Foundation, staking incident coverage
• [15] Aviatrix Threat Research Center, infrastructure incident analysis
• [18] SEC, complaint announcement 2024-79, published June 28, 2024; checked September 26, 2026.
• [19] SEC, dismissal announcement LR-26277, published March 27, 2025; checked September 26, 2026.

Financial information, not individualized investment or legal advice. This documentary profile reflects the source snapshot as of October 20, 2026, with SEC source checks retained at September 26, 2026. It does not promise safety, loss prevention, recovery, returns or regulatory approval.