MetaMask has begun exiting affected Ethereum validators after disclosing a Sept. 30 infrastructure security incident, with Lido expecting the final impacted validators to exit by Oct. 7.
Summary
- MetaMask is exiting affected Ethereum validators after identifying a security incident within its infrastructure systems.
- Lido expects the final affected MetaMask validators to exit by October 7, pending network conditions.
- MetaMask says its staking service remains non-custodial and does not control client withdrawal keys directly.
- Lido says stETH holders need no action while exited ETH gradually returns through protocol processes.
- Aave founder Stani Kulechov says its markets remain unaffected while teams monitor developments with Lido.
MetaMask said it was responding to an ongoing incident affecting part of its infrastructure and was working with external partners and security advisers on remediation. The company said it had identified “no immediate threat to MetaMask wallets,” while giving no technical details about the systems involved.
As a precaution, the company started exiting affected validators from its non-custodial staking operations. MetaMask said it does not hold withdrawal keys for client stake, meaning the validator operator does not control the keys used to withdraw the underlying funds.
Public disclosures available as of Oct. 1 do not identify the attack method, the number of validators affected, the amount of ETH involved or whether any data was accessed. MetaMask said it would continue monitoring the incident and provide more information as its investigation develops.
MetaMask says wallets face no immediate threat
MetaMask’s statement separates the affected infrastructure from its wallet product. While the company confirmed a security incident, it did not report a compromise of MetaMask wallets or disclose losses involving wallet users. Its wording was limited to saying no immediate wallet threat had been identified at the time of the update.
The affected operations involve MetaMask Staking, previously known as Consensys Staking. Earlier in September, Consensys Software Inc. announced plans to operate under the MetaMask name while separating its protocols and institutional infrastructure businesses into a newly formed Consensys company. Completion of that corporate separation is expected by the end of 2026.
MetaMask’s validator staking service is built around a non-custodial model. Its support documentation states that users retain control over their stake and rewards while the staking infrastructure operates the validator. For direct validator staking, ETH remains tied to Ethereum’s staking system until the user initiates an exit and withdrawal.
As crypto.news previously reported on MetaMask’s validator staking service, the product was launched using Consensys-operated validator infrastructure. MetaMask’s current incident notice does not say whether every part of its staking business is affected or identify the infrastructure component involved.
Lido expects validator exits to run through Oct. 7
Lido provided a more detailed operational update after MetaMask disclosed the incident. In a Sept. 30 security disclosure on its governance forum, a Lido representative said MetaMask Staking had taken precautionary action following an “infrastructure compromise.”
Validators operated by MetaMask Staking within the Lido protocol have begun exiting. Lido expects the final affected validators to complete the exit stage by the end of Oct. 7, though they will not necessarily be fully withdrawn by then.
Ethereum validator withdrawals involve several stages. Lido said ETH leaving MetaMask-operated validators would gradually return to the protocol as each validator passes through exit, withdrawal and eventual re-entry. The entire process could take up to approximately 45 days because of Ethereum’s extended validator entry queue.
Lido told stETH users that “No action is required from stETH holders.” The protocol said MetaMask’s exit process could lead to foregone staking rewards and possible downtime penalties if affected validators are taken offline before their exits finish.
Taking validators offline before the formal exit process finishes can reduce exposure to some validator risks, but inactive validators can incur Ethereum penalties. Lido attributed the possible downtime step to efforts to reduce risks related to potential network penalties and did not say the validators had been slashed.
Lido pointed to its distributed node operator structure and an ad hoc reserve fund holding more than 6,750 stETH as systems intended to absorb operational disruptions. The protocol currently reports more than 600 operators across its staking modules.
Lido’s validator infrastructure overhaul, the protocol introduced Curated Module v2 in July, adding support for higher effective validator balances and new mechanisms covering operator accountability and penalties.
Non-custodial staking keeps withdrawal keys with clients
MetaMask stressed the distinction between operating a validator and controlling the assets tied to it. Its staking operation signs validator duties and maintains validator infrastructure, while the company says it does not manage client withdrawal keys.
MetaMask’s own documentation describes validator staking as self-custodial. Users deposit ETH to Ethereum’s beacon deposit contract and maintain control over the withdrawal process, while MetaMask’s staking infrastructure handles node operation.
Lido uses a related separation of duties for node operators. Its technical documentation states that withdrawal credentials are set by the protocol, while operators generate validator signing keys used to perform validator duties. The withdrawal credentials determine where withdrawn ETH can move.
MetaMask did not say whether validator signing keys were accessed during the incident. It likewise did not disclose evidence of slashing, stolen client stake or unauthorized withdrawals. Lido’s forum post refers to potential downtime penalties and possible network penalties as risks connected with the precautionary response, not as confirmed losses.
Current information therefore remains limited to the infrastructure incident, the validator exit process and the companies’ stated safeguards. MetaMask said remediation was underway with outside security advisers, while Lido said a “full investigation is underway” and further updates would follow.
Aave says its markets remain operational during the probe
Aave founder Stani Kulechov said he was monitoring the MetaMask Staking incident and developments involving Lido after the validator exits became public.
Kulechov said Aave’s markets had not been affected and that the protocol’s functions were operating normally, according to his Oct. 1 update. No verified disruption to Aave markets tied to the MetaMask incident had been reported at the time of the statement.
The comment is relevant because stETH and other Ethereum staking assets are widely used across decentralized finance, including lending markets. Lido’s security disclosure did not instruct stETH holders to withdraw, exchange or move their tokens during MetaMask’s validator exit process.
No public MetaMask update reviewed on Oct. 1 gave a deadline for completion of the security investigation. The dated operational milestone comes from Lido, which expects the last affected MetaMask-operated validators to enter the exited state by the end of Oct. 7 before withdrawals and re-entry continue through the estimated 45-day cycle.
