TLDR: LONDONāAFI Protocol said an exploit drained about $480,000 from its afiUSD vault on Ethereum on May 30, and recovery is ongoing.
Key Takeaways:
- AFI Protocol says it still has $225.32 million in total value locked across remaining systems after the May 30 breach.
- It reported the attacker converted about $252,000 DAI into ETH, then sent about 150 ETH to Tornado Cash after testing wallets.
- AFI paused the vault, rotated keys, and is working with Quantstamp, Cantina, and SEAL 911 while offering a bounty to recover funds.
- Compared with its TVL, the reported loss is small, but DeFi hacks remain frequent across bridges, chains, and token systems.
Fast containment helped, but the real test starts when stolen crypto meets privacy tools. Bounty plus tracing partners is the only honest path back to the vault.
Fast containment helped, but the real test starts when stolen crypto meets privacy tools. Bounty plus tracing partners is the only honest path back to the vault.
Q&A
Why would an attacker swap DAI into ETH after draining a vault, instead of moving funds immediately?
Swapping can create liquidity on a larger market, reduce price impact, and set up faster exits. It also helps the attacker avoid sticking to a single token path that could get flagged.
What does sending funds to Tornado Cash signal about the attackerās exit timeline?
It suggests the attacker wanted to break linkability early, likely while testing wallet behavior. Using privacy tooling right after probing can mean they plan to move quickly before tracing firms cluster activity.
How does rotating operational keys and pausing a vault change what investigators can still learn on chain?
Pausing can stop further automated interactions and reduce new logs from the vulnerable component. Rotating keys can also limit follow on control attempts, making it easier to isolate the breach window and affected contracts.
What happens if traces with Quantstamp, Cantina, and SEAL 911 only recover part of the $480,000?
AFI will likely shift from pure recovery to risk reporting and user compensation decisions. Partial recoveries also affect how the protocol prices future yield and audits vault risk controls.
Why do DeFi incidents keep clustering even when TVL is high and protocols say they are secure?
High TVL attracts attackers, and DeFi stacks many moving parts. Even when core systems stay intact, a single vault specific flaw or integration weakness can be enough to trigger a costly, fast exploit.
No comments yet. Be the first to share your thoughts!