Clober Liquidity Vault Hack

TOTAL LOST $500K
Low Reentrancy base

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain base Incident surface
Recovered - No recovery reported
All-Time Rank #1003 By amount stolen
Auditors 1 Prior security audit

Incident Overview

Clober is a fully on-chain orderbook DEX protocol that offers CEX-equivalent trading experience, powered by Limit Order Book with Segment Tree for Efficient Order-matching (LOBSTER) algorithm.

This is classified as a Reentrancy . Compare similar hacks →

Incident Report

Protocol / Project Clober Liquidity Vault
Date of Incident
Affected Chain(s) base
Attack Technique Reentrancy
Classification Protocol Logic
Primary Source View Post-Mortem

Protocol Information

Protocol Type Dexs
Official Website app.clober.io/
Protocol Twitter/X @CloberDEX

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 reentrancy and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with base smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Clober Liquidity Vault's contract logic - root cause: protocol logic
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? Yes — skilled auditors routinely flag Reentrancy vulnerabilities in code review
Audited by Audit Report 1 — still lost $500K. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • Verify all logic paths related to Reentrancy are guarded by proper access controls and input validation - see the Reentrancy attack class for patterns
  • Check that all state-changing functions follow the Checks-Effects-Interactions (CEI) pattern to prevent reentrancy and logic ordering bugs
  • 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 Reentrancy examples →

Reentrancy

Sources & References

Browse all hacks

These hacks used the same attack technique. Understanding the pattern helps prevent future exploits.

1Inch $2.6M
Reentrancy
StepHeroNFTs $90K
Reentrancy
Clober $500K
Reentrancy
Penpie $27.0M
Reentrancy
PolyNetwork $5.0M
Reentrancy
GAME $50K
Reentrancy

Learn to Prevent the Next Clober Liquidity Vault

The Clober Liquidity Vault 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.

Start Free Trial Browse Attack Library
Recreate exploit patterns safely Free Trial