Aave v3 exploit drains up to $310K after Safe module attack
An exploit on a FlashLoopAdapter module linked to Aave v3 drained about 114 ETH, with multiple reports putting the loss at roughly $305,000 to $310,000 from two Safe multisig wallets. Aave’s founder said Aave v3 itself was unaffected, and the contract involved was a third-party adapter rather than Aave’s core pools.
What this rests on
What it means
Each sentence links inside to the piece that supports it.
Users who relied on the affected Safe wallets would notice the loss immediately, because the attack drained funds from two multisig addresses. Aave users would also see that the incident was described as separate from Aave v3 itself, with the affected contract sitting outside the core protocol.
Before this event, the adapter was used to manage leveraged Aave v3 positions through a third-party module. After the exploit, that same setup could no longer be treated as secure in the way it had been, because the access-control weakness in FlashLoopAdapter was the route used to take funds.
Market reaction
How the story was built
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 1.2 years ago | numa. · Incorrect Share Accounting incident | $313k |
| 2.7 years ago | Poldo (POLDO) incident | $311.6k |
| 2.7 years ago | Bullran Index incident | $310k |
| 2.7 years ago | LongNoseDog (LONG) incident | $309.7k |
| 4 months ago | mySwap CL · Incorrect Share Accounting incident | $305k |
4197 incidents stored · 1254 were as large as this one or larger ($310k)
What could happen next
What the prediction markets currently price as likely. This is context, not a forecast of ours: there is money on it, and that is all we show.