May 12, 2025
11 11 11 AM
Latest Post
Ethereum’s Next Upgrade ‘Fusaka’ Could Cut Layer-2 and Validator Costs XRP, BTC Among Major Tokens Flashing Signs of Bulls Returning to Crypto DeFi Development Soars 20% as Solana Holdings Top $100M With Latest Purchase Malaysia Power Theft by Illegal Crypto Miners Rose 300% Since 2018 CoinDesk 20 Performance Update: Uniswap (UNI) Surges 12.7% Over Weekend BNB Surges Nearly 5% With Strong Volume Support Suggesting Institutional Accumulation David Bailey’s Nakamoto Holdings Going Public Via Merger With KindlyMD; Shares Soar 650% Trump Family Backed American Bitcoin To Go Public via Merger With Gryphon Digital Strategy Makes $1.34B Bitcoin Buy, Adding Another 13,390 BTC Bitcoin’s Bull Run Against Gold Could Accelerate as U.S.-China Trade Tensions Ease: Chart Analysis

Ethereum Staking Giant Lido Loses Just 1.4 ETH in Hacking Attempt

Lido, Ethereum’s largest liquid staking protocol, avoided a major security incident after one of its nine oracle keys was compromised in what appears to be a low-impact but serious breach involving validator operator Chorus One.

Lido secures over 25% of all ETH staked on Ethereum, making it one of the most systemically important protocols in the Ethereum ecosystem.

The compromised key was tied to a hot wallet used for oracle reporting, leading to the theft of just 1.46 ETH ($4,200) in gas fees. No user funds were affected, and no broader compromise was detected, per X posts from both Lido and Chorus One

Lido’s oracle system is a blockchain-based tool that supplies Ethereum consensus data to Lido’s smart contracts using a 5-of-9 quorum mechanism. This means that even if one or two keys are compromised, the system can function securely.

Contributors first detected the suspicious activity early Sunday after a low-balance alert triggered a closer look at the address. It revealed unauthorized access to an oracle private key used by Chorus One that was originally created in 2021 and not secured to the same standards as newer keys, the firm said in an X post.

In response, Lido has launched an emergency DAO vote to rotate the compromised oracle key across three contracts: the Accounting Oracle, the Validators Exit Bus Oracle, and the CS Fee Oracle. The new key has been generated using better security controls to avoid any repeat.

The hack occurred just as several other oracle operators were experiencing unrelated node issues, including a minor Prysm bug introduced by Ethereum’s recent Pectra upgrade, briefly delaying oracle reports on May 10.

The compromised address (0x140B) is being replaced by a new secure address (0x285f), with the on-chain vote already approved and in its 48-hour objection period as of Asian morning hours Monday.

This post was originally published on this site