Kava Lend (November 2026) hack — November 2026
Incident facts
| Date of incident | |
|---|---|
| Publicly disclosed | November 14, 2026 |
| Target type | Lending protocol |
| Loss | $3,672,207Price at time of incident |
| Method | Contract logic errorAn arithmetic flaw in Kava Lend's near-empty BUSD market: with the pool's effective supply pushed down to two base units, the supply interest index grew about 243,000-fold in three minutes, inflating the attackers' collateral; they borrowed KAVA against it in 127 rounds and liquidations erased each loan without recovering enough collateral |
| Chains | Other, BNB Chain |
| Outcome | Unresolved |
What happened
Between 04:04 and 05:42 UTC on 14 November 2026 two wallets drained Kava Lend, the lending app on the Kava blockchain. According to Bitquery's block-by-block reading of the chain, they used the app's almost unused BUSD market: after reducing the pool's supply figure to two base units, its supply interest index grew about 243,000 times in three minutes, which inflated the value of their BUSD deposits as collateral. Against it they borrowed 55.2 million KAVA in 127 loans, and a liquidation erased the debt after each one. The KAVA held in the lending pool fell from 55.3 million to 519.
About 1.3 million of the borrowed KAVA went to repay other borrowers' loans, leaving the attackers with 53.9 million KAVA, about $3.67 million at the pre-sale price of $0.068 (the figure here). Six hours later a third wallet bridged most of it to BNB Chain and sold 48.4 million KAVA in 35 minutes for about $2.09 million, the low end; the price fell 36% during the sale and roughly half over two hours. Upbit, Bithumb and Coinone suspended KAVA deposits and withdrawals and a bridge was paused.
Kava said the event was isolated to Kava Lend and was not an infinite mint, and promised more information. About $1.17 million of the proceeds bought XMR1 on Hyperliquid. A further 612,416 USDT sent through LI.FI to the Relay bridge was not paid out (status BLOCKED_WALLET); Bitquery notes the deposit is marked as one the sender can pull back, so it is not counted as recovered. Kava has not said how lenders, who are owed the drained KAVA, will be covered.
Sources
- Kava on X (14 November 2026, 12:01 UTC)Primary · retrieved 2026-11-15
- Bitquery investigation (14 November 2026)Secondary · retrieved 2026-11-15
- Crypto Briefing (14 November 2026)Secondary · retrieved 2026-11-15
- DefiLlama hacks, Kava Lend entryAggregator · retrieved 2026-11-15
Changes to this entry
- Added at 53.9m KAVA kept by the attackers (Bitquery) x $0.06813 (CoinGecko hourly, 14 Nov 04:00 UTC, before the sale); low $2.09m = proceeds of the 48.4m KAVA sale on BNB Chain. The 612,416 USDT stopped at Relay is not counted as recovered: the deposit is reclaimable by the sender. Replace with Kava's post-mortem figures when published.
Cite this
This data is published under CC BY 4.0. You may reuse it, including commercially, as long as you credit iTokenly and link back.
iTokenly Hack Registry, "Kava Lend (November 2026) hack — November 2026", iTokenly, accessed 2026-11-15, https://itokenly.com/hacks/kava-lend-november-2026https://itokenly.com/hacks/kava-lend-november-2026Permalinks never change. If an entry is renamed, the old address keeps working.
Spotted an error? Write to [email protected]. Corrections to published figures are logged on this page. See the methodology for how entries are checked.