Description

Under normal behavior, the protocol should safely transfer collected WETH fees to the designated fee collector and revert if the transfer fails to ensure funds are not silently lost and accounting remains correct.

However, the contract uses a direct ERC20 transfer call to send WETH to the collector without checking the return value or using SafeERC20.safeTransfer. For non-standard ERC20 implementations that return false instead of reverting on failure, the transfer can silently fail while execution continues, causing the protocol to assume fees were successfully transferred when they were not.

Risk

Likelihood:

• This occurs whenever the token being transferred does not strictly follow the ERC20 specification and returns false instead of reverting.

• The protocol assumes the transfer always succeeds and does not check the return value, so any silent failure will go unnoticed.

Impact:

• WETH fees intended for the collector may never be received, resulting in stuck or lost funds.

• Protocol accounting may incorrectly reflect that fees were collected, potentially leading to inconsistent balances or misreporting.

Proof of Concept

Recommended Mitigation