The Circuitry
THE CIRCUITRYYour one-stop source for all tech news
HOMETODAYNEWSFEEDEVENTS
BOOKMARKS
RSS
© 2026 The Circuitry
About UsSourcesContactCorrectionsPrivacy
  • Today
  • Feed
  • Events
  • Saved
Scroll for more
Verification
VERIFIEDConfidence: HIGH
Source identified
Claims cross-referenced
No discrepancies found
Fact-check summary

Multiple outlets including CoinDesk, CryptoBriefing, Blockhead and Lido's governance forum confirm MetaMask's precautionary validator exits from Lido after an infrastructure incident on Sept 30.

Sourcing
1source

via Decrypt

Decrypt · track record
36Stories
100%Verified
530d
All sources →
Markets
ETH···

Live quote · not investment advice

From The CircuitryWhy The Circuitry

Verified tech news, cross-checked.

Every story is checked against independent sources before it posts — no rumors dressed up as fact.

How we verify →
Home/Markets/MetaMask Withdraws Validators from Lido Following Infrastructure Issue
VERIFIEDBy Xavier Rivera·Thursday, October 1, 2026 at 5:48 AM EDT·1.5 min read

MetaMask Withdraws Validators from Lido Following Infrastructure Issue

MetaMask has begun removing Ethereum validators from Lido after a security incident struck part of its infrastructure. The action is precautionary, with no immediate wallet threat identified and ETH returns possibly taking up to 45 days.

Source:Decrypt
Post
MetaMask Withdraws Validators from Lido Following Infrastructure Issue
From The CircuitryWhy The Circuitry

Verified tech news, cross-checked.

Every story is checked against independent sources before it posts — no rumors dressed up as fact.

How we verify →
TL;DRAI · 60 sec read

MetaMask removes its Ethereum validators from Lido after a security incident hit its infrastructure. The firm reports no direct risk to wallet users. Exits began September 30 and should finish by October 7. Return of ETH to the protocol could require as long as 45 days. Lido calls the moves protective measures.

MetaMask has initiated removal of its Ethereum validators from the Lido staking protocol after an ongoing security incident hit part of its infrastructure.

MetaMask sees no direct risk to its wallet users at present. The company indicated it found no immediate danger to MetaMask wallets and is handling the matter with help from partners and advisors. Affected validators in the non-custodial staking setup are being removed.
MetaMask sees no direct risk to its wallet users at present.

Validator exits commenced September 30 and should conclude by October 7. The process for the impacted validators is underway, with completion anticipated by October 7. Lido characterized these actions as protective measures following the discovery of a compromise in infrastructure.
POST FROM @MetaMask· official announcement tweet from MetaMask regarding the security incident and validator exits
https://x.com/MetaMask/status/2105442300335620460

Return of ETH to the protocol could require as long as 45 days. According to Lido, the stake will come back over time through the exit, withdrawal, and re-entry process. Ethereum's entry queue may extend this to 45 days.
From The CircuitryThe Feed — live briefs across tech, all day.See what’s happening →

The non-custodial nature of the staking is emphasized by both parties. Withdrawal keys remain with clients, not MetaMask. Lido confirmed no steps needed from stETH holders and highlighted its operator diversity plus a reserve exceeding 6,750 stETH to mitigate issues.
Withdrawal keys remain with clients, not MetaMask.

Analysis indicates minimal losses from the incident to date. Researcher Kaden noted that 19 MetaMask validators received block rewards, with 18 directed to a Tornado Cash-linked address totaling about 0.36 ETH. The same review shows roughly 17,000 validators with 523,000 ETH exiting preemptively.
From The CircuitryWhy The Circuitry

Verified tech news, cross-checked.

Every story is checked against independent sources before it posts — no rumors dressed up as fact.

How we verify →
Aave founder Stani Kulechov stated the lending protocol is monitoring the situation with Lido and reported no effects on Aave markets involving stETH.
Why this mattersAI · ~100 words

Tap a lens to see what this story means for you.

Morning Brief

Liked this? The Brief brings you the whole day in tech, verified, every morning.

Two minutes, free forever. What's in The Brief →

Reader-supported
DonateBuy me a coffee →Follow@thecircuitry_ →Follow@thecircuitry.to →
HELP US IMPROVE
From The Circuitry

See what’s happening right now

The Feed runs all day — short, verified briefs the moment they break.

Open the Feed →
From The Circuitry

Follow @thecircuitry_

Every story we publish, as it happens. No noise between.

Follow on X ↗On Bluesky ↗

Reader-supported

The Circuitry is a passion project I've always wanted to build, and I love the work behind it.

Running it costs real money. APIs, hosting, time. To keep improving the site and growing this into something useful for everyone, those costs have to be covered.

Any contribution is appreciated. If not, no pressure. Thanks for reading.

Buy me a coffee
metamasklidoethereumstakingsecurity
More fromDecrypt
  • OKX Secures Backing at $25 Billion Pre-Money Valuation

    Markets · 7d
  • OKXICE Files for 24/7 Tokenized Stock Trading Under SEC Exemption

    Markets · 9d
  • This week in crypto: stablecoin payments partnership, BTC rebound, and Strategy buy

    Markets · 15d
More inMarkets
  • Payward Moves to Gain EU Bank License via Saldo Purchase

    Markets · 7h
  • Standard Chartered Debuts Bitcoin Trading for UAE Wealth Clients

    Markets · 9h
  • UK court rules Chinese law governs claims to 61,000 seized bitcoin

    Markets · 1d
SupportThe Work

The Circuitry is reader-supported. If you find the daily brief useful, you can buy me a coffee to keep it going.

Buy a coffee →
From The CircuitryWhy The Circuitry

Verified tech news, cross-checked.

Every story is checked against independent sources before it posts — no rumors dressed up as fact.

How we verify →

MORE IN THIS BEAT

All Markets →
  • Tech·Oct 14

    Two high-severity flaws affect TeamPlus Messenger 16.8.0 through 17.0.6

    TWCERT/CC disclosed two code injection flaws in TeamPlus Messenger 16.8.0 through 17.0.6, each rated 8.8 under CVSS 3.1. Attackers who trick users into opening crafted links or content can run code after a Windows warning; version 17.0.7 fixes them.

  • Tech·Oct 14

    CISA adds Palo Alto PAN-OS CVE-2026-0322 to KEV catalog

    CISA added PAN-OS flaw CVE-2026-0322 to its Known Exploited Vulnerabilities catalog on October 14, giving federal agencies until October 17 to act. The management-interface bug lets authenticated attackers run code as root; Palo Alto reports very limited exploitation.

  • Tech·Oct 14

    Critical command injection flaw affects D-Link DIR-868L firmware 2.01b05

    CVE-2026-110536 is an unauthenticated OS command injection flaw in the HNAP handler of D-Link DIR-868L firmware 2.01b05, rated 10.0 by VulDB under CVSS 3.1 and CVSS 4.0. Exploit code is public, and D-Link no longer patches the end-of-life router.

  • Tech·Oct 14

    Adobe fixes high-severity flaws in Content Credentials SDK

    Adobe's APSB26-163 bulletin fixes more than 30 vulnerabilities in its Content Credentials Rust SDK, C2PA Tool and JS SDK. Adobe rates the worst, a server-side request forgery flaw, 8.6 and most others 7.5, and says it knows of no exploits in the wild.

  • Tech·Oct 14

    Adobe patches 14 high-severity flaws in Substance 3D Stager

    Adobe's APSB26-170 bulletin patches 16 vulnerabilities in Substance 3D Stager 3.1.8 and earlier, including 14 rated 7.8 (High) that can lead to arbitrary code execution when a user opens a malicious file, plus two medium-severity issues.