A single oversized trade turned into one of the clearest recent examples of execution risk in decentralized finance. A trader routed a $50.4 million USDT order to buy AAVE and ended up receiving only about $36,200 worth of the token after extreme slippage and on-chain extraction tore through the transaction.
What makes the episode stand out is not just the scale of the loss, but how it unfolded in plain sight. The order moved through CoW Protocol, hit a thin SushiSwap AAVE-USDT pool, and was then exploited by automated market actors that captured most of the value before the trade could settle in any economically rational way.
How the Trade Collapsed
The SushiSwap AAVE-USDT pool held only about $73,000 in liquidity when the $50.4 million buy order arrived. That imbalance produced an estimated 99% price impact, effectively guaranteeing that the trade would execute at a catastrophic rate once it reached the pool.
The Aave interface did not process the trade without warning. The platform flagged “extraordinary slippage” and required manual confirmation, yet the user still approved the order on a mobile device and the swap went through despite the obvious liquidity mismatch.
Once the transaction was visible, automated extractive actors moved in quickly. MEV participants used sandwich-style strategies to front-run the pending order and sell into the price spike created by the oversized buy, turning the trader’s mistake into a highly profitable extraction event.
Analysis attributed roughly $44 million of extracted value to those actors. About $34 million was linked to Titan Builder and another $9.9 million to a separate bot, leaving the original trader with a near-total loss on what had been intended as a large AAVE purchase.
What the Incident Says About DeFi Execution Risk
The trade exposed several failures at once rather than a single isolated weakness. It showed how dangerous it is to route large one-shot orders into shallow liquidity, how little protection warnings provide when users can still override them, and how quickly MEV systems can amplify losses once a vulnerable transaction enters the public mempool.
Large swaps need staged execution, deeper pre-trade liquidity checks, or off-chain coordination if they are to avoid turning into slippage disasters exposed to automated extraction.
If a platform allows a single order of this size to execute into a pool with only about $73,000 in liquidity, then clearer warnings alone are not enough and stronger execution safeguards become part of the product responsibility.
