Submitted by jonah1005
addLiquidity in the VaderRouter and VaderRouterV2 contract does not check the minimum liquidity amount. This makes users funds vulnerable to sandwich attacks.
The team says a minimum amount is not required as the VaderPool supports imbalanced mint. However, imbalanced mint is a helper function of buying tokens and providing to lp. A sandwich attack would take over more than 50% of a transaction in an illiquid pool.
Given the current network environment, most transactions in the mempool would be sandwiched. However, users may avoid this attack if they only send tx through flashbot RPC. I consider this is a medium-risk issue.
VaderRouterV2.sol#L77-L96
That says a user wants to provide 1M ETH in the pool.
Attackers can sandwich this trade as follows:
None
Always check how much liquidity a user received in a transaction. A tx would not be sandwiched if its not profitable.
We could learn a lot about MEV from Robert Millertweets.
SamSteinGG (Vader) disputed:
alcueca (judge) commented:
SamSteinGG (Vader) commented:
