Solmate safetransferFrom doesnt check the existence of code at the token address, all contract below that use SafeTransferLib and all safeTransfer and safeTransferFrom has the issue below. (See wardens original submission for the impacted function and LOC)
This is a known issue while using solmates libraries. Hence this may lead to miscalculation of funds and may lead to loss of funds, because if safetransfer() and safetransferfrom() are called on a token address that doesnt have contract in it, it will always return success, bypassing the return value check.
If an underlying token is self-destructed, the code may consider the transfer because the lack of contract existence contract.
Due to this, protocol will think that funds has been transferred and successful, and records will be accordingly calculated, but in reality funds were never transferred.
So this will lead to miscalculation and possibly loss of funds.
Use openzeppelins safeERC20 or implement a code existence check.
