On June 8th, according to X user @litangsongyx's analysis, this morning "trading KOGE/USDT was sandwiched with a single transaction of $47,000" due to the user setting nearly 50% slippage and not enabling MEV protection. The user's single transaction volume was $210,000, ultimately receiving KOGE worth $161,000, losing $47,000. Due to the user's massive trading volume, the router split the transaction across 3 liquidity pools:
$120,000 trading volume used Uniswap V4 liquidity pool;
$43,000 trading volume used Uniswap V3 liquidity pool ending with E507;
$47,000 trading volume used PancakeSwap liquidity pool ending with 7057;
When trading through the PancakeSwap liquidity pool ending with 7057, an MEV robot used a $320,000 transaction to push KOGE to an extremely high level, causing the user to complete the trade at an extremely high price. The PancakeSwap liquidity pool did not have any issues, as the pool is only responsible for exchange, with slippage judgment handled by the order router. The fromTokenAmount parameter indicates the user wanted to exchange $214,838 for KOGE, the minReturnAmount parameter shows the user wanted to receive a minimum of 1,640 KOGE tokens, actually receiving 2,547 KOGE tokens, and the order router did not make any errors.
The problem was setting the slippage too high. $214,838 could exchange for about 3,300 KOGE tokens at the time, and by setting the minimum received amount to 1,640 tokens, it can be inferred that the user set slippage at nearly 50% and did not enable MEV protection. After the MEV attack, the user added KOGE tokens to the ZKJ-KOGE liquidity pool to earn fees.
