MEV bot steals $370,000 from a phishing victim’s $500,000 loss on the Base chain

iconKuCoinFlash
Share
AI summary iconSummary
On-chain reports indicate that on August 7 (UTC+8), a Base chain user lost 500,000 USDC in a phishing attack. The attacker attempted to swap the funds to WETH but failed to set slippage limits, routing the trade to a low-liquidity Uniswap V4 pool. The trade returned only 67.9 ETH ($129,000), with $370,000 captured by an MEV bot reported in ETH news. The bot paid 0.03 USDC to front-run the trade and spent 3.5 ETH in gas fees. The victim later sent on-chain messages to both the attacker and the MEV address, offering a 10% bounty for a refund.

According to ME News, on August 7 (UTC+8), GoPlus monitoring revealed that a user on the Base chain lost 500,000 USDC due to a phishing attack. When the attacker attempted to convert the stolen funds into WETH, their script lacked slippage protection, routing the transaction through a Uniswap V4 WETH/USDC pool with nearly no liquidity. As a result, the 500,000 USDC were exchanged for only 67.9 ETH (worth $129,000), with $370,000 siphoned off by MEV bots. The MEV bot front-ran the transaction by paying just 0.03 USDC but incurred a gas fee of 3.5 ETH. Subsequently, the victim sent on-chain messages to both the attacker and the MEV address, claiming to have identified the attacker’s identity and offering a 10% bounty in exchange for a refund. (Source: ChainCatcher)

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.