Dolomite Hack

TOTAL LOST $1.9M
Medium Acces Control Exploit / Other ethereum

Summarize with AI

Affected Chain ethereum Incident surface
Recovered - No recovery reported
All-Time Rank #658 By amount stolen
Auditors 2 Prior security audits

Incident Overview

Dolomite encountered an approval attack, leading to approximately $1.9 million in losses on the Ethereum network.

The attacker exploited the batchTransfer feature within the TradeDelegate contract, exploiting users' approved tokens and transferring them to the malicious contract. This method allowed the hacker to execute unauthorized transfers of approved tokens, resulting in significant financial losses.

Incident Report

Protocol / Project Dolomite
Date of Incident
Affected Chain(s) ethereum
Attack Technique Acces Control Exploit / Other
Classification Protocol Logic / Yield Aggregator
Primary Source View Post-Mortem

Protocol Information

Protocol Type Lending
Smart Contract Language Solidity
Official Website dolomite.io/
Protocol Twitter/X @Dolomite_io
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
DeFi Ethereum Ecosystem Coinbase Ventures Portfolio Lending & Borrowing Arbitrum Ecosystem Berachain Ecosystem Binance Alpha Airdrops Binance Ecosystem

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 Deep understanding of acces control exploit / other and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with ethereum smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Dolomite's contract logic - root cause: protocol logic / yield aggregator
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
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? Likely — with a thorough Acces Control Exploit / Other audit checklist and test coverage
Audited by Audit Report 1, Audit Report 2 — still lost $1.9M. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • Verify all logic paths related to Acces Control Exploit / Other 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

Security Audit History

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 Dolomite

The Dolomite 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