MetaMask infrastructure incident prompts Lido operator exits
The Ledger · · Ketju Research
Developing. Some claims here are not yet confirmed; they are listed apart from the confirmed facts. A new version replaces this one when the primary evidence changes.
Affects: Lido (protocol)
What happened
An operator infrastructure incident prompted precautionary exits of MetaMask-operated Lido validators.
What changed
Affected stake enters an exit, withdrawal, and re-entry cycle with possible missed rewards and downtime penalties.
What did not change
The notices do not establish compromised withdrawal keys or a core-protocol exploit.
Confirmed
- Lido confirms that affected validators began exiting.
- MetaMask says it does not manage clients' staking withdrawal keys.
- An October 5 Lido reply proposes zero deposit targets in both curated modules; execution is not established.
Still open
- Attack scope, realised penalties, and completed remediation.
- Actual completion dates and approval of the proposed deposit limits.
- The estimated 45-day operator cycle does not establish a stETH withdrawal queue exceeding 30 days.
What it means for an advisor
- Review operator concentration, reward impairment, and exit assumptions in the Lido memo.
- Track remediation and deposit-limit execution before concluding recovery.
Sources
- [Security Disclosure] MetaMask Staking Precautionary Out of Order Exits · Lido protocol contributors / Lido governance ·
- User update · MetaMask ·
Version 1, published . We check this event again on . Educational research, not investment advice.