The DAO Hack

In June 2016, an attacker exploited a reentrancy vulnerability in The DAO, a decentralized autonomous organization built on the Ethereum blockchain. The exploit allowed the attacker to recursively drain 3.6 million Ether, worth approximately $50-70 million at the time. The incident caused a market crash for Ether and forced the Ethereum community to implement a hard fork to recover the funds, resulting in the creation of Ethereum Classic.

On June 18, 2016, an attacker successfully exploited a vulnerability in The Decentralized Autonomous Organization (The DAO) on the Ethereum blockchain to steal 3.7M Ether valued at $70M.

Source: AI Incident Database

Risk classification

  • Primary risk domain: 7 AI system safety, failures, & limitations
  • Primary risk subdomain: 7.3 Lack of capability or robustness

The incident was caused by a critical reentrancy vulnerability in the smart contract code, representing a severe lack of robustness and capability in the autonomous system.

Additional risk subdomains

  • 6.5 Governance failure: The failure of the decentralized governance model and the subsequent forced hard fork that split the community.
  • 4.3 Fraud, scams, and targeted manipulation: The attacker exploited the system to gain a personal financial advantage of $50-70 million.

Causal factors

  • Entity: AI
  • Intent: Unintentional
  • Timing: Post-deployment

The incident was caused by the autonomous execution of Slock.it's smart contract code, which allowed recursive withdrawals post-deployment, leading to an unintentional drain of funds.

EU AI Act risk tier

  • Risk tier: 4 Minimal or No Risk

Minimal or No Risk: The system is a decentralized investment fund operating via deterministic smart contracts, which poses minimal or no systemic risk to fundamental human rights as defined under the EU AI Act, placing it in Risk Level 4.

AI system and alleged parties

  • AI system: None named
  • AI purpose: Smart Contract; Financial Processing
  • Behaviour type: Autonomous
  • Alleged developer: The DAO
  • Alleged deployer: The DAO
  • Alleged harmed parties: DAO Token Holders

Harm severity

Severity ratings are based on this scale.

Highest direct severity in any category: Substantial. Severity is scored from Negligible to Catastrophic in each harm category, for harm the reports describe as caused directly or indirectly by the AI system.

  • Physical: direct Negligible, indirect Negligible
  • Infrastructure: direct Negligible, indirect Negligible
  • Property: direct Negligible, indirect Negligible
  • Financial: direct Substantial, indirect Severe
  • Environmental: direct Negligible, indirect Negligible
  • Malicious content: direct Negligible, indirect Negligible
  • Differential treatment: direct Negligible, indirect Negligible
  • Civil rights: direct Negligible, indirect Negligible
  • Democracy: direct Negligible, indirect Negligible
  • Privacy: direct Negligible, indirect Negligible
  • Psychological: direct Negligible, indirect Minor
  • Epistemic: direct Negligible, indirect Negligible
  • Child sexual exploitation and abuse: direct Negligible, indirect Negligible

Financial

Reported: Yes, the reports explicitly describe a loss of 3.6 million Ether, valued at approximately $50 million to $70 million at the time, across a single occurrence.

Directly caused: The attacker drained 3.6 million Ether from the DAO smart contract, representing an average financial loss of approximately $50 million to $70 million for this single occurrence.

Indirectly caused: The panic following the hack caused the market price of Ether to crash by over 50%, from $21.50 to $10.67, resulting in a temporary paper loss of over $150 million in the value of the remaining DAO assets and broader market capitalization.

Inferred additional harm: While the hard fork eventually allowed investors to recover their Ether, some investors likely realized permanent losses due to panic selling during the crash, and the creation of Ethereum Classic split the asset values.

Psychological

Reported: Yes, the reports describe panic among the investors and the community following the hack.

Indirectly caused: The sudden drain of a third of the DAO's funds and the subsequent 50% crash in the price of Ether caused widespread panic and distress among the estimated 20,000 investors.

People affected

  • Occurrences reported: 1
  • People reportedly harmed: 20000
  • People reportedly exposed: 20000

Potential causes

Management

  • Rushed Deployment: The DAO was launched and funded rapidly without resolving known risks.
  • Inadequate Risk Assessment: Slock.it and curators failed to assess systemic risks of a huge fund size.

Technology

  • Recursive Call Vulnerability: The splitDAO function allowed recursive calls to drain funds repeatedly.
  • Flawed State Update Order: The contract transferred Ether before updating the internal token balance.
  • Overloaded CALL Opcode: EVM CALL opcode was overloaded for method calling and sending Ether.

Data Inputs

  • Lack of Input State Validation: The contract did not validate caller state during recursive execution.
  • Missing Reentrancy Guard Data: No boolean flags or reentrancy locks were used to track execution state.

Human Factors

  • Overconfidence in Smart Contracts: Belief that 'code is law' led to ignoring human fallibility in coding.
  • Inadequate Developer Education: Developers lacked deep understanding of EVM execution and reentrancy.

Process and Methods

  • Absence of Formal Specification: No independent specification of wanted behavior; code was its own spec.
  • Insufficient Exception Testing: The code was not thoroughly tested for edge cases and complex call paths.
  • Slow Response to Warnings: Community warnings and calls for a moratorium were not addressed quickly.

Regulatory Environment

  • Lack of Regulatory Clarity: Unclear legal status of DAOs hindered early oversight and compliance.

Information quality

  • Classification confidence: High
  • Reason for confidence: The reports provide extremely detailed, consistent, and technically precise accounts of the reentrancy exploit, the financial impact, and the subsequent community response (the hard fork). Multiple independent sources dissect the exact code vulnerability and the timeline of events, leaving very little ambiguity about what transpired.
  • Ambiguities identified: The exact identity of the attacker remains unknown, and there are minor variations in the reported dollar value of the stolen Ether due to rapid market price fluctuations during the incident.
  • Alternative interpretations: Some community members argued that the exploit was not a 'hack' or a failure, but rather a legitimate execution of the smart contract's explicitly coded rules ('code is law').

An attacker exploited a reentrancy vulnerability in The DAO, an autonomous smart contract on the Ethereum blockchain, draining 3.6 million Ether (worth 50-70 million dollars). While causing significant financial losses and leading to a permanent blockchain split (creating Ethereum Classic), the incident had minor national security implications, affecting private global investors rather than state critical infrastructure or sovereignty.

  • Overall national security impact: Minor
  • Scope: Multiple nations
  • Primary target: No clear primary
  • Other affected: Multiple nations
  • Alleged perpetrator: Unknown

Threat characteristics

  • Imminence: Long-term. The event is historical and resolved, representing a long-term strategic concern regarding autonomous smart contract vulnerabilities.
  • Autonomy: Full autonomy. The smart contract executed withdrawals and state transitions autonomously without human intervention.
  • Novelty: First-of-its-kind. First-of-its-kind major exploit of a decentralized autonomous organization, establishing a significant precedent for blockchain security.

Impact by dimension

  • Physical security: Negligible. No physical systems, critical infrastructure, or human safety were impacted by the smart contract exploit.
  • Information security: Negligible. No intelligence capabilities, classified information, or systematic information operations were involved.
  • Sovereignty: Negligible. The incident affected a decentralized venture fund and blockchain community, with no direct impact on state authority or government operations.
  • Economic security: Minor. Significant financial loss of 50-70 million dollars and a temporary cryptocurrency market crash occurred, but it was limited to private investors without threatening national economic stability.
  • Societal stability: Negligible. Widespread panic occurred among 20,000 private investors, but there were no threats to public safety, civil liberties, or broader societal stability.
Explore in the interactive Incident Tracker