Deep Web3

SYSTEMS.
PEOPLE.
POSSIBILITIES.

Menu

Go beneath
the surface.

HARD Lend exploit: reported KAVA losses and a proposed lending shutdown

In a report published on November 16, 2026, at 19:37 UTC+8, TechFlow said an attacker had removed approximately 53.9 million KAVA, worth about $1.83 million, from HARD Lend, a lending application on Kava Chain. Kava’s response included a proposal to permanently stop new lending on the application; the shutdown had not been approved at the time of the report.

Reported failure and fund movements

Citing Kava’s security update, TechFlow attributed the exploit to an accounting flaw in HARD Lend’s dormant BUSD collateral market. The attacker allegedly inflated the recorded value of BUSD collateral, then repeated borrowing and liquidation transactions to drain available liquidity from an older lending pool.

TechFlow reported that on-chain data showed approximately 49.2 million of the affected KAVA—91.28% of the reported total—moved to BNB Chain through LayerZero and was sold. The report did not provide a transaction-level analysis or a separate valuation method. It said some funds had been frozen at centralized exchanges and bridge endpoints as of November 16, while Kava contributors were working with security teams, trading platforms and law enforcement to trace the remaining funds.

Scope and proposed response

According to Kava’s account as relayed by TechFlow, the incident was confined to HARD Lend’s application-level contracts. Kava said its consensus and network infrastructure were unaffected, no unauthorized tokens were minted at the protocol level, and validator block production and cross-chain communication continued. Those statements describe Kava’s assessment of the incident’s scope, not an independent verification of every other application or user balance.

Kava initiated a seven-day community governance vote. If approved, the proposal would permanently close HARD Lend to new borrowing and lending, with existing positions wound down in stages under redemption guidance. The report did not establish that the vote had passed or that the proposed shutdown had taken effect.