← Back to incidents

Ethereum DAO Smart Contract Vulnerability Exploited for $60 Million

Critical

The Ethereum DAO autonomous organization was hacked for $60 million in June 2016 due to a reentrancy vulnerability in its smart contract code. The incident led to a controversial hard fork of the Ethereum blockchain to recover the stolen funds.

Category
Agent Error
Industry
Finance
Status
Resolved
Date Occurred
Jun 17, 2016
Date Reported
Jun 17, 2016
Jurisdiction
International
AI Provider
Other/Unknown
Application Type
agent
Harm Type
financial
Estimated Cost
$60,000,000
People Affected
11,000
Human Review in Place
No
Litigation Filed
No
smart_contractsblockchaincryptocurrencyautonomous_systemsreentrancyethereumhard_forkdecentralized_finance

Full Description

The Ethereum DAO (Decentralized Autonomous Organization) was launched in April 2016 as an ambitious experiment in decentralized governance and investment. The DAO operated entirely through smart contracts on the Ethereum blockchain, allowing token holders to propose and vote on investment decisions without traditional management structures. By May 2016, the DAO had raised approximately $150 million worth of Ether, making it the largest crowdfunding project in history at the time. On June 17, 2016, an unknown attacker began exploiting a critical vulnerability in the DAO's smart contract code. The vulnerability, known as a reentrancy attack, existed in the splitDAO function that allowed users to leave the DAO and withdraw their funds. The contract's flawed logic updated user balances after transferring funds rather than before, enabling the attacker to recursively call the withdrawal function multiple times before the balance was updated. Over the course of several hours, the attacker drained approximately 3.6 million Ether, worth about $60 million at the time. The Ethereum community and developers faced an unprecedented crisis as the attack continued. The vulnerability had been identified by security researchers weeks earlier, but the complex governance structure of the DAO made it difficult to implement fixes quickly. As the attack progressed, developers and miners worked frantically to understand the exploit and develop countermeasures. The attacker's funds were temporarily locked in a child DAO due to the contract's design, providing a 28-day window before the stolen funds could be withdrawn. The incident triggered intense debate within the Ethereum community about how to respond. Two main factions emerged: those supporting intervention through a hard fork to reverse the theft, and those arguing that 'code is law' and the blockchain should remain immutable. After weeks of heated discussion, the Ethereum Foundation decided to implement a hard fork on July 20, 2016, effectively reversing the DAO hack and returning the stolen funds to their original owners. This decision led to a permanent split in the Ethereum blockchain, with the original chain continuing as Ethereum Classic and the new chain becoming the current Ethereum network. The incident highlighted critical risks in autonomous algorithmic systems and led to improved security practices in smart contract development.

Root Cause

The DAO smart contract contained a reentrancy vulnerability in its splitDAO function that allowed an attacker to recursively call the withdrawal function before the contract updated the user's balance, enabling multiple withdrawals of the same funds.

Mitigation Analysis

The incident could have been prevented through formal verification of smart contract code, comprehensive security audits including reentrancy testing, and implementation of reentrancy guards. Post-deployment monitoring systems to detect unusual transaction patterns and emergency pause mechanisms would have limited damage. The absence of code review standards and testing frameworks for autonomous financial systems was a critical gap.

Lessons Learned

The DAO hack demonstrated that autonomous algorithmic systems require rigorous security testing and formal verification before handling significant financial assets. The incident established the importance of security audits, bug bounty programs, and emergency response mechanisms for decentralized autonomous systems, while also highlighting the tension between immutability and corrective action in blockchain governance.

Sources

Critical Update Re: DAO Vulnerability
Ethereum Foundation · Jun 17, 2016 · company statement