← Back to research

Kava Lend Hack Drains 55.2M KAVA From Lending Pool

Kava says the November 14 incident was contained to Kava Lend. An on-chain investigation traced 55.2M KAVA out of the lending pool.

By Stalkchain ResearchPublished Nov 15, 2026Updated Nov 15, 20263 min read
KavaKava LendHack

Quick answer

On November 14, 2026, about 55.2 million KAVA was drained from Kava Lend, according to Bitquery's on-chain investigation. Kava said the incident was confined to Kava Lend and that the KAVA sold on BNB Chain came from existing supply. StalkChain verified that about 49.2 million KAVA reached the seller wallet on BNB Chain on November 14. Bitquery later measured 0.19 KAVA in the lending pool. Kava had yet to announce a plan for affected lenders at our reporting cutoff.

Kava Lend hack in numbers

KAVA drained from Kava Lend
55.2M
Bitquery's November 14 on-chain estimate.
Received by seller wallet on BNB Chain
49.2M KAVA
StalkChain observed three inbound transfers totaling 49,207,600 KAVA on November 14.
Estimated BNB Chain sale proceeds
~$2.09M
Bitquery's estimate based on assets the seller received.
Remaining in the lending pool
0.19 KAVA
Bitquery's later November 14 balance reading.
Blocked at Relay
612,416 USDT
Bitquery reported one blocked bridge order at its November 14 cutoff.

What happened at Kava Lend

Bitquery attributed the drain to an accounting flaw in a dormant BUSD market. The protocol overstated the value of collateral and allowed existing KAVA to be borrowed out of its lending pool. The suspected cause comes from Bitquery's reading of public chain data and protocol code. Kava had yet to publish its own account of the cause at our reporting cutoff. Bitquery's on-chain investigation.

Kava initially reported unusual activity at 11:28 UTC. At 12:01 UTC it said the incident was isolated to Kava Lend and ruled out an unlimited mint. It also said partner exchanges had paused transfers. At 14:05 UTC Kava announced a pause on the Axelar bridge and said an incident report would follow. Kava's first update · Kava's scope clarification · Kava's bridge announcement.

Where the KAVA went

StalkChain's BNB Chain data shows three incoming transfers to the seller wallet on November 14. They totaled 49,207,600 KAVA. The first arrived at 10:01 UTC, and the final transfer arrived at 12:07 UTC. Bitquery reported about $2.09 million in sale proceeds and said Relay blocked an order involving 612,416 USDT. The Relay figure reflects Bitquery's November 14 snapshot. Bitquery's on-chain investigation.

The seller wallet was 0x37d732914f86cc6eb1e87419e3046a739f011042 on BNB Chain. You can look up its public transfers using the StalkChain transaction feed or follow our wallet transfer history guide.

Exchanges paused KAVA deposits and withdrawals

Three South Korean exchanges posted transfer restrictions before Kava's first public update. Upbit later issued a separate trading caution.

ExchangeTime (UTC, November 14)Announcement
Bithumb10:35KAVA deposit and withdrawal pause
Upbit10:36Kava network deposit and withdrawal pause
Coinone10:38Notice of KAVA deposit and withdrawal pause from 10:40
Upbit11:00KAVA trading caution

What remains open for lenders

Bitquery reported that the KAVA pool owed lenders 55.2 million KAVA and held 0.19 KAVA when it checked later on November 14. Kava's announcements through our reporting cutoff gave no reimbursement plan or date for restoration of the Axelar bridge. The affected exchanges publish transfer status in their own notices. Bitquery's pool balance reading · Kava's bridge announcement.

Proxima reported a separate Solana wallet drain on November 14. See Proxima's loss figures and refund coverage.

Kava Lend Hack: 55.2M KAVA Drained, Pool Left With 0.19 KAVA