MetaMask's hack netted $967. Lido exited validators anyway.

A security incident that diverted less than $1,000 in block rewards triggered the mass exit of thousands of Ethereum validators. The gap between those two numbers is the entire story.

Why Did MetaMask Exit Validators Over a $967 Hack?

MetaMask exited validators because compromised signing keys create slashing risk, not because the attacker stole meaningful funds. On September 30, 2026, MetaMask disclosed an active security incident affecting part of its infrastructure in a statement posted to X at 23:35 UTC, and simultaneously began a precautionary mass exit of the Ethereum validators it operates inside Lido, the largest liquid staking protocol on Ethereum . The actual theft was roughly 0.36 ETH — about $967 — while the validator set potentially at risk holds hundreds of thousands of ETH .

Quick Answer: MetaMask exited its Lido validators after a September 30, 2026 infrastructure compromise diverted only ~0.36 ETH (~$967) in block tips. The exit was precautionary: compromised signing keys cannot withdraw stake but could theoretically trigger slashing, which destroys part of each validator's 32 ETH deposit.

The mechanics explain why the direct loss was so small. Independent Ethereum security researcher Kaden found that of 19 MetaMask validators that won block rewards during the attack window, 18 had their payments routed to an address funded through the Tornado Cash mixer (0x98B9…24A3) rather than the correct fee recipient, over roughly four and a half hours on September 30 . Changing a validator's fee recipient reroutes block tips without touching its 32 ETH stake — a configuration change, not a withdrawal. Neither MetaMask nor Lido has confirmed Kaden's figures.

The tail risk is what mobilized the response. Signing keys cannot move staked ETH, but they can in principle be used to make a validator commit a slashable offense, which destroys part of the stake and forcibly ejects the validator from the network.

The attacker "likely never had the ability" to withdraw staked ETH, but depending on how signing permissions were obtained, affected validators could theoretically be maliciously triggered for slashing. — Kaden, independent Ethereum security researcher (source: Decrypt, 2026-10)

MetaMask's own wording stayed narrow: it was "responding to a security incident affecting part of our infrastructure," had "identified no immediate threat to MetaMask wallets," and was "proactively exiting affected validators within our non-custodial staking operations" . The company stressed that its staking operation is non-custodial and that it does not manage withdrawal keys on behalf of clients — the operator signs for validators but cannot move the underlying stake .

Lido's governance forum post spelled out the cost. The protocol confirmed MetaMask Staking had "taken precautionary steps to protect client assets" following "an investigation into an infrastructure compromise," and that the exits "will likely incur foregone rewards as well as possible downtime penalties should validators be taken offline" . That tradeoff was accepted deliberately: a known, bounded loss of staking income in exchange for removing the possibility of network-level slashing penalties across a large validator fleet. No slashing has been reported by either party.

Timeline: From Disclosure to Full Exit

The disclosure-to-exit sequence ran on a compressed clock: MetaMask posted its first public statement on X at 23:35 UTC on September 30, 2026, and Lido published a governance-forum disclosure the same night, with the final validator exits scheduled to complete by the end of October 7, 2026 . That is roughly a week from first notice to a fully drained validator set — fast by operational standards, but only the first leg of a round trip that Lido estimates may take up to 45 days.

The diverted-rewards window itself was short. Independent Ethereum security researcher Kaden traced block-reward payments over roughly four and a half hours on September 30 and found that 18 of 19 MetaMask validators that won blocks during that period had their fee recipient pointed at an address funded through the Tornado Cash mixer (0x98B9…24A3), for a diverted total near 0.36 ETH . Those figures are Kaden's on-chain estimates and have not been confirmed by MetaMask or Lido .

The distinction Lido drew in its October 7 language is the one most easily misread. "Relevant validators have begun the exit process, with the final validators expected to be exited (but not fully withdrawn) by the end of October 7th, 2026," the forum post states . Exiting removes a validator from active duty; withdrawal moves its 32 ETH balance back out; re-entry puts that ETH to work again under a different operator or a rebuilt one. Lido put the complete cycle at "approximately up to 45 days due to the extended entry queue" . That figure describes capital flowing back into staking productivity, not a lock on stETH — a point at least one outlet has emphasized explicitly to counter the misreading .

MetaMask's own statement added that it is working with external partners and security advisors on remediation, that a full investigation is underway, and that further updates would follow . As of the time of writing, no interim technical post-mortem has been published by either party, and the exit schedule — not the investigation — is the only part of this timeline with a firm public date attached.

How Big Was the Hack, Really? The Scale Dispute

The size of MetaMask's affected validator set is genuinely contested, and the two circulating figures differ by roughly 2x. Independent Ethereum security researcher Kaden's on-chain estimate puts the operator at about 17,000 validators holding roughly 523,000 ETH — approximately $1.4 billion at prevailing prices . Lido's own node operator registry has been cited at a materially lower 7,204 MetaMask validators and an estimated 230,000 ETH . Neither number has been confirmed by MetaMask or by Lido, and traders sizing this event should treat the range, not either endpoint, as the working figure.

The gap exists because neither official document quantified anything. MetaMask's public statement described "proactively exiting affected validators within our non-custodial staking operations" without a count, and Lido's security disclosure specified an exit deadline but no validator total and no ETH amount . At least one outlet covering the incident explicitly flagged the higher, widely shared estimate as unconfirmed . Everything in the larger figure traces back to independent chain analysis rather than to a disclosure from either party.

The distinction matters for reading the queue data rather than for assessing solvency. On Kaden's higher estimate, MetaMask's exits alone would account for roughly two-thirds of Ethereum's exit queue — which would make this incident the dominant driver of network-wide exit congestion. On the registry-derived figure, it is a large contributor among several. Either way, the amounts describe stake being rotated out of one operator's infrastructure, not stake at risk of disappearing: the exits are precautionary and the underlying ETH remains under Lido's withdrawal credentials.

Kaden also flagged loose ends that complicate any clean tally. Three validators suspected of being affected had not exited at the time of his review, and roughly 821 potentially affected validators remained in operation for reasons that were not publicly explained . Those residuals could reflect false positives in the detection method, validators judged unaffected on review, or simply a staggered exit schedule — but until MetaMask publishes a technical breakdown, there is no way to distinguish between those explanations from the outside.

"[The attacker] likely never had the ability [to withdraw staked ETH]," said Kaden, independent Ethereum security researcher, while cautioning that depending on how signing permissions were obtained, affected validators could theoretically be maliciously triggered for slashing (source: Decrypt, 2026-10).

For anyone building a position view from these numbers, the practical rule is to cite the range with its provenance attached and to anchor exposure estimates to the lower, registry-derived figure until an operator-confirmed count appears. A second useful check is incident reporting on the compromise itself, which likewise carries no official validator count — a reminder that the 2x spread reflects a disclosure gap, not a data error.

What This Means for stETH Holders

For stETH holders, the operational answer from Lido is explicit: "No action is required from stETH holders" . The MetaMask Staking exits affect how a slice of the protocol's validator set earns, not whether stETH can be held, moved, or sold. Lido's disclosure cited two buffers: a diverse node operator set, so no single operator's withdrawal interrupts the protocol's staking function, and an ad hoc reserve fund of more than 6,750 stETH available to absorb operational disruption . The cost that does land on holders is income, not principal: Lido said the exits "will likely incur foregone rewards as well as possible downtime penalties should validators be taken offline," with downtime accepted deliberately to reduce the risk of larger network penalties .

The most common misreading of this event is the 45-day figure. Lido's "approximately up to 45 days due to the extended entry queue" describes the full round trip of exited ETH through exit, withdrawal, and re-entry into active validator duty — a validator lifecycle timeline driven by Ethereum's entry queue . It is not a 45-day lockup on stETH, a point reporting on the validator cycle made explicitly . stETH is a liquid staking token traded on secondary markets; it remained transferable and tradeable throughout the exit window, independent of where any individual validator sat in the queue.

The second question holders reasonably ask is about contagion through the venues where stETH is used as collateral. Downstream monitoring during the incident found no impact on Aave's stETH collateral markets and no direct stETH exposure in Ethena's USDe backing . That matters because the DeFi transmission path for a staking incident usually runs through liquidation mechanics rather than the staking protocol itself — a sharp stETH discount can cascade through leveraged collateral positions. No such dislocation was reported.

Practically, the exposure checklist for a holder is short:

• Principal risk: none reported. Signing keys cannot move the underlying 32 ETH per validator, and MetaMask does not manage withdrawal keys on behalf of clients .
• Slashing risk: theoretical, and the reason for the exit. No slashing has been reported by either MetaMask or Lido .
• Yield risk: real but bounded — foregone rewards and possible downtime penalties on the affected validator subset, diluted across the whole stETH supply rather than borne by specific holders .
• Liquidity risk: stETH stayed liquid; the queue delay applies to redeployment of exited ETH, not to secondary-market trading .

The honest framing for a retail holder is that this was a yield event with a tail-risk justification, not a solvency event. The signal worth tracking is not stETH's price but Lido's reward-rate reporting over the coming weeks, since that is where the foregone-rewards cost eventually surfaces.

The Ethereum Exit Queue: How Clogged Did It Get?

Ethereum's exit queue went from effectively empty to 773,447 ETH waiting to leave in roughly 24 hours — the largest exit backlog since December 2025 . That backlog translated into an exit wait of about 13 days, while roughly 1.57 million ETH sat on the other side of the ledger queued to activate at about a 27-day delay . The queue is not a congestion bug; it is the protocol doing exactly what it was designed to do.

The mechanism is a hard rate limit on how fast the validator set can change composition. Ethereum currently processes a maximum of 256 ETH per epoch in each direction, and with epochs lasting 6.4 minutes and 225 epochs per day, that caps daily throughput near 57,600 ETH . Every validator that wants out — whether it is leaving for yield reasons or, as here, for security reasons — joins the same single-file line. A large operator cannot buy priority.

The before-and-after snapshots make the shift concrete. On September 30, before the disclosure propagated, the exit queue was near zero, with 205,011 ETH recorded as exiting against an entry queue of 1,603,958 ETH that implied roughly 27 days and 20 hours to activate, across 884,366 active validators . By Wednesday, October 1, Validator Queue data showed the exit side had refilled to 773,447 ETH .

Sources: Validator Queue, Bitcoin.com News, DL News.

Sizing MetaMask's share of that backlog depends on which validator estimate you accept, and the two available figures diverge sharply. On researcher Kaden's on-chain estimate of roughly 523,000 ETH across about 17,000 validators, MetaMask's exits alone would account for close to two-thirds of the 773,447 ETH exit queue . On the lower figure drawn from Lido's operator registry — 7,204 validators and an estimated 230,000 ETH — the share falls to roughly 30%, which is still the single largest contributor but no longer the dominant one . Neither MetaMask's statement nor Lido's forum disclosure specified a count, so the ratio stays an inference rather than a confirmed figure .

What matters practically is the asymmetry between the two queues. Exiting takes roughly 13 days; re-entering takes roughly 27. That gap is why Lido put the full round trip of exited ETH at approximately up to 45 days, and why the cost of this event is measured in idle capital rather than destroyed capital . For anyone planning their own unstaking over the next month, the queue is now the binding constraint, and it is a shared one.

The 2025 Kiln Precedent: What Foregone Rewards Could Look Like

Kiln's September 2025 incident is the closest available template for estimating MetaMask's eventual foregone-reward bill. After a leaked GitHub token exposed Kiln's staking infrastructure, the provider exited its entire Lido validator fleet: roughly 5,726 validators, about 13.5 days off duty, and 207.3 ETH in missed rewards . The structure of that loss — income, not principal — is the same structure now in play, which makes the per-validator arithmetic portable even though the headcount is not.

Run that arithmetic and the asymmetry becomes concrete. Kiln's 207.3 ETH spread across 5,726 validators works out to roughly 0.036 ETH of foregone rewards per validator over its idle window. Apply that rate to Lido's registry figure of 7,204 MetaMask validators and the implied bill lands near 260 ETH; apply it to the contested on-chain estimate of about 17,000 validators and it approaches 610 ETH . Both ranges sit orders of magnitude above the 0.36 ETH — under $1,000 — the attacker actually diverted through the rerouted fee recipient . These are derived estimates, not disclosed figures: neither MetaMask nor Lido has published a reward-loss number, and Lido's own language stops at saying the exits "will likely incur foregone rewards as well as possible downtime penalties" .

The second half of the Kiln precedent is the part that outlasted the incident itself. That single fleet exit clogged Ethereum's exit queue for four months, peaking near 2.67 million ETH in mid-September 2025, and did not fully clear until January 2026 . Kiln's own operators were off duty for 13.5 days, but the congestion they created taxed every unrelated staker who wanted out during that window. The current backlog of 773,447 ETH is well below the 2025 peak, so the queue arithmetic is less punishing this time — but the mechanism is identical, and it compounds the direct reward loss rather than replacing it .

Three caveats keep the comparison honest. First, Kiln's validator count is firm while MetaMask's is disputed by a factor of more than two, so any extrapolation inherits that uncertainty. Second, Kiln's 13.5-day idle period reflected 2025 queue conditions; MetaMask's exits are scheduled to finish by October 7, 2026, with re-entry governed by a roughly 27-day activation queue, which can lengthen the income gap beyond Kiln's . Third, Lido's ad hoc reserve fund of more than 6,750 stETH exists precisely to absorb operational shortfalls of this kind, which is why the practical read-through for stETH holders is a marginal yield drag rather than a balance-sheet event . The useful lesson from Kiln is not a dollar figure. It is that in liquid staking, an infrastructure compromise worth less than a thousand dollars can generate a remediation cost two to three orders of magnitude larger, and that the cost lands mostly on timing and throughput.

What's Still Unknown

The disclosure gaps in this incident are wide enough to change how the event should be interpreted, and neither MetaMask nor Lido has closed them. As of October 2, 2026, neither party has named which system inside MetaMask's staking infrastructure was compromised, how the intruder got in, or when the breach was first detected . MetaMask's statement described only "a security incident affecting part of our infrastructure" and said a full investigation is underway with external partners and security advisors . The attacker's identity is unknown, and the only on-chain handle is the destination wallet 0x98B9…24A3, funded through the Tornado Cash mixer .

A second open question is the blast radius of the fee-recipient change. Researchers confirmed rerouted payments on 18 of the 19 MetaMask validators that proposed blocks during the roughly four-and-a-half-hour window on September 30 — but that sample only covers validators that happened to win a proposal slot. Whether the attacker held the ability to rewrite fee recipients across the entire operated set, or only a subset, has not been established . Loose ends persist in the on-chain picture as well: three suspected-affected validators had not exited, and roughly 821 potentially affected validators remained in operation for reasons not publicly explained .

What is established is the custody boundary. MetaMask Staking is non-custodial: the operator signs for validators but does not manage withdrawal keys on behalf of clients, so the underlying stake cannot be moved by the operator — or by anyone who compromises operator signing infrastructure . That architectural fact is why the researcher who surfaced the incident framed the risk as slashing rather than theft.

"Likely never had the ability" to withdraw staked ETH — though depending on how signing permissions were obtained, affected validators could theoretically be maliciously triggered for slashing, says Kaden, independent Ethereum security researcher (source: Decrypt, 2026-10).

On that specific tail risk, the record so far is clean: no slashing event has been reported by MetaMask, by Lido, or in the Lido governance disclosure, which described the exits purely as precautionary and flagged only foregone rewards and possible downtime penalties . Readers should also note that Kaden's scale estimates — roughly 17,000 validators and about 523,000 ETH — remain unconfirmed by either organization, with Lido's operator registry cited at 7,204 validators and an estimated 230,000 ETH . Until MetaMask publishes a post-incident report, the honest summary is narrow: a confirmed infrastructure compromise, a confirmed diversion of roughly 0.36 ETH, a confirmed precautionary exit, and an unconfirmed everything else.

Outlook: Queue Pressure, Rebrand Context, and What to Watch

The practical outlook rests on three trackable variables: how fast Ethereum's exit queue drains, whether MetaMask publishes official validator counts, and how much re-entry pressure the returning ETH adds to the activation queue. None of them require a stETH holder to act. All of them determine whether this incident stays a two-week income interruption or becomes a months-long queue distortion like the one Kiln produced in late 2025. The single most useful instrument is the public queue data at validatorqueue.com, which showed 773,447 ETH waiting to exit on October 1, 2026 .

Naming context helps when reading future statements. MetaMask Staking is the rebranded Consensys Staking . In September 2026, Consensys Software Inc. said it would operate as MetaMask while separating its protocols and institutional infrastructure businesses into a newly formed Consensys entity, a split expected to complete by the end of 2026 . Disclosures over the coming months may therefore arrive under either brand, and the institutional staking business sits on the side of that line most exposed to operator-level scrutiny.

Three things to watch, in order of how much they change the picture:

• Queue clearance pattern. Kiln's 2025 exit kept the backlog elevated for roughly four months, peaking near 2.67 million ETH in mid-September 2025 and clearing only in January 2026 . If the confirmed MetaMask scale lands closer to Lido's registry figure of 7,204 validators than the circulated 17,000 estimate, clearance should run considerably faster than that.
• Official numbers. Neither MetaMask's statement nor Lido's disclosure specified a validator count or ETH amount . A post-incident report settling the dispute also settles the foregone-rewards arithmetic.
• Re-entry pressure. Exited ETH returns gradually, a round trip Lido put at approximately up to 45 days because of the extended entry queue . That re-entry stacks onto an activation queue already near 1.57 million ETH at roughly a 27-day delay — a second-order effect on anyone timing new stake deployment, independent of the compromise itself.

The concrete takeaway for a retail position: treat this as a yield event, not a solvency event. Final exits were scheduled to complete by the end of October 7, 2026 , Lido stated that no action is required from stETH holders and pointed to a reserve fund of more than 6,750 stETH , and no slashing has been reported by either party . If you are deploying fresh ETH into staking this month, assume activation waits measured in weeks rather than days and size accordingly; if you already hold stETH, the rational response is to check the queue data monthly and otherwise do nothing.

Frequently asked questions

How much was actually stolen in the MetaMask hack?

Roughly 0.36 ETH — under $1,000 at prevailing prices — was diverted in block-reward tips, not staked principal . Independent Ethereum security researcher Kaden found that of 19 MetaMask validators that won block rewards during the window, 18 had payments routed to an address funded through the Tornado Cash mixer (0x98B9…24A3) rather than the correct fee recipient, over a span of about four and a half hours on September 30, 2026 . Changing a validator's fee recipient reroutes tips without touching its 32 ETH deposit, which is why the direct loss was so small. Neither MetaMask nor Lido has confirmed Kaden's figures.

Why did MetaMask exit validators over such a small amount?

Because the risk was slashing, not theft. Signing keys cannot withdraw a validator's stake, but depending on how the attacker obtained signing permissions, they could in principle be used to make a validator commit a slashable offense — which destroys part of the 32 ETH stake and forcibly ejects the validator from the network. Kaden said the attacker "likely never had the ability" to withdraw staked ETH but warned that affected validators could theoretically be triggered for slashing . That tail risk justified a precautionary exit of a very large validator set, even though it costs foregone rewards and possible downtime penalties . No slashing has been reported by either party.

Do stETH holders need to do anything?

No. Lido's disclosure states plainly that "No action is required from stETH holders," and the protocol pointed to its diverse node operator set plus an ad hoc reserve fund of more than 6,750 stETH as buffers against operational disruption . Downstream venues were monitored without incident: reporting noted no impact on Aave's stETH collateral markets and no direct stETH exposure in Ethena's USDe backing . The widely quoted round trip of approximately up to 45 days refers to the full validator exit-withdrawal-re-entry cycle driven by Ethereum's extended entry queue — it is not a lockup on stETH .

How many MetaMask validators were affected?

The figure is disputed, and no official count exists. Kaden's on-chain estimate, the most widely circulated, is roughly 17,000 MetaMask-operated validators holding about 523,000 ETH, worth around $1.4 billion . Lido's own operator registry has been cited as showing 7,204 MetaMask validators and an estimated 230,000 ETH, and at least one outlet explicitly flagged the higher numbers as unconfirmed . Neither MetaMask's statement nor Lido's forum disclosure specified any validator count or ETH amount. Kaden also flagged loose ends: three suspected-affected validators had not exited, and roughly 821 potentially affected validators remained in operation for reasons that are not yet clear.

Is this similar to any past incident?

Yes — the closest precedent is Kiln's September 2025 exit from Lido. After its staking infrastructure was exploited via a leaked GitHub token, Kiln exited roughly 5,726 Lido validators, which spent around 13.5 days off duty and gave up 207.3 ETH in missed rewards . That episode congested Ethereum's exit queue for four months, peaking near 2.67 million ETH in mid-September 2025 and only clearing in January 2026 . The Kiln case is the best available template for estimating what MetaMask's foregone rewards may ultimately total, though the two fleets differ in size and the exit windows differ in market conditions.

Enjoyed this article? Subscribe to get new stories by email whenever they're published.

Subscribe