Stake DAO Hack
Incident Overview
On May 27, 2026, the DeFi protocol Stake DAO was exploited on the Arbitrum network following the compromise of a deployer private key. Due to the limited liquidity available for vsdCRV, the attacker was only able to realize roughly $91,170 in profit before swapping and bridging the funds to the Ethereum mainnet.
The incident was a direct result of a private key leakage and was not caused by a vulnerability in the protocol's smart contracts or the LayerZero infrastructure. The attacker gained access to a single Stake DAO deployer key on Arbitrum, which controlled privileged administrative configuration rights.
Using this key, the attacker altered the setPeer() configuration for the vsdCRV cross-chain bridge, effectively redirecting the protocol's trust to a contract they controlled on Ethereum. Approximately 25 seconds after this configuration change, the attacker's contract sent a malicious LayerZero message back to Arbitrum. Because the bridge routing had been altered, the Arbitrum vsdCRV contract accepted the message as an authentic bridging command and minted over 5.4 trillion tokens directly to the attacker’s address. While the nominal volume of these tokens was massive, the attacker could only swap 16.83 million vsdCRV for 43.78 ETH before completely exhausting the shallow liquidity pools.
Incident Report
Protocol Information
Market Context at Time of Hack
What the Attacker Needed to Succeed
Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.
What Auditors Should Check
If you're auditing a protocol with similar architecture to Stake DAO, these are the critical security checks that could have prevented this incident (May 2026).
- Verify all logic paths related to Access Control are guarded by proper access controls and input validation - see the Access Control Attacks attack class for patterns
- Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs
Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.
Free TrialSecurity Audit History
- Audit Report 1 Report
Related Attack Classes
The technique used in this hack maps to these vulnerability classes in our security curriculum:
Sources & References
Learn to Prevent the Next Stake DAO
The Stake DAO hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.