GemPad Hack
Reported loss
$2.0M
Reentrancy
What happened
On December 17, 2024, an attacker exploited a reentrancy flaw in GemPad's multi-chain liquidity-locking infrastructure. Reports put the loss at roughly $1.9 million in locked tokens across Ethereum, BNB Chain, and Base.
How it happened
- The attacker deployed malicious token contracts that could call back during token transfers.
- They used GemPad's vulnerable
collectFeespath while creating or interacting with LP locks. - The external callback re-entered the lock contract before its state was safely finalized.
- Repeated reentry withdrew locked liquidity multiple times across the shared contracts on Ethereum, BNB Chain, and Base.
Protocol details
Evidence
- report @CyversAlerts incident report x.com
- report @TheGemPad incident report x.com
- report GemPad - Rekt rekt.news
- analysis DeFiLlama defillama.com
Understand the attack patterns
Build your security review skills
Work through hands-on labs covering real exploit mechanics, review techniques, and defensive patterns.