Kava Lend Loses $3.8 Million in DeFi Exploit as Dormant BUSD Market Exposes Accounting Flaw

0
2

Kava’s decentralised finance ecosystem is facing renewed scrutiny after an attacker extracted approximately 53.9 million KAVA tokens from its HARD Lend application on November 14. The incident, initially estimated at $3.76 million, exposed a critical weakness in the protocol’s collateral accounting: an almost inactive BUSD lending market allowed the attacker to artificially inflate deposited collateral and repeatedly borrow assets from the lending pool.

The exploit did not compromise the underlying Kava blockchain or involve the creation of new tokens. Instead, it drained existing KAVA held by the lending application. Kava’s November 16 incident report confirmed that the vulnerability had been blocked and that protective measures were in place. However, questions remain over fund recovery and the future of HARD Lend.

The attack centred on HARD Lend’s BUSD market. BUSD, the stablecoin issued by Paxos, had become largely inactive after Paxos announced in February 2023 that it would stop minting new tokens. Despite the decline in usage, the lending market remained operational.

According to on-chain analysis by The Block and blockchain intelligence firm Bitquery, the attacker manipulated the market’s accounting conditions until its effective net supply became extremely small. Kava Lend’s interest-index calculation divided accrued interest by net market supply. Although the code accounted for a supply value of exactly zero, it did not adequately protect against an extremely small positive value.

The result was dramatic: the market’s supply interest index increased approximately 243,000-fold in around three minutes. Deposits controlled by the attacker were consequently assigned an enormous artificial value, allowing them to be used as collateral for borrowing KAVA.

The attacker then executed a series of borrowing and liquidation transactions. Bitquery identified 127 borrowing rounds conducted through two wallets over approximately 98 minutes. The repeated transactions enabled the attacker to extract liquidity while circumventing the protocol’s borrowing limits.

The distinction between the gross borrowing activity and the final amount retained is important. On-chain analysis initially identified approximately 55.2 million KAVA borrowed, worth around $3.76 million at pre-attack prices. After accounting for repayments, the attacker retained approximately 53.9 million KAVA — the figure subsequently confirmed by Kava’s incident report.

Following the exploit, approximately 49.2 million KAVA was transferred to BNB Chain through LayerZero. The Block reported that the attacker sold most of the bridged tokens for approximately $2.09 million in BNB and USDT.

The difference between the estimated pre-attack value and the sale proceeds reflects the market impact of the transactions and the subsequent decline in KAVA’s price. The token fell sharply following the incident, losing close to 40% over a 24-hour period in The Block’s initial reporting.

There have also been some indications of potential recovery. Bitquery identified approximately $612,000 in USDT proceeds blocked by the Relay bridge. However, blocked funds should not be treated as recovered assets: there has been no confirmation that this amount has been returned to the protocol or affected lenders.

Kava said a portion of the attacker’s funds had been frozen and that it was working with ecosystem partners, exchanges and law enforcement to trace and recover the remaining proceeds. The team has not disclosed the total amount frozen or recovered.

Kava has stated that the exploit was isolated to HARD Lend and that the underlying blockchain infrastructure remains secure. Its incident report also said individual user deposits were largely unaffected, although it did not provide a detailed reconciliation of lender balances or explain how any outstanding losses would be addressed.

The project is accelerating the retirement of HARD Lend’s legacy lending functionality. A governance proposal, numbered 223, went live on November 16. It seeks to set borrowing limits to zero across the application while restoring the minimum borrowing threshold, effectively preventing new borrowing while allowing existing borrowers to repay. The voting period is scheduled to end on November 23.

The proposal is an important immediate containment measure, but it is not the same as a completed recovery or a final shutdown of every lending function. Kava has said remaining positions will be handled through an orderly process, with further guidance to users.

The Kava incident highlights a recurring weakness in DeFi risk management: markets can remain technically active long after their underlying assets have lost meaningful liquidity and usage.

Dormant markets may receive less monitoring than heavily used pools, yet their accounting mechanisms can still influence collateral valuations and borrowing capacity. The exploit demonstrates why protocols need safeguards not only against zero liquidity, but also against extreme values, rounding errors and abnormal changes in market indices.

For DeFi developers, the lesson extends beyond Kava. Lending systems need explicit liquidity thresholds, limits on index growth, robust validation of collateral calculations and mechanisms to automatically pause markets when accounting conditions become abnormal.

Kava has contained the identified vulnerability, but the longer-term consequences will depend on whether funds can be recovered, how remaining lender positions are resolved and whether governance approves the proposed withdrawal of HARD Lend’s borrowing functionality. The incident is another reminder that the security of a blockchain does not automatically guarantee the security of the applications built on top of it.

LEAVE A REPLY

Please enter your comment!
Please enter your name here