Tree News

GoPlus Security 🚦 · 2026-11-16 11:22 UTC

1/7 ⚠️ Exploit Analysis: On November 14, @KAVA_CHAIN’s native lending protocol Kava Lend was exploited. The attacker reduced the net supply of its largely inactive BUSD market to just 2 base units, inflating the market’s supply interest index by approximately 243,000× in about three minutes. The attacker then used inflated BUSD deposit claims to borrow 55,205,050.60 KAVA across 127 transactions—worth approximately $3.76 million at the pre-attack price. 🔍 Root Cause: Kava Lend uses the supply interest index, supplyInterestFactor, to distribute interest paid by borrowers to depositors. It divides the interest accrued since the previous block, newInterest, by the market’s net supply, totalSupply (cash + borrows − reserves). The public code skips the division and returns a neutral factor when net supply is exactly zero, but does not guard against a positive yet extremely small denominator. When totalSupply approaches zero while remaining positive, the resulting supply interest index can become massively inflated. The attacker first repaid all 37 outstanding BUSD loans on behalf of their borrowers, then used a single deposit–borrow–withdraw transaction to reduce net supply to 2 base units (2×10⁻⁸ BUSD). The tiny amount of interest accrued each block was then divided by these 2 base units, causing the index to rise from approximately 2.76 to 671,186.99—roughly 243,000×—in about three minutes. As a result, the main wallet’s previously deposited BUSD was recorded as a claim worth approximately 1.25449 billion BUSD. The attacker then used a second wallet in a loop: the helper wallet deposited BUSD as collateral; the main wallet withdrew the same BUSD against its inflated deposit claim; and the helper wallet borrowed KAVA at a loan-to-value ratio of approximately 50%. In the next block, the main wallet liquidated the helper wallet. Despite there being almost no BUSD left in the pool to seize—the first liquidation auction had a lot of 0 BUSD—the loan was still closed, freeing up capacity under the KAVA borrowing cap. The configured maximum_limit for ukava was equivalent to 448,358 KAVA.

Loading the story on Tree News…