One of Ethereum’s most notorious trading bots just got beaten at its own game. Jaredfromsubway.eth, a crypto trading bot long associated with front-running on-chain DeFi trades and a name that references disgraced former Subway spokesperson Jared Fogle, was lured into a trap and drained of roughly $7.5 million in crypto.
On Ethereum and similar crypto networks, MEV stands for maximal extractable value (originally known as miner extractable value). In simple terms, it refers to the extra profit that can be made by controlling how transactions are ordered inside a block on a particular blockchain. Basically, whoever assembles a block on a crypto network sits in a privileged position and can profit from seeing user transactions before they are finalized. This is most relevant to crypto networks where decentralized finance (DeFi) applications live, such as Ethereum.
The concept becomes much easier to understand once you get to sandwich attacks, which are Jaredfromsubway’s specialty. In a sandwich attack, a bot spots a pending trade in the crypto network’s mempool, jumps in front of it with its own buy order, lets the victim’s trade push the price higher, and then sells immediately after. The user gets a worse execution price, while the bot profits from the victim’s price impact and the worse execution permitted by the user’s slippage settings.
Jaredfromsubway became infamous because it industrialized that process. The bot has been widely cited as one of the most prolific sandwich attackers on Ethereum, and a previous report from Cointelegraph Research linked the bot to roughly 70% of sandwich attacks on the network from November 2024 to October 2025. For ordinary DeFi users, that made Jaredfromsubway less of a meme and more of a recurring tax collector embedded in the structure of trading. Protos recently highlighted just how opportunistic Jaredfromsubway can be when it reported that the bot even sandwich attacked a trade made by Ethereum creator Vitalik Buterin.
How Jaredfromsubway Was Tricked
That reputation is what made the recent incident so striking. Rather than exploiting a smart contract bug or stealing a private key, the attacker appears to have targeted Jaredfromsubway’s operating logic. Reports on the incident described it as a kind of counter-MEV honeypot. According to an X thread posted by crypto security platform Blockaid, the setup involved dozens of fake ERC-20 tokens, some designed to mimic familiar assets such as WETH, USDC, and USDT, along with sham liquidity pools that made the contracts look like profitable opportunities for an automated trading system (Note: Readers should not assume that the Jaredfromsubway account tagged in Blockaid’s thread is operated by the real entity behind the bot).
🚨Community Alert:
Blockaid Exploit Detection system detected an exploit involving the @jaredsmev MEV bot on Ethereum.
The incident resulted from attacker-controlled contracts tricking an automated MEV execution system into granting token approvals, later used to drain funds.…— Blockaid (@blockaid_) June 20, 2026
The point was not to trick a human trader into clicking a malicious link. It was to bait a bot like Jaredfromsubway into doing what it always does.
The attacker deployed 66 counterfeit token contracts over a period of weeks and structured them to resemble profitable MEV opportunities, says Blockaid’s recounting of the incident. In order to interact with those routes, Jaredfromsubway’s system approved attacker-controlled helper contracts to spend tokens on its behalf. At first, those approvals reportedly appeared harmless because the associated trades immediately used the allowances. Later, however, the attacker introduced routes that left some of the allowances unused, giving attacker-controlled contracts standing permission to move the bot’s tokens. Once enough of those permissions accumulated, the attacker swept genuine WETH, USDC, and USDT from addresses controlled by the MEV operation.
The total haul was estimated at about $7.5 million, and the entity that set the trap has since sent some of those funds to Ethereum-based crypto mixer Tornado Cash, according to CoinDesk.
DeFi’s Broader Issues
Jaredfromsubway is a vivid example of a broader issue with financial activity on transparent blockchains. If pending transactions are visible before they settle, then actors with privileged access to block production can exploit that visibility. Even in traditional finance, front-running is a dirty word. In DeFi, versions of the same kind of behavior have often been treated as a business model or as an unavoidable side effect of open systems.
Of course, researchers and infrastructure providers are also developing ways to limit the more harmful forms of MEV, including private transaction routing, encrypted mempools, and mechanisms intended to make transaction ordering fairer or less susceptible to manipulation.
And even if one sets aside MEV, the DeFi sector’s security record has looked much shakier over the past year or so. In April, JPMorgan analysts said persistent security vulnerabilities continue to limit DeFi’s institutional appeal. Notably, April was the worst month on record for crypto protocol hacks by sheer number of incidents, with 29 hacks tracked in a single month and $651 million in losses recorded.
Manuel Aráoz, an OpenZeppelin co-founder and one of the early prominent names in smart contract auditing, recently said he now considers all of DeFi unsafe and has advised friends and family to exit their positions. His argument was that AI is making the attacker-defender imbalance worse, as coding agents are becoming “superhuman at finding vulnerabilities” while defenders are still catching up to this new paradigm. However, the recent vulnerability found in Zcash (ZEC) that would have allowed an attacker to effectively print ZEC out of thin air was reportedly discovered through the proactive, defensive use of Anthropic’s Claude Opus 4.8. OpenZeppelin also distanced itself from Aráoz’s assessment, saying the threat is real but arguing that AI-augmented and continuous security work is the appropriate response rather than abandoning DeFi.
Read the full article here
