Tapioca DAO Hack

TOTAL LOST $4.7M
Medium Private Key Compromised (Social Engineering) / Access Control arbitrum

Summarize with AI

Affected Chain arbitrum Incident surface
Recovered - No recovery reported
All-Time Rank #438 By amount stolen
Protocol Type Exploit/Access control Target category

Incident Overview

On October 18, 2024, Tapioca DAO suffered a social engineering attack that resulted in the compromise of two critical contracts stealing a total of 591 ETH and 2.8M USDC.

The attack was social engineering-based, allowing the attacker to seize ownership of the TAP vesting contract and claim 30M TAP tokens, leading to a sell-off that affected the TAP/ETH liquidity pool. Additionally, by taking control of the USDO stablecoin contract, the attacker added a malicious minter, enabling the infinite minting of USDO, which was then swapped for USDC and ETH, draining liquidity. The attacker successfully stole 591 ETH and 2.8M USDC before moving the funds.

Incident Report

Protocol / Project Tapioca DAO
Date of Incident
Affected Chain(s) arbitrum
Attack Technique Private Key Compromised (Social Engineering) / Access Control
Classification Protocol Logic / Stablecoin
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exploit/Access control
Smart Contract Language Solidity
Official Website www.tapioca.xyz/
Protocol Twitter/X @tapioca_dao
Team Anonymous
Source Code Unverified

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.

Technical Knowledge Operational-security tradecraft (phishing, malware, leaked seed phrases, or insider access) to obtain treasury signing authority
Capital Required Minimal capital - only enough to cover gas while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised wallets / multisig signers, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of Tapioca DAO's high-value treasury accounts and the authority / multisig structure controlling them
Execution Speed Speed to drain the compromised accounts before the team detects the breach and revokes signing authority or freezes the assets
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Hard to catch — private key / OpSec failures are outside smart contract audit scope

If you're auditing a protocol with similar architecture to Tapioca DAO, these are the critical security checks that could have prevented this incident (October 2024).

  • Verify all logic paths related to Private Key Compromised (Social Engineering) / 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 Trial

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Access Control Attacks examples →

Sources & References

Learn to Prevent the Next Tapioca DAO

The Tapioca 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.

Recreate exploit patterns safely Free Trial