An attacker drained about 55.2 million KAVA from Kava Lend on November 14, 2026, after exploiting how the protocol valued deposits in a nearly empty stablecoin market. The tokens were worth about $3.76 million at prices before the attack, according to on-chain data reviewed by The Block.
Kava said the incident was confined to its lending protocol and did not involve unlimited minting of KAVA. The distinction matters for traders: the attacker drained existing tokens from a lending pool, then moved much of that balance to another network to sell it.
Key Takeaways
- The Block estimates that about 55.2 million KAVA was drained, worth roughly $3.76 million before the attack.
- About 49.2 million KAVA was moved to BNB Chain, where most of it was sold. The reported proceeds were about $2.1 million.
- Kava said the incident was limited to Kava Lend. As of November 16, an official loss figure, recovery total and repayment plan could not be verified.
How a Nearly Empty BUSD Market Led to the Loss
In crypto lending, a borrower’s collateral helps determine how much they can take out of a pool. If the protocol overstates the value of that collateral, it can lend far more than the deposit should support.
The Block’s review of the transactions found that the attacker took a small loan from Kava Lend’s BUSD market, leaving its net supply barely above zero. The calculation used to credit interest then inflated the recorded value of BUSD deposits by roughly 243,000 times. The attacker used an existing BUSD deposit as collateral and repeatedly borrowed KAVA against the inflated value.
The Loopscale exploit illustrates a similar risk: when a lending protocol accepts collateral at an inflated value, the attacker can take real assets from the pool. The two incidents involved different mechanisms, but both show why a lending pool depends on sound collateral accounting.
Why the Two Dollar Figures Differ
The $3.76 million estimate values the KAVA drained at its price before the attack. The roughly $2.1 million figure refers to what the attacker reportedly received in BNB and USDT after selling most of the tokens moved to BNB Chain. One number estimates what left the pool; the other measures proceeds from a subset of the tokens. Neither is a recovery figure.
The transfers also involved two distinct routes. The attacker moved tokens to BNB Chain via LayerZero. Kava separately paused the Axelar bridge as a precaution, according to The Block. Because cross-chain transfers rely on specific bridges, a pause on one route does not establish the status of another.
What Traders and Lenders Should Watch
In its initial incident update, Kava said it had identified transfers and sales on BNB Chain and that the incident was contained within Kava Lend. Some exchanges paused KAVA transfers following the exploit. Anyone planning to move KAVA should check the exchange’s current status for deposits and withdrawals on the network they intend to use. Lenders should look for a separate update on access to funds in the affected pool.
Conclusion
The available transaction data shows how an inflated BUSD deposit let the attacker drain KAVA already held in the lending pool. The next update to watch is Kava’s incident report, particularly what it says about lender balances, any assets recovered, and when users can access affected funds.
Related Posts:
Related posts:
- Ethereum Layer-2 Network Base Sets New Daily Record for DEX Trading Volume
- Bahrain’s Rain Crypto Exchange Hit by $14.8M Exploit, Funds Diverted to BTC and ETH
- Elon Musk Reopens Lawsuit Against Sam Altman’s OpenAI: Details
- Supreme Court Greenlights US to Sell $4.4 Billion in Seized Silk Road Bitcoin
- US Spot Bitcoin ETFs Attract Record $479M in Inflows, Hitting 2-Week High













