On March 12, 2025, at around 9:04 a.m. (UTC), someone sent 220,806 USDC to a Uniswap pool to get USDT. An exchange between two digital dollars. The kind of transaction where you'd expect to lose a few cents in fees.
They received 5,273 USDT. About 2.4% of what they put in. More than $215,000 evaporated in a single Ethereum block.
No hack. No contract vulnerability. Just a recipe bots know by heart: the sandwich.
The recipe, in three slices
Basic ingredient: the mempool. It's the public waiting room where transactions sit before entering a block. Anyone can read it. Bots can too, in a matter of milliseconds.
Top slice. The bot spots your pending swap. It buys the same asset just before you, paying a little more to jump ahead. The price goes up.
You’re the filling. Your order executes at the inflated price. You get less than you expected.
Bottom slice. Right after you, the bot sells. It pockets the difference. All three transactions fit in the same block, in that exact order.
What made March 12 so brutal
It comes down to one setting: slippage tolerance. That’s the maximum price difference you’re willing to accept before your order is canceled. According to EigenPhi’s analysis, this transaction’s price limit was set to zero, which effectively meant: “I accept any price.” The bot drained the USDT from the pool, let the swap go through, then put everything back. In the same five minutes, EigenPhi counted six similar sandwich attacks, for total losses of around $714,000.
The term for all this is MEV: the value a block producer or bot can extract by choosing the order of transactions. The term comes from a 2019 research paper titled “Flash Boys 2.0.”
And this isn’t just an Ethereum thing. Solana doesn’t have a native mempool, but the Jito client offered one. In March 2024, Jito shut it down overnight, explaining that filtering sandwich attacks had become a game of cat and mouse they were bound to lose.
My take, which may not be popular
People like to say, “It’s the user’s fault; they should have set their slippage.” I think that’s too easy. When an interface lets a $220,000 order through with zero protection and no full-screen red alert, the problem isn’t just the human. A market where one wrong click automatically funds a bot isn’t “neutral.” It’s simply well-oiled for the people writing the code.
What I keep in mind for my own DEX swaps:
- set a low, considered slippage tolerance; never leave it on “automatic” without checking;
- split up a large amount instead of sending it all at once through a small pool;
- check whether your wallet or aggregator offers private submission (protected RPC), which avoids the public waiting room.
None of this makes you invisible. It just makes you less appetizing.
Bots don’t sleep, whether you’re swapping $ETH or $SOL. The real question: before today, did you know where the slippage setting was in your favorite app, or have you always left it at the default?
Not financial advice. Sources: Cointelegraph, EigenPhi, Routescore (block 22029771), CoinDesk.