Kava says a security incident on 14 November took approximately 53.9 million KAVA from HARD Lend, its decentralised lending application. In an incident report dated 16 November, the HARD Lend Incident Response Team said the attacker “exploited a lending-accounting vulnerability that inflated the value of BUSD collateral, enabling repeated borrowing and liquidation transactions to withdraw existing KAVA from the lending pool.” “The identified exploit has been blocked,” the report said, “and measures preventing its repetition are in force.”
Kava’s official account, @KAVA_CHAIN, posted the report at 09:52 GMT on 16 November, writing that “the identified exploit has been blocked” and that “Kava Chain’s underlying security was not compromised.”
What Kava says was taken, and what happened next
The official figures are specific. Approximately 53.9 million KAVA was taken from the lending application. Approximately 49.2 million KAVA was subsequently bridged to BNB Chain via LayerZero. The report said the incident was confined to HARD Lend, that the exploit “did not create new KAVA tokens,” and that “individual user deposits were largely unaffected.”
Kava gave no dollar value. The Block, in a 14 November article by Zack Abrams based on on-chain data reviewed before the official report, put the tokens taken at about 55.2 million KAVA, “worth roughly $3.76 million at pre-attack prices.” That dollar conversion, and the 55.2 million figure, are The Block’s, not Kava’s. The Block also reported that the roughly 49.2 million KAVA later confirmed by Kava as having been bridged was sold for roughly $2.1 million in BNB and USDT. Kava’s 16 November report does not state a sale total.
The project said “a portion of the attacker’s funds has already been frozen,” and that work with ecosystem contributors, partners, exchanges and law enforcement was continuing to trace and freeze the remaining proceeds and to pursue recovery. It published three principal addresses identified in the exploit and the subsequent movement of funds: two on Kava (kava1uzx5924cqsutcw365ajs8kkc3rr4vtlyzms255 and kava1v2s266sll8ca5xrs06swmsc00nwwt7u77eufk4) and one on BNB Chain (0x37d732914f86cc6eb1e87419e3046a739f011042). It did not say how much of the 53.9 million had been frozen.
A vote to turn lending off
Protective measures, the report said, now prevent the attacker from repeating the identified exploit or continuing to drain funds through it. The planned retirement of HARD Lend’s legacy lending functionality is “being accelerated.” A governance proposal “will be submitted to permanently disable new lending and borrowing through the required seven-day voting process.” Those protective measures, it said, remain in force throughout that process. Remaining positions will be addressed “through an orderly process,” with further guidance to be given to users.
The measures are specific to HARD Lend. “Kava Chain and the broader Kava ecosystem remain active,” the report said, with continued network operations and activity across other applications. Further updates were promised as governance progresses and additional recovery milestones are confirmed.
DeFi lending and vault incidents have been a regular TSN file this autumn, including Swell’s pause of swETH and rswETH after a suspected hot-key compromise, an attacker draining 8.6 BTC from a Troves vault through a retired contract, and a $1.01 million USDC drain from a Tranche vault on Avalanche. Those are neighbouring exploit cases, not this BUSD-collateral incident.
An official token total is not a closed recovery
The cleanest reading of the 16 November report is as a first official account, not a completed one. Kava has now put its own number on the tokens taken — approximately 53.9 million KAVA — and has described the route: a BUSD collateral-accounting flaw, repeated borrow-and-liquidation transactions, and about 49.2 million KAVA bridged to BNB Chain via LayerZero. It has also said the chain itself was not compromised, that no new KAVA was minted, and that individual user deposits were “largely unaffected.” Those last points are the project’s. “Largely unaffected” is not a line-by-line statement that every depositor is whole, and the report promises further guidance on remaining positions rather than giving it now.
The same caution applies to the money. Kava published no dollar figure. The Block’s roughly $3.76 million conversion sits on its own earlier on-chain reading of about 55.2 million KAVA, made on 14 November at a pre-attack price of $0.068, before the official 53.9 million total existed. Treating that dollar figure as a conversion of Kava’s later official count would mix two different tallies. The frozen portion is likewise unquantified: “a portion” has been frozen, recovery work continues, and no recovered total is given.
The governance step is also still ahead. A proposal will be submitted, through a required seven-day vote, to disable new lending and borrowing permanently. That is a plan, not a passed decision, and the report is clear that protective measures stay in place while the vote runs. Until that vote concludes, and until Kava or law enforcement states how much of the 53.9 million has been frozen or returned, the documented record is the official token count, the BUSD accounting flaw, the LayerZero bridge, and a lending market that the project now wants to switch off for good.
Sources
- HARD Lend Incident Response Team, “HARD Lend Security Incident,” 16 November 2026
- Kava (@KAVA_CHAIN), post linking the incident report, 09:52 GMT, 16 November 2026
- Zack Abrams, The Block, “Kava Lend loses roughly $3.8 million to hack, sending KAVA token down nearly 40%,” 14 November 2026
Get TSN’s biggest tech stories, explained.
News and insights across AI, tech, crypto and cybersecurity. Every source linked. Unsubscribe anytime.
Get the newsletterRelated stories
- Swell Pauses swETH and rswETH After Suspected Hot-Key Compromise is the closest earlier TSN neighbour in this autumn’s DeFi-exploit file, and the right next stop for how another lending-related project handled a pause.
- Troves Says Retired Contract Let Attacker Drain 8.6 BTC From Vault
- Attacker Drains $1.01m in USDC From a Tranche Vault on Avalanche
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X