A sandwich attack is a type of front-running exploit on decentralized exchanges (DEXs) where a bot places one transaction before yours and another immediately after it, artificially inflating the price you pay and then profiting from the price swing. If you have ever swapped tokens on a platform like Uniswap and noticed you received slightly less than expected, you may have been sandwiched. These attacks are not random glitches; they are systematic, automated, and increasingly common on public, transparent liquidity pools. The good news is that you can significantly reduce your risk by understanding how the attack works and adjusting your swapping habits.
The Mechanics of a Sandwich Attack
To understand the attack, you first need to know how automated market makers (AMMs) like Uniswap set prices. The price of a token in a pool is determined by the ratio of the two assets in reserve. When you buy a token, you remove some of it from the pool and add the other token, which shifts the ratio and moves the price upward.
Step 1: The Bot Spots Your Pending Transaction
When you submit a swap on a DEX, it sits in the public mempool—a waiting room for unconfirmed transactions. Bots constantly monitor this mempool for large or profitable trades. They do not need to see your identity; they only need to see the size of your trade and the pool you are using.
Step 2: The Front-Run and the Back-Run
The bot quickly submits its own swap with a higher gas fee, ensuring it gets confirmed before yours. This front-run transaction buys the same token you want, pushing the price up. Your transaction then executes at this higher, unfavorable price. Finally, the bot submits a back-run transaction that sells the token it just bought, now at the inflated price, capturing the difference as profit.
Step 3: The Profit Is the Price Slippage
The bot’s profit is directly equal to the extra amount you paid for your tokens. If the price moved 2% because of the front-run, you effectively paid 2% more than you should have, and the bot pocketed that difference. The larger your swap relative to the pool’s liquidity, the larger the potential profit for the bot, which is why high-value trades are the primary targets.
Why Uniswap and Other AMMs Are Vulnerable
The core issue is not a bug in the smart contract code; it is the inherent design of a transparent, permissionless system.
- Public Mempool: Every transaction is visible to everyone before it is mined. Bots have no barrier to reading this data.
- Deterministic Pricing: AMM prices are formula-based and predictable. A bot can calculate the exact price impact of your trade in milliseconds.
- No Order Flow Protection: Uniswap does not match buyers and sellers privately; it simply executes against a public pool. This openness is what makes it decentralized, but it also removes the privacy that centralized exchanges offer.
Practical Strategies to Avoid Being Sandwiched
You do not need to stop using DEXs, but you should change how you swap. The goal is to make your transaction less attractive to bots or to make the attack unprofitable.
Set a Tighter Slippage Tolerance
Most wallets default to a slippage tolerance of 0.5% to 1%. If you manually reduce this to 0.1% or 0.2%, the bot cannot push the price far enough to profit without causing your transaction to fail. The trade-off is that your transaction may fail more often during volatile market conditions, but it will fail safely—you keep your funds.
Use a Private Transaction Service
Instead of broadcasting your swap directly to the public mempool, you can use a service that submits your transaction directly to a miner or validator. This bypasses the public waiting room entirely. Many wallets now integrate these "private" swapping options, although they often charge a small fee. On Uniswap’s interface, you may see options for "Flashbots" or similar relays, depending on your wallet.
Swap Smaller Amounts or Use More Liquid Pools
A sandwich attack is only profitable if the price impact is large enough to cover gas fees and bot overhead. If you swap a small amount in a highly liquid pool, the price movement is negligible, and the bot will not bother. If you must swap a large amount, consider splitting it into several smaller trades over time, though this exposes you to price drift.
Advanced Tools: MEV Protection and Batch Auctions
The DeFi ecosystem has developed specialized tools to counter sandwich attacks, and it is worth knowing which ones actually help.
MEV-Protected RPC Endpoints
Some wallet providers and infrastructure companies offer custom RPC endpoints that route your transaction through a private mempool. These are not fully private, but they do hide your transaction from the general public for a short period, which is often enough to prevent a sandwich.
Batch Auction Protocols
Certain aggregators and DEXs use a "batch auction" model where all trades within a specific time window are executed at the same clearing price. Because your trade is grouped with others, the bot cannot single you out. Uniswap’s core pools do not do this, but some aggregators that route through Uniswap do offer this protection as a feature.
Final Risk Assessment: You Cannot Eliminate the Risk, Only Reduce It
It is important to be realistic: as long as you use a public AMM, you are exposed to some level of MEV (maximal extractable value) risk. The strategies above reduce the frequency and severity of attacks, but they do not make you immune. The most effective single habit is to check your slippage settings before every swap and to be suspicious of any transaction that promises a "guaranteed" better price without explaining how it protects you. Understanding the attack is your first line of defense; adjusting your behavior is the second. Always verify the exact output amount in your wallet before confirming a swap, and if the price looks too good—or too bad—to be true, pause and reconsider.