0x714a6d31714a…714a6d34
Kava Lend exploit drains 53.9 million KAVA worth $1.83 million
Attackers inflated BUSD collateral 243,000-fold on Kava Lend, extracting 53.9 million KAVA worth $1.83 million. Kava will seek a governance vote to permanently end new lending.

Outputs
Exploit drained ~53.9 million KAVA, valued by Kava at approximately $1.83 million
BUSD deposit values were inflated roughly 243,000-fold; the attacker borrowed 127 times against fake collateral
~49.2 million KAVA bridged to BNB Chain via LayerZero and swapped for ~$2.09 million in BNB and USDT
Kava plans a seven-day governance vote to permanently end new lending on Kava Lend
Kava says the vulnerability is patched, part of the stolen funds frozen, and law enforcement is involved
An exploit against Kava Lend drained approximately 53.9 million KAVA, valued by the project at roughly $1.83 million, according to Kava's own account of the incident. The project now plans to ask governance voters to permanently stop new lending on the protocol, a decision that would require a seven-day vote and has not yet been approved.
Kava stated that its underlying blockchain was unaffected. That claim, however carefully worded, addresses the chain itself — not the lending pool that absorbed the loss.
How did the attacker drain the pool?
The attacker manipulated lending calculations so that Kava Lend overstated the value of BUSD collateral, Kava said. On-chain records show the attack targeted a largely empty BUSD market: deposit values inflated roughly 243,000-fold, an extraordinary distortion that the protocol's accounting failed to catch.
The attacker then borrowed against the inflated collateral 127 times in succession. A second account cleared those loans, effectively bypassing the protocol's KAVA borrowing cap — a cap that existed precisely to limit this kind of extraction.
To put the scale in perspective: the attacker executed 127 separate borrow-and-liquidate cycles before the drain was complete. In plain words, the protocol's own liquidation mechanics were turned into the extraction tool.
Where did the stolen funds go?
On-chain data show approximately 49.2 million KAVA crossed to BNB Chain through LayerZero. The majority was then exchanged for 3,006.5 BNB and 231,557 USDT, together worth approximately $2.09 million at the time.
That figure exceeds Kava's $1.83 million valuation of the stolen tokens. The discrepancy reflects different measurement points rather than any additional loss, but Kava has not fully reconciled the two numbers in its public statements.
Kava said the exploit created no additional KAVA and left individual users' deposits largely unaffected. The word "largely" is doing considerable work in that sentence; the project did not quantify any residual user impact.
What is Kava's response?
The project said it has repaired the vulnerability and frozen a portion of the stolen funds. It did not specify how large that portion is. Efforts to trace the remaining funds are underway in collaboration with exchanges and law enforcement agencies, though no agency names or jurisdictions were disclosed.
The governance response goes beyond patching the accounting flaw. Kava's planned proposal would permanently end new lending on Kava Lend entirely, subject to the seven-day vote.
A permanent shutdown, if passed, would represent a structural retreat: the protocol would wind down one of its core functions rather than attempt to restore confidence in it. Whether voters treat that as prudence or as an admission of deeper design problems remains to be seen.
The seven-day governance window now determines the protocol's lending future. Until the vote concludes, new lending continues to operate on the same codebase that Kava has already patched once.
via en.cryptonomist.ch (Source)
More from Elena Vasquez
Show full bio
Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.
1,525 articles