
MEV Sandwich Bots: How Much They Take From Traders
Nearly $40M taken from Ethereum traders in 2025. One bot took home about 70% of it.
EigenPhi data reported by Cointelegraph shows sandwich attacks cost Ethereum users close to $40 million in 2025, with roughly 60,000 to 90,000 attacks happening every month. A single operator, known on-chain as jaredfromsubway.eth, was behind about 70% of that volume and has extracted an estimated $295M since March 2023. In June 2026 that same bot got a taste of its own medicine, losing $7.5M to a counter-MEV honeypot. This isn't one scandal. It's an industrial, ongoing market — and it's measurable.
The Scheme: Sandwich MEV at Industrial Scale
A 'sandwich attack' works in three steps: (1) the bot watches the public mempool for a pending swap; (2) it inserts a buy before yours, pushing the price up; (3) it sells immediately after yours at the inflated price. Your swap fills at a worse rate. The bot pockets the difference — minus gas. This is well documented on Ethereum mainnet: EigenPhi-sourced data puts the 2025 toll at nearly $40M, spread across 60,000-90,000 attacks a month. It's not a one-off heist. It's a recurring tax on anyone who signs a swap with public, unprotected settings.
Case File Update
Removed an unsourced $12M / 8,400-trader case; page now uses documented figures.
You signed the trade. The bot signed two more around it. The market didn't move. Your wallet did.
The Hard Truth: It's Legal, It's Public, and It's Dominated by One Bot
MEV — Maximum Extractable Value — is not illegal anywhere. The bots aren't hacking your wallet, stealing keys, or breaking smart contracts. They're reading the same public mempool every node sees and submitting transactions with higher gas. Every blockchain that orders by gas price is vulnerable. The 'predator' is just a faster, richer, hungrier participant in a system you opted into.
EigenPhi's research, cited by Cointelegraph (4 Dec 2025), tagged one operator — the wallet and bot network known as jaredfromsubway.eth — as responsible for roughly 70% of Ethereum sandwich volume. Bitcoin.com News reported the bot has extracted an estimated $295M since March 2023. That's not a scrappy searcher script. That's close to a monopoly on a $40M-a-year market.
Ironically, the hunter became prey. Chainalysis and CoinDesk reported that in June 2026, jaredfromsubway.eth's bot was lured into a counter-MEV honeypot and drained of $7.5M in a single exploit — proof that even the dominant predator bot can be out-engineered. The 'predator' isn't invincible. It's just another piece of code with its own attack surface.
It's not a hack. It's not a bug. It's a feature of public mempools — and one operator industrialized it into a near-monopoly.
The Anatomy: Mempool → Front-Run → Back-Run → Profit
When you click 'Swap' on a DEX, your transaction enters the public mempool — a waiting room every node can read. Sandwich bots scan the mempool continuously. The instant they see a swap with default slippage (commonly 0.5% on Uniswap, 0.3% on most aggregators), they calculate the exact size of a front-run trade that will move the price just enough to extract the full slippage allowance — and not a basis point more.
The bot then submits two transactions around yours in the same block: a buy at a slightly higher gas price (front-run) and a sell at a slightly lower gas price (back-run). Block builders order by gas, so the sequence becomes: bot buys → you buy at a higher price → bot sells. The bot's two transactions cancel out as inventory. The price impact you absorbed becomes the bot's profit. You never had a chance to react. The trade was already over before you saw it confirm.
Operators like jaredfromsubway.eth didn't invent this attack — sandwiching has existed on Ethereum for years. What built a $295M track record was scale and automation: scanning multiple DEXs continuously, filtering for the most profitable pending swaps, and running the playbook around the clock. They didn't invent the attack. They industrialized an old attack with better tooling and more capital.
The bot doesn't need to outsmart you. It just needs to outbid you on gas — and you already lost that race.
Vocabulary Decoded: What the DEX Doesn't Tell You
What the swap UI promised vs what the mempool actually did:
"Best price routing"
What it sounds like:
The aggregator scans every DEX and routes your trade through the cheapest path. You always get the best execution.
What actually happened:
The aggregator did find the best path — at the moment it quoted. Between the quote and the on-chain execution, a sandwich bot can front-run you so the price you actually get is worse than the quote. The aggregator promised the best price; on an unprotected swap, the bot can still take a cut.
"0.5% slippage tolerance"
What it sounds like:
A safety net. If the price moves more than 0.5% against you, the trade fails and you keep your money. Sounds protective.
What actually happened:
It's not only a safety net for you. It's also a budget a bot can target. A bot can calculate a front-run sized to consume most of your slippage allowance and sell immediately. You signed a check that said 'lose up to 0.5%' and, on an unprotected mempool, a bot can cash close to the maximum — repeatedly.
"Decentralized finance"
What it sounds like:
No middlemen. No gatekeepers. Permissionless trading on transparent rails.
What actually happened:
There ARE middlemen — they're called searchers, builders, and validators. They sit between your signature and your settlement, and they can extract value while you watch. Decentralization moved the rent-seeker from a brokerage to a block builder.
The aggregator showed you the best price. The block showed the bot the best opportunity.
How One Bot Took ~70% of a $40M Market
Sandwich extraction isn't a single attack. It's a 24/7 industrial pipeline:
Step 1: Mempool Surveillance
Sandwich bots subscribe to the public mempool of every chain they operate on. They parse pending transactions in real time, decoding swap call data to identify token pairs, sizes, and slippage tolerances.
The mempool is public. Anyone can read it. The dominant bots just read it continuously and act in milliseconds.
Step 2: Profitability Filter
Not every swap is sandwich-worthy. Bots score pending trades on pool depth, slippage allowance, gas cost, and competing bots. Only a fraction of opportunities pass the filter and trigger an attack — EigenPhi's data suggests the market overall runs 60,000-90,000 successful attacks a month on Ethereum.
The filter exists because losing gas on a failed sandwich kills the margin. Picky, well-capitalized bots like jaredfromsubway.eth win the most opportunities.
Step 3: Front-Run + Back-Run Submission
The bot crafts two transactions: a buy ordered just before the victim's swap and a sell ordered just after. Both are submitted to the block builder as a bundle, ensuring atomic ordering.
Bundle submission is the real innovation. Without it, the front-run and back-run could land in different blocks, letting the price arbitrage back before the bot profits.
When the Predator Became Prey: The $7.5M Honeypot
According to Chainalysis and CoinDesk, in June 2026 the dominant sandwich bot got out-engineered:
The Setup: A Counter-MEV Honeypot
An unknown actor deployed a crafted transaction designed to look like a highly profitable sandwich opportunity for jaredfromsubway.eth's bot — essentially baiting the predator's own profit-detection logic.
The bot's filters are built to grab anything that looks sufficiently profitable, fast. That reflex became the exploit's entry point.
The Bite: Bot Takes the Bait
The bot executed its usual front-run/back-run sequence against the crafted transaction, just as it would for any ordinary retail swap.
No warning signs distinguished the honeypot from a normal trade — that was the point.
The Drain: $7.5M Extracted
Instead of the bot pocketing a profit, the malicious contract logic flipped the outcome, draining roughly $7.5M from the bot's own funds in the exchange.
Chainalysis's write-up frames it as a case study in counter-MEV engineering: beating a predator bot at its own game.
The Aftermath
CoinDesk and Bitcoin.com News reported the loss as a blow to a bot that had extracted an estimated $295M since March 2023 — a reminder that dominance in MEV doesn't mean invulnerability.
The underlying sandwich market kept running; only one operator took a one-time hit.
The bot that sandwiched thousands of traders got sandwiched itself — once, for $7.5M.
Documented Figures: The Numbers Behind the Headlines
Three data points, each independently sourced, that frame the scale of sandwich MEV:
EigenPhi data reported by Cointelegraph (4 Dec 2025): sandwich attacks cost Ethereum users close to $40M across 2025, at a pace of roughly 60,000 to 90,000 attacks per month.
Translation: this is a recurring, ongoing market — not a single incident.
EigenPhi tracks on-chain sandwich signatures (identical-block, inverse-direction trades) to produce this estimate; it is the most cited independent dataset on Ethereum MEV.
Jaredfromsubway.eth was responsible for about 70% of Ethereum sandwich volume per EigenPhi/Cointelegraph, and Bitcoin.com News reports the bot extracted an estimated $295M total since March 2023.
Translation: a single well-capitalized operator captures most of this market.
The Block reported as early as August 2024 that this bot kept resurfacing with new contracts after public attention, showing how persistent and profitable the operation is.
Helius reported that one Solana sandwich bot made roughly 65,880 SOL (about $13.4M) in 30 days from 1.55 million sandwich transactions.
Translation: sandwich MEV isn't an Ethereum-only phenomenon — it scales to any chain with a public, orderable mempool.
Solana's faster blocks and lower fees mean sandwich bots there operate at far higher transaction volume but smaller average profit per trade than Ethereum's.
Red Flags: How to Spot You're Sandwich-Bait
- •Default slippage of 0.5% or higher on swaps above $500 — Wide slippage = wide profit margin for the bot. Tighten it to 0.1-0.3% for stables and blue-chips.
- •Using a public mempool for trades above $1,000 — Every public mempool is bot-monitored. Use MEV Blocker, Flashbots Protect, or CowSwap for any meaningful trade.
- •Trading low-liquidity tokens during off-peak hours — Low liquidity = bigger price impact = bigger sandwich. Off-peak hours can mean fewer bots competing for the same opportunity, and a cleaner shot for whichever bot gets there first.
- •Never checking execution price after a swap — Most victims never check. EigenPhi's free MEV Analysis tool shows execution details for a given transaction hash in seconds. Audit your last 10 trades today.
- •Using DEX aggregators that don't route through private mempools — Some aggregators route through public RPCs by default. CowSwap and UniswapX route through batch auctions and private pools by default.
If your settings make life easy for the bot, the bot will live well — at your expense.
The Numbers: What the Documented Data Shows
The scale of sandwich MEV, as reported by independent researchers:
~$40M Lost on Ethereum in 2025
EigenPhi data via Cointelegraph (4 Dec 2025), across roughly 60,000-90,000 sandwich attacks per month.
~70% From One Operator
Jaredfromsubway.eth accounted for about 70% of Ethereum sandwich volume, per the same EigenPhi/Cointelegraph research.
$295M Extracted Since March 2023
Bitcoin.com News' estimate of that single operator's cumulative take, before it lost $7.5M to a counter-MEV honeypot in June 2026 (Chainalysis, CoinDesk).
$13.4M on Solana in 30 Days
Helius reported one Solana bot made about 65,880 SOL from 1.55 million sandwiches in a single month (January 2025 report).
Why DEX UIs Don't Warn You
MEV is everyone's problem and nobody's job:
DEXes Compete on Quotes, Not Execution
Most DEX front-ends show you the *quote* in their UI. The execution price — what actually happens after your transaction confirms — is buried in the transaction receipt. The UI optimizes for the click, not the outcome.
If DEXes showed average execution slippage prominently, users would compare on real outcomes. Few do, because the comparison would be unflattering.
Wallets Don't Simulate Final Outcomes
Most wallets simulate the transaction but use the quote price, not a probabilistic post-MEV estimate. The signature request shows the wallet's best guess, which doesn't account for a possible sandwich.
A few wallets are improving this, but adjusting for predicted MEV before you sign is still not the norm.
L2 Sequencers Profit from Ordering
Several L2s run centralized sequencers that order transactions and capture some MEV themselves, which gives them weak incentives to aggressively stop external sandwich bots. Sequencer fairness proposals have been debated for years; none have shipped broadly at scale.
If an L2 itself profits from ordering, asking it to stop the bots is asking the casino to ban card-counting. The incentives don't line up.
Why Most Victims Never Notice
Sandwich attacks are designed to feel like normal market behavior:
It Looks Like Slippage
When you receive less than the quoted amount, your wallet doesn't say 'sandwiched.' It says 'completed.' To the average user, it looks like the price moved against them — which it did, just for a very specific reason.
The Loss Is Small Per Trade
A few dollars or a fraction of a percent on any single trade is annoying, not catastrophic. People grumble and move on. Aggregated across tens of thousands of trades a month, that 'small annoying' number becomes tens of millions of dollars a year. The bots win by spreading the pain thin.
DEX UI Hides the Evidence
The DEX shows the trade as 'successful' the moment it confirms. The execution price is in the tx receipt; you have to dig. Few people do.
Tools to Prove It Aren't Default
EigenPhi can show you exactly what was extracted, by which bot, on supported chains. But the user has to know EigenPhi exists, find their tx hash, paste it in, and check. Most people never do this for routine trades.
The bot's advantage starts the moment you accept the default slippage. Everything else is math.
Protection: 5 Habits That Make You Sandwich-Proof
You can't outrun a bot. But you can make yourself the wrong target.
Set custom slippage to 0.1% for stablecoin pairs and 0.3% for blue-chips.
Default slippage on most DEX UIs is 0.5% to 1.0% — generous room for sandwich bots to profit. For USDC/USDT swaps, 0.1% is enough. For ETH/wBTC, 0.3% is enough. If your trade fails because of low slippage, the price moved against you in real time — try again, don't widen the window.
Use private mempools (MEV Blocker, Flashbots Protect, CowSwap) for any swap above $500.
MEV Blocker (mevblocker.io) is free, takes about 30 seconds to add to MetaMask, and routes your transactions through a private pool that sandwich bots can't see ahead of time. CowSwap batch auctions clear at uniform prices, removing the public ordering that bots exploit. For trades above $500, this should be the default — not a special case.
Expect bots to be active at all hours — don't rely on timing alone.
MEV bots run continuously and compete for every opportunity. Timing your trades doesn't reliably avoid them; tightening slippage and using private routing does.
For trades above $5,000, use a TWAP order instead of a single market swap.
Time-Weighted Average Price (TWAP) splits a large order into many small executions over minutes or hours. Each piece is too small to attract a sandwich bot. CowSwap, 1inch Fusion, and UniswapX all support TWAP-style orders.
Check your execution price on a block explorer after every swap.
Compare 'amount in' and 'amount out' from the swap event log against the pool's price at the block before yours. EigenPhi's MEV Analysis tool automates this for supported chains — paste a tx hash and it flags whether a sandwich occurred.
Got a Suspicious Message?
Use our AI-powered detector to analyze potential scams instantly.
Key Takeaways
- EigenPhi data via Cointelegraph: sandwich attacks cost Ethereum users nearly $40M in 2025, at 60,000-90,000 attacks per month.
- One operator, jaredfromsubway.eth, was behind about 70% of that volume and has extracted an estimated $295M since March 2023.
- That same bot lost $7.5M to a counter-MEV honeypot in June 2026 (Chainalysis, CoinDesk) — dominance doesn't mean invulnerability.
- Sandwich attacks aren't Ethereum-only: Helius reported one Solana bot made about $13.4M in 30 days from 1.55 million sandwiches.
- Sandwich attacks are legal — they exploit public mempools, not bugs. Default slippage (0.5%+) is effectively a subsidy for bots.
- Private mempools (MEV Blocker, Flashbots Protect, CowSwap) and tight slippage are the practical defense — not timing or luck.
“It's not the market.”
It's a bot — and the data says it's winning.
Frequently Asked Questions
Sources & Citations
Research for this investigation compiled from publicly available blockchain data, security reports, and community documentation.
Cointelegraph Research · 4 Dec 2025
Cointelegraph Research · 4 Dec 2025
Chainalysis · 26 Jun 2026
Chainalysis · 26 Jun 2026
CoinDesk · 21 Jun 2026
CoinDesk · 21 Jun 2026
Bitcoin.com News · 30 Aug 2026
Bitcoin.com News · 30 Aug 2026
Flashbots Docs · Date not published or not verified
Flashbots Docs · Date not published or not verified
The Block · 20 Aug 2024
The Block · 20 Aug 2024
U.S. DOJ (SDNY) · 15 May 2024
U.S. DOJ (SDNY) · 15 May 2024
Verification: On-chain references: none published for this case.
Methodology: Every case needs at least two independent sources before publication, plus verifiable on-chain evidence whenever a public transaction trail exists. Full standards: /methodology
Legal notice: This assessment is based on publicly available data, including on-chain records, official statements and reported incidents. It is journalistic and educational analysis, not legal advice, an accusation of criminal conduct or a court finding. Named companies, projects, domains, wallets and individuals are described as reported by the cited sources; a company name may appear because fraudsters impersonated it, not because the company did anything wrong. If you believe something is inaccurate or out of date, write to cryptostrapon@pm.me and we will correct it and log the change. Editorial policy
More Scam Warnings
Continue learning about crypto threats
7 Crypto Wallet Scams Draining Victims in 2026
Wallet Security • 2026-06-24
Phishing apps stole $4.6B in 2025. See real attack screenshots, fake seed phrase tricks, and the 3-step verification that stops 99% of wallet drains.
Flash USDT Scam Explained: Fake Tokens and Seller Tricks
Token Scam • 2026-06-24
What Flash USDT means, how fake balances and seller pitches deceive, and where to check payments, network contracts, software offers and honeypots.
Airdrop Survey Scams: The Eligibility Check That Drains
Airdrop Fraud • 2025-10-01
Fake airdrop pages hide an approval behind the Claim button. One signature and a drainer contract can move every token in your wallet.