Euler exploit extracted assets valued near $197 million

Euler Finance’s Ethereum lending protocol was drained on March 13, 2023 after an attacker exploited a missing account-health check in its `donateToReserves()` path. CertiK’s event-day reconstruction estimated the loss at approximately $197 million across five lending pools, making the incident one of decentralized finance’s most consequential smart-contract failures to that date.

Ethereum transaction records place the first successful extraction at 08:50:59 UTC. Euler’s later first-party chronology says the principal exploiter began additional transactions at 08:56:35 UTC and continued for roughly 15 minutes. Those records establish when the transactions executed and which contracts moved tokens. They do not independently convert the token balances into a single realized-dollar loss.

How the position was manufactured

Euler represented deposits with eTokens and debts with dTokens. Its `mint()` function let a user recursively create deposit and debt exposure in the same asset, while liquidation rules allowed an undercollateralized position to be closed at a bonus.

In the DAI example reconstructed by CertiK, the attacker borrowed 30 million DAI from Aave in a flash loan, deposited 20 million DAI into Euler, and used `mint()` to build a much larger leveraged position. A flash loan must be repaid within the same Ethereum transaction or the entire transaction reverts; it supplied scale, but it was not itself the software defect.

The critical step was `donateToReserves()`. The function reduced the attacker contract’s eToken collateral without performing the liquidity check applied to ordinary eToken transfers. The attacker deliberately pushed its own account into an unhealthy state, liquidated that position through a separate account, collected the liquidation discount and withdrew assets from Euler. Repeating the sequence against several pools turned one missing solvency check into a protocol-wide shortfall.

Euler later said the vulnerable function had been introduced while addressing an earlier “first depositor” issue. That explanation is first-party retrospective context, not information established by the March 13 transaction data alone.

What the $197 million estimate contained

CertiK’s March 13 accounting listed 8,877,507 DAI, 8,080 wrapped ether, 846.4 wrapped bitcoin, 73,821 staked ether and 34,224,863 USDC removed from Euler pools. After swaps, the firm tracked 96,732.66 ETH and approximately 43 million DAI under exploiter control.

Those quantities are an attributed security-firm reconstruction of the March 13 transaction set, not an audited claims register. The approximately $197 million figure applies contemporaneous token valuations to different assets and therefore changes with pricing inputs. It should not be read as dollars received, a later recovery value or a precise measure of every depositor’s eventual loss.

The incident mattered beyond the headline total because Euler was permissionless infrastructure used by other decentralized-finance applications. Deposits, treasuries and structured products built on top of a lending market could inherit its impairment even if their own contracts functioned as designed. March 13 exposed composability’s reverse side: integrations that spread liquidity and utility can also transmit a contract failure across protocols.

What was known on March 13

By the end of March 13, the defensible record was that multiple Ethereum transactions had exploited Euler’s deployed code, the vulnerable account-health path had been identified, and roughly $197 million was the leading forensic estimate. Attribution to a specific real-world person, the final recoverable amount and the method for restoring users remained unknown.

Later context

On April 4, 2023, the Euler Foundation said negotiations had produced the return of all recoverable funds. That outcome materially changed the loss picture, but it was not knowable on March 13 and does not diminish the event-day failure.