JaredfromSubway Bot Front-Runs Vitalik Buterin’s $4 Token Swap
The JaredfromSubway MEV bot front-ran Ethereum co-founder Vitalik Buterin‘s $4 token swap on May 7, generating $1 million in sandwich-attack volume in the process. The incident was covered by CoinDesk.
The bot extracted value from both sides of Buterin’s transaction, buying the token before his order and selling immediately after. The episode drew immediate attention because Buterin has publicly campaigned against exactly this class of attack for months.
What the JaredfromSubway MEV Bot Did
The bot executed a classic sandwich attack.
It placed a buy order in the same block immediately before Buterin’s swap, driving the price up, then sold into Buterin’s purchase for an instant profit. The $4 nominal size of the original swap made no difference to the bot’s mechanics.
The $1 million in surrounding volume came from the bot cycling capital across the attack sequence, not from Buterin’s trade size itself.
MEV, or maximal extractable value, refers to profit that block producers or automated bots extract by reordering, inserting, or censoring transactions within a block. Sandwich attacks are one of the most common MEV strategies on Ethereum (ETH), and JaredfromSubway is among the most recognized bots operating in this space.
Background
Buterin has spent months pushing for technical solutions to MEV abuse.
His proposals have centered on encrypted mempools, a design in which transaction contents remain hidden until after block ordering is finalized, preventing bots from reading pending swaps and front-running them. The irony of the co-creator of Ethereum becoming a victim of the precise attack vector he has argued against publicly was not lost on the cryptocurrency community.
JaredfromSubway first gained notoriety in 2023 when on-chain analysts identified it as one of the largest sandwich bots on Ethereum by cumulative extracted value.
Also Read: Kraken Parent Buys Reap for $600 Million in Asian Payments Push
Outlook
The incident gives fresh momentum to encrypted mempool proposals. Buterin’s public position means the episode is likely to appear in future governance discussions as a concrete example of how current mempool architecture disadvantages ordinary users and protocol architects alike.
Whether the Ethereum developer community moves toward encrypted mempools as a protocol-level fix or leaves the work to application-layer solutions such as private RPC endpoints remains an open question. Either path carries tradeoffs between censorship resistance and MEV suppression.
Read Next: Adam Back Says Bitcoin is Winning the DeFi Security War at Consensus Miami
