Taken i
0.40 WAVAX
No dollar figure was reported, so we do not rank it by size.
At a glance
- Date
- Mar 18, 2025
- Severity
- —
- Way in
- Smart contract
- How
- Business logic flaw
- Chain
- Avalanche
- Recovered
- None reported
What happened i
An attacker drained 0.40 WAVAX from a liquidity pool on March 18, 2025 by exploiting a token that allowed external burning of pair reserves before the pool could sync its balances.
Funds after the attack i
Nothing recovered, returned or frozen has been reported so far. Funds often come back days or weeks after a theft; this updates when the record does.
Timeline i
- Mar 18, 2025 The attack · 0.40 WAVAX
- Added to our incident archive
BlockBoard stories i
Similar past incidents i
| When | Who | How | Taken |
|---|---|---|---|
| Nov 17, 2026 | B18 TimeBank | Smart contract vulnerability | $404.5k |
| Nov 17, 2026 | Paytaca | Backend vulnerability | — |
| Nov 16, 2026 | MORE Markets | Smart contract vulnerability | $308.0k |
| Nov 15, 2026 | Chain Games | Smart contract vulnerability | $20.0k |
| Nov 14, 2026 | Kava Lend | Smart contract vulnerability | $3.8M |
| Nov 14, 2026 | Luxor | Software vulnerability | $10.5k |
Earlier incidents at unverified i
| When | How | Taken |
|---|---|---|
| Mar 16, 2026 | CheckoutPool old BOC missing access control | 85,730 USDC |
| Aug 16, 2025 | Business logic flaw | 3,131.11 DAI |
| Jul 17, 2025 | Signature verification | 502.42 USDT |
| Jul 5, 2025 | Access control | $285.7k |
| Mar 6, 2025 | Business logic flaw | 980.32 USDC |
Source: BlockBoard. Information only, not advice.