Hacks & Security · Explained
Kava Lend exploit drains about 55 million KAVA in BUSD market flaw
An attacker manipulated an inactive BUSD market to inflate collateral and borrow KAVA, according to on-chain reports, Kava says the incident was contained.
Key takeaways
- Dormant market. A BUSD market with little activity remained live and became the entry point for the exploit.
- Accounting flaw. Near-zero net supply caused collateral to be overstated by about 243,000 times, enabling repeated KAVA borrowing.
- Loss gap. The borrowed KAVA's pre-attack value and the proceeds from selling it differ, so final losses await an incident report.
What happened
Kava Lend, a lending protocol on the Kava blockchain, suffered an exploit that allowed an attacker to borrow and remove about 55.2 million KAVA tokens. Bitcoinist and NewsBTC both reported the incident, citing on-chain analysis published by The Block. Kava confirmed the event and said it was confined to Kava Lend, adding that it did not involve an unlimited token mint.
The reports describe the attacker targeting Kava Lend's BUSD market. BUSD, the Binance-branded stablecoin issued by Paxos, has not been minted since 2023, but its market on Kava Lend remained active with very little liquidity. According to the public source code reviewed in the reports, Kava Lend uses a market's net supply to calculate deposit interest. The code blocks calculations at exactly zero net supply but does not handle very small positive amounts. By using a small BUSD loan to reduce the market's net supply to a negligible level, the attacker caused deposits to be recorded at about 243,000 times their actual value, with collateral treated as worth roughly 1.25 billion BUSD.
The inflated collateral let the attacker borrow KAVA repeatedly. The reports say the attacker executed 127 KAVA borrowing transactions and used a second account to settle individual loans, bypassing borrowing limits. On-chain activity cited in the coverage indicates preparation began on November 8, several days before the exploit, through repeated BUSD deposits and borrows. Published accounts place the exploit around November 13, 14; Kava's pooled account, which held about 55.33 million KAVA beforehand, was left with 0.19 KAVA afterward.
The attacker then moved about 49.2 million KAVA to BNB Chain through Kava's LayerZero bridge, beginning early on Saturday, and most of it was sold within an hour, generating about 3,006.5 BNB and 231,557 USDT, or roughly $2.09 million combined. Another 4.58 million KAVA was spread across five addresses that have not been publicly identified. KAVA fell to about $0.042, down roughly 39% over 24 hours, and several partner exchanges suspended KAVA deposits and withdrawals as a precaution. Kava also paused the Axelar bridge, although the stolen tokens had moved through LayerZero.
Why it matters
The case shows how a market with almost no activity can still create a serious opening. Lending systems rely on collateral values to set borrowing limits; when an accounting rule misreads a near-zero market, the protocol can approve loans that no real market price would justify. Depositors may be exposed to every collateral market a lender supports, even if they never use the asset that triggers the failure. The reports also draw a line between the pre-attack value of the borrowed KAVA and the smaller amount realized by selling into a falling market. That difference matters because the amount borrowed, the loss to lenders and the amount ultimately recovered need not be the same.
What the data shows
The figures reported include about 55.2 million KAVA borrowed, valued at roughly $3.76 million at a pre-attack price of about $0.068. The pooled account fell from about 55.33 million KAVA to 0.19. About 49.2 million KAVA crossed LayerZero to BNB Chain and was mostly sold for about $2.09 million in BNB and USDT. The collateral overstatement was about 243,000 times, with deposits treated as worth about 1.25 billion BUSD. The attacker carried out 127 KAVA borrow transactions. KAVA later traded near $0.042, about 39% lower over 24 hours.
Background
BUSD is a legacy stablecoin whose issuer stopped minting new tokens in 2023, but Kava Lend kept a market for it running. The reports say that market had little trading activity and liquidity before the attack. Kava Lend's code is public, and the reports focus on how its interest calculation handles near-zero net supply. The incident follows a broader pattern in DeFi in which risk controls and economic design remain active governance issues for lending markets, as NewsBTC has reported in coverage of Aave governance. Institutional interest in lending infrastructure makes those controls more consequential.
What is still unclear
At the time of the reports, Kava had not published a complete official loss assessment or full post-incident report. The reports do not establish the final loss borne by lenders or depositors, whether any market remains impaired, or what code changes Kava will make. They also do not say whether the 4.58 million KAVA sent to five addresses can be recovered. The two dollar figures in circulation describe different things: a pre-attack valuation of the borrowed tokens and the proceeds from selling part of them.
What to watch
The next useful disclosures are Kava's incident report, its accounting for user losses, and any remediation to the BUSD market or the interest calculation. Independent review of proposed code changes would help show whether the specific near-zero net-supply edge case has been closed. Also relevant is whether other dormant markets on Kava Lend or similar protocols remain operational under the same accounting assumptions.
Questions readers ask
What did the attacker do?
The attacker manipulated an inactive BUSD market to inflate collateral, then borrowed KAVA 127 times and used a second account to settle individual loans.
Was this an infinite mint?
No. Kava said the incident was contained to Kava Lend and did not involve an unlimited token mint; the reports describe an accounting and valuation flaw.
How much was taken?
About 55.2 million KAVA was borrowed, worth roughly $3.76 million before the attack. About 49.2 million KAVA was moved to BNB Chain, with sales realizing roughly $2.09 million.