This is a research prototype. The data and analyses are preliminary and not yet validated — we'd welcome your .
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.
Domain classification, causal taxonomy, severity scores, and national security assessments were LLM-classified and may contain errors.
AI systems that fail to perform reliably or effectively under varying conditions, exposing them to errors and failures that can have significant consequences, especially in critical applications or areas that require moral reasoning.
Also classified as
The attacker exploited the system to gain a personal financial advantage of $50-70 million.
The failure of the decentralized governance model and the subsequent forced hard fork that split the community.
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.
AI system
Due to a decision or action made by an AI system
Unintentional
Due to an unexpected outcome from pursuing a goal
Post-deployment
Occurring after the AI model has been trained and deployed
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.
Added categories peak at 2: Minor (Psychological Harm, Indirect)
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.
The reports describe The DAO as an autonomous organization governed entirely by code on the blockchain. It operated independently, executing transactions and splits automatically in response to user inputs without human intervention or centralized control.
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.
The DAO was explicitly designed and deployed as a smart contract on the Ethereum blockchain to autonomously manage and process venture capital investments.
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.
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').
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.
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.
Regulatory Environment
Lack of Regulatory Clarity
Unclear legal status of DAOs hindered early oversight and compliance.
AI system involved
Identified by automated extraction; can differ from the alleged developers above.
