Kava Lend’s Dormant BUSD Market Let an Attacker Borrow 55 Million KAVA

Key Takeaways
- An attacker used a dormant BUSD market to borrow about 55.2 million KAVA through 127 loans.
- Most of the moved tokens were sold on BNB Chain for about $2.1 million; that is less than their pre-sale valuation.
- Kava said the incident was contained within Kava Lend and did not involve an infinite mint; its full incident report had not been published by November 15.
**Updated November 15, 2026**
A near-empty lending market became the opening for an attack that drained almost all the KAVA held in Kava Lend’s lending pool. On November 14, two wallets borrowed about 55.2 million KAVA through a sequence of 127 loans, according to blockchain analytics firm Bitquery. At prices before the sell-off, that amount was worth roughly $3.7 million. Most of the coins were moved to BNB Chain and sold, bringing in about $2.1 million.
The distinction between those figures matters: the pre-attack value of the borrowed tokens was not the proceeds the attackers realized. Kava has not published a final loss figure or incident report. It said the event was contained within Kava Lend and did not involve an “infinite mint,” meaning the attack used existing tokens rather than creating new KAVA.
How a nearly dormant BUSD market became collateral
Kava Lend is a money market on the Kava blockchain. Users supply tokens to shared pools, and borrowers take loans against collateral. A deposit’s value can change as interest accumulates, tracked through a supply index.
Bitquery’s reconstruction says the attacker targeted a BUSD market that had very little activity. BUSD, the dollar-linked token once issued by Paxos for Binance, stopped being minted in 2023. In the Kava pool, reserves exceeded the remaining cash and loans. That left the denominator used in the interest-index calculation extremely small and negative.
Kava’s publicly available source code skips a division when the denominator is exactly zero, but the analysts found no equivalent guard for a tiny non-zero value. The attacker manipulated the market’s net supply to just two base units. The index then rose about 243,000-fold in three minutes, making a small BUSD deposit appear vastly larger in the protocol’s accounting.
That was an accounting distortion, not real collateral arriving in the pool. The attacker used the inflated claim to borrow KAVA. Bitquery says a second wallet repeatedly borrowed and was liquidated; the liquidation closed each loan despite the pool having almost no BUSD to seize. Clearing the debt reopened room under the borrowing cap, allowing the cycle to repeat 127 times in 98 minutes.
Where the KAVA went
The Block’s on-chain review found the Kava Lend module account fell from about 55.33 million KAVA to 0.19 KAVA in a little over an hour and a half. Bitquery separately traced about 48.4 million KAVA sold on BNB Chain for roughly $2.1 million. The Block reported about 49.2 million coins crossed to BNB Chain through LayerZero, with most sold for approximately 3,006 BNB and 231,557 USDT.
Those are different measures: one describes the amount moved across the bridge, while Bitquery tracks the amount it identified in sales. Neither should be confused with the higher pre-sale market value of the original borrowing.
Bitquery also reported that the Relay bridge blocked 612,416 USDT associated with the proceeds. That is a separate interception and does not establish that the remaining funds have been recovered. The analytics firm’s wallet labels and tracing are its own analysis of public-chain data, not a determination by a court or an official Kava incident report.
Kava’s response and the transfer restrictions
Kava first said it was investigating unexpected activity from an application in its ecosystem. In a follow-up, it acknowledged KAVA transfers to BNB Chain and said the incident was isolated to Kava Lend. The team later announced a precautionary pause to withdrawals through the Axelar bridge. The stolen KAVA had moved through LayerZero, so the Axelar pause should not be described as reversing or stopping that route.
The Defiant reported that Upbit, Bithumb and Coinone suspended KAVA deposits and withdrawals on November 14. These were transfer restrictions, not necessarily suspensions of KAVA trading. Exchange notices and service status can change, so users should check the relevant exchange’s current notice before initiating a deposit or withdrawal.
At the time of reporting, Kava had promised a complete incident report but had not published one. The available account of the calculation flaw and borrowing sequence comes from independent on-chain analysis. The protocol team has not publicly confirmed each technical detail or explained how suppliers will be made whole.
What the incident does—and does not—show
Kava said the incident did not involve an unlimited creation of tokens and described the problem as confined to Kava Lend. That narrows the claim about what happened; it does not mean the lending pool was unharmed or that deposits are currently withdrawable. Bitquery’s snapshot showed the pool held almost none of the KAVA it owed lenders, but its balance can change and should not be treated as a current live withdrawal test.
For users, the practical question is not simply whether a blockchain keeps producing blocks. An application can remain accessible while a lending market has insufficient assets to meet claims. Before supplying funds to any lending pool, check which assets are active, how collateral and interest are calculated, whether withdrawal liquidity is available, and whether there is a current incident notice. A dormant market can still affect the accounting of a live protocol if its calculations rely on balances near zero.
Kava’s forthcoming post-mortem and any remediation plan will determine what happened at the code and governance levels and what suppliers can expect. Until then, the on-chain tracing provides a detailed but independently produced reconstruction—not a final accounting from the team.
DISCLAIMER
This article is for informational purposes only and does not constitute financial advice. Cryptocurrency investments involve substantial risk and extreme volatility - never invest money you cannot afford to lose completely. The author may hold positions in the cryptocurrencies mentioned, which could bias the presented information. Always conduct your own research and consider consulting a qualified financial advisor before making any investment decisions.









