The deposit() function calculates shares based on the current exchange rate, mints those shares to the user, and then calls assetToken.updateExchangeRate() with a calculated fee. However, this fee is entirely unbacked—the actual underlying tokens are not transferred into the AssetToken contract until the very last line. Because the exchange rate is artificially inflated by this fee, the rate permanently becomes greater than 1.0. Later, when a user calls redeem(), the function multiplies their shares by this inflated rate to calculate the payout. This results in the contract attempting to safeTransfer more underlying tokens than it actually holds. The transfer reverts with "ERC20: transfer amount exceeds balance", effectively locking all deposited funds permanently.
Likelihood: High. This is triggered by the first legitimate deposit made by any user, with no attacker action or special conditions required.
Impact: High. The protocol is permanently bricked. All users are unable to redeem their shares, causing a total loss of access to funds for all liquidity providers.
The PoC deposits funds, then attempts to redeem. The redeem reverts because the inflated rate caused the requested transfer amount to exceed the pool balance.
Remove the phantom fee calculation from the deposit path. The exchange rate should only increase when actual yield is generated and transferred to the pool.
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.