Taken i
$183.0k
Larger than 31% of the 2,956 incidents with a figure in our archive; 1,206 were larger.
At a glance
- Date
- Feb 11, 2025
- Severity
- Moderate 3/5
- Way in
- Smart contract
- How
- Business logic flaw
- Chains
- BNB Chain, BSC
- Recovered
- None reported
What happened i
Four.Meme lost $183,000 on 11 February 2025 when an attacker manipulated a liquidity pool's price before the platform integrated it.
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
- Feb 11, 2025 The attack · $183.0k taken
- Added to our incident archive
BlockBoard stories i
Similar past incidents i
| When | Who | How | Taken |
|---|---|---|---|
| Jul 11, 2024 | OpSec | Security vulnerability | $182.0k |
| Jan 3, 2023 | GDS | Business logic flaw | $180.0k |
| Jul 8, 2023 | CIVNFT | Lack of access control | $180.0k |
| Jan 25, 2024 | Nebula Revelation | Reentrancy attack | $180.0k |
| May 29, 2024 | MetaDragon | Lack of access control | $180.0k |
| May 20, 2026 | Butter Bridge | Smart contract vulnerability | $180.0k |
Earlier incidents at Four.Meme i
| When | How | Taken |
|---|---|---|
| Mar 18, 2025 | Price manipulation | $19.5k |
Source: BlockBoard. Information only, not advice.