Headline: Kava Lend drained of ~55M KAVA after accounting bug in near-empty BUSD market — not an “infinite mint” On November 14, an attacker exploited a fragile corner of Kava Lend and walked away with roughly 55.2 million KAVA tokens, exposing a dangerous class of DeFi vulnerability that can lie hidden until unusual market conditions trigger it. What happened - The exploit didn’t create tokens from thin air. On-chain analysis shows the attacker manipulated a largely inactive BUSD market on Kava Lend — a market that had become nearly empty after BUSD’s issuer stopped minting new tokens in 2023. - By driving the effective net supply of that BUSD market extremely close to zero, the protocol’s accounting routine inflated deposited collateral values by roughly 243,000×. In short: a software-accounting error caused collateral to be treated as far more valuable than it actually was. - That misvaluation let the attacker repeatedly borrow. They executed 127 KAVA borrow transactions, pulling about 55.2M KAVA (pre-attack valuation: roughly $3.76M). Bridging and liquidation - Around 49.2M of the stolen KAVA was bridged to BNB Chain via LayerZero. On-chain records indicate sales generated about $2.09M in BNB and USDT — a smaller realized haul than the pre-attack dollar estimate because heavy selling pushed the token price down. - These differing dollar figures illustrate the gap between the nominal value at the time of borrowing, the amount lenders lost on paper, and the proceeds the attacker actually realized. A definitive accounting must await Kava’s formal incident report. Protocol response and outstanding questions - Kava’s team said the issue was isolated to Kava Lend and was not an infinite-mint vulnerability. They reported taking precautionary steps around bridging, and some trading venues imposed restrictions on KAVA transfers. - Those actions may limit further damage, but they don’t automatically restore assets to depositors or explain how the accounting edge case passed testing and audits. - The community needs more than reassurances: a detailed post-mortem is critical. Key answers should include who ultimately bears the loss, whether any markets remain impaired, what code fixes are planned, and whether those fixes will receive independent review. An “audit label” alone won’t illuminate the specific failure mode. Why this matters for DeFi - Lending protocols rely on accurate collateral valuations, oracles, liquidity math and careful accounting. When those assumptions break—especially in an obscure or dormant market—the consequences can cascade. - The Kava incident is a reminder that the most dangerous attack surface can be a forgotten market rather than a high-liquidity pool. Anyone using DeFi lenders is exposed to every supported collateral type, even assets they never directly touch. Context - This event mirrors long-standing risks in money markets and governance debates around risk design, as seen in conversations about other protocols such as Aave. Institutional interest in lending infrastructure only raises the stakes for robust, well-reviewed economic safeguards. Reporting: on-chain data and The Block’s coverage informed this article. A full Kava post-mortem and recovery plan had not been published in the reporting reviewed for this piece. Read more AI-generated news on: https://app.chaingpt.org/news
