MetaMask Exits Thousands of Ethereum Validators After Security Incident
BSCN reported the development in a post on X, citing security researcher Kaden, who estimated that roughly 17,000 validators holding about 523,000 ETH were sent toward the exit process. MetaMask has not confirmed those figures.
The incident was disclosed on Oct. 1, when MetaMask said it was actively investigating a security issue affecting part of its infrastructure. The company said it was proactively removing affected validators from its non-custodial staking operations as a precaution while teams worked on containment and verification.
MetaMask Says Customer Wallets Were Not Compromised
MetaMask has said its investigation found no indication of a compromise involving customer wallets or funds. The company has also emphasized that its staking operations are non-custodial and that it does not manage withdrawal keys for clients' staked assets.
The distinction is important because Ethereum validators have separate mechanisms for handling staked assets and validator-related payments. A compromised fee-recipient configuration can redirect block-production rewards without necessarily providing access to the underlying staked ETH.
Kaden estimated that approximately 0.36 ETH in validator tips was diverted during the incident. CoinDesk reported that the researcher identified 18 of 19 MetaMask-operated validators that had received block-production payments as sending those payments to an unexpected address. MetaMask has not publicly confirmed the 0.36 ETH figure.
Around 17,000 Validators Reportedly Sent to Exit
Kaden's estimate puts the number of validators being removed at around 17,000, with those validators holding roughly 523,000 ETH. BSCN cited the figures as part of its account of the incident, but MetaMask has not confirmed the size of the validator group.
Separate onchain analysis by Bitquery later counted 16,965 MetaMask-operated validators that had exited or entered the exit queue by early Oct. 1, holding 565,056 ETH. That analysis also found 0.36 ETH in diverted block tips and reported that no validators had been slashed.
The difference between the estimates underscores that the 17,000-validator and 523,000-ETH figures in BSCN's post should be treated as an external estimate rather than a figure confirmed by MetaMask.'
Lido Confirms MetaMask Validators Are Leaving
Lido separately confirmed that MetaMask Staking validators were being removed from its protocol. Lido said the affected validators had begun the exit process and that the final validators were expected to exit by Oct. 7, although the ETH would not necessarily have been fully withdrawn by that date.
Lido estimated that the full process of exiting, withdrawing and potentially re-entering staking could take up to approximately 45 days because of the Ethereum staking-entry queue. The protocol said no action was required from stETH holders.
MetaMask's investigation remains focused on the affected infrastructure, while the company has not publicly confirmed the scale of validator exits cited by Kaden or provided a detailed explanation of how the security incident occurred.
Writer: Ethan Collins
Crypto Journalist
Ethan Collins reports on developments across the cryptocurrency and blockchain sector. His work covers market movements, protocol updates, regulatory changes, and emerging trends in digital assets.
He focuses on presenting complex topics in a clear and accessible manner for a broad readership.
Check out other news and articles on Google News
Disclaimer:
The articles on Hokanews are here to keep you updated on the latest buzz in crypto, tech, and beyond—but they’re not financial advice. We’re sharing info, trends, and insights, not telling you to buy, sell, or invest. Always do your own homework before making any money moves.
Hokanews isn’t responsible for any losses, gains, or chaos that might happen if you act on what you read here. Investment decisions should come from your own research—and, ideally, guidance from a qualified financial advisor. Remember: crypto and tech move fast, info changes in a blink, and while we aim for accuracy, we can’t promise it’s 100% complete or up-to-date.