Kava moves to retire HARD Lend after exploit drains 53.9 million KAVA
In brief
- Attackers kept 53.9 million KAVA from HARD Lend after the Nov. 14 exploit, per Bitquery.
- Bitquery valued the stolen tokens at $3.7 million before the market selloff.
- Kava says it patched the accounting flaw and froze part of the attackers' funds.
- Governance proposal to disable new lending and borrowing still needs a seven-day vote.
How the exploit worked
Kava said the attackers manipulated the value of BUSD collateral inside HARD Lend. That let them repeatedly borrow KAVA and trigger liquidations that cleared their debts (without the borrowed tokens ever being recovered). Bitquery found they borrowed about 55.2 million KAVA across 127 transactions and kept 53.9 million after repayments involving other borrowers.
From there, about 49.2 million KAVA moved to BNB Chain through LayerZero. Bitquery traced the sale of 48.4 million KAVA, which brought in roughly $2.09 million in BNB and USDT. One payout didn't go through: the Relay bridge rejected a 612,416 USDT transfer with a BLOCKED_WALLET message, which stopped it from reaching Ethereum.
Kava says part of the attackers' funds has been frozen and it's working with exchanges, ecosystem partners and law enforcement to trace and recover the rest. It hasn't disclosed how much was secured, or whether the frozen funds include the USDT that Bitquery identified.
The liquidity gap lenders face
Bitquery's Nov. 14 reconstruction showed the lending pool owed users about 55.2 million KAVA while holding only 0.19 KAVA available for withdrawals. (The pool and bridge observations are dated Nov. 14; the Relay record was read at 16:20 UTC and the BNB Chain and Ethereum data end at 16:08 UTC.)
That's the number lenders should watch.
Withdrawals need usable KAVA in the pool, and blocking a bridge payout or reopening exchange transfers doesn't supply that liquidity by itself, as CryptoSlate's analysis noted. Kava said individual user deposits were largely unaffected, but it didn't explain how that assessment squares with outstanding lender claims or the depleted pool.
What happens next
“The planned retirement of HARD Lend's legacy lending functionality is being accelerated,” Kava said
A governance proposal would permanently disable new lending and borrowing, but it still has to pass a seven-day vote (existing protective measures stay in force in the meantime). Kava says it patched the vulnerability and added safeguards to prevent a repeat. It also said the breach was confined to HARD Lend and didn't compromise the underlying Kava blockchain or create additional tokens.
Remaining positions will be handled through an orderly process, according to Kava, and it's promised further guidance for affected users as the retirement goes ahead.
Frequently asked questions
How did attackers drain KAVA from HARD Lend?
Kava said the attackers manipulated the value of BUSD collateral within HARD Lend to repeatedly borrow KAVA. They then triggered liquidations that cleared their debts without the borrowed tokens being recovered. Bitquery found they borrowed about 55.2 million KAVA across 127 transactions and kept 53.9 million.
Why doesn't freezing the stolen funds let HARD Lend lenders withdraw?
Lender withdrawals need usable KAVA in the pool. Bitquery's Nov. 14 reconstruction showed the pool owed users about 55.2 million KAVA while holding only 0.19 KAVA. As CryptoSlate's analysis noted, blocking a bridge payout or reopening exchange transfers doesn't supply that liquidity by itself.
Is HARD Lend's shutdown final?
Not yet. Kava's governance proposal to permanently disable new lending and borrowing has to pass a seven-day vote, while existing protective measures stay in force. Kava said it would handle remaining positions through an orderly process.


