Copy
Trading Bots
Events
More

Ethereum MEV Bot Loses $7.5M in Approval Trap

2026/06/21 21:25Browse 0

A well-known Ethereum MEV bot, Jaredfromsubway.eth, has been drained of approximately $7.5 million in an exploit that leveraged a transaction approval trap, according to on-chain security firm Blockaid. The attack targeted a vulnerability in the bot's router contract, forcing it to execute unfavorable sandwich trades that benefited the attacker. Blockaid first flagged the incident on its monitoring channels and shared a detailed analysis on X.

Exploit Mechanism

The attacker used custom smart contracts to trick the bot into approving and executing trades that were unprofitable for the bot but profitable for the attacker. Blockaid explained that the exploit exploited a weakness in how the bot processed transaction approvals, essentially manipulating it into a series of losing trades. The bot, known for its high gas consumption and active arbitrage strategies, was unable to detect the trap before its contract balance was drained.

Implications for Automated Bots

This incident underscores that even sophisticated MEV bots are vulnerable to protocol-level smart contract traps. Blockaid's analysis, available on X, highlights the need for continuous security auditing and vigilance, even among established Ethereum participants. The exploit serves as a reminder that automated trading systems must constantly adapt to new attack vectors, as cleverly designed traps can bypass standard safeguards.

Disclaimer: This page may contain third-party information and does not necessarily reflect BYDFi's views or opinions. This content is for general reference only and does not constitute any representation, warranty, financial advice, or investment advice. BYDFi is not responsible for any errors, omissions, or any results arising from the use of such information. Virtual asset investments involve risks. Please carefully evaluate the risks of the product and your risk tolerance based on your financial situation. For more information, please refer to our Terms of Use and Risk Disclosure.