---
title: Kava's HARD Lend incident report: an accounting flaw that inflated BUSD collateral let an attacker drain about 53.9M KAVA; lending and borrowing will be permanently disabled | ctxsec
url: https://ctxsec.com/items/kava-hard-lend-incident-report-53-9m-kava-bust-collateral-accounting-flaw-lending-to-be-disabled
description: "Kava published its incident report on the Nov 14 HARD Lend exploit. It says an attacker exploited a lending-accounting vulnerability that inflated the value of BUSD collateral, then used repeated borrowing and liquidation transactions to withdraw about 53.9 million existing KAVA from the lending pool; about 49.2 million KAVA was bridged to BNB Chain via LayerZero. Kava says the exploit is blocked, no new KAVA was minted, Kava Chain's underlying security was not compromised and individual user deposits were largely unaffected. Part of the stolen funds has been frozen, and tracing continues with exchanges and law enforcement. On November 16, proposal 223 opened a seven-day vote (through November 23) to set every Lend borrow cap to zero and restore the $10 minimum borrow so existing borrowers can make partial repayments; proposal 224 would restore some Stability Committee permissions on Lend markets. Kava's official taken-funds figure remains 53.9 million KAVA. A 55.2 million figure circulated in press coverage from Bitquery's reconstruction of gross borrowing; that is not the number in Kava's report."
status: "official (Kava HARD Lend incident report, Nov 16, 2026; on-chain proposals 223 and 224); USD value and the 55.2M figure are not from Kava, last updated Nov 19, 2026, 12:45 PM ET"
published: 2026-11-16
updated: 2026-11-19T12:45:00-05:00
---

> Kava published its incident report on the Nov 14 HARD Lend exploit. It says an attacker exploited a lending-accounting vulnerability that inflated the value of BUSD collateral, then used repeated borrowing and liquidation transactions to withdraw about 53.9 million existing KAVA from the lending pool; about 49.2 million KAVA was bridged to BNB Chain via LayerZero. Kava says the exploit is blocked, no new KAVA was minted, Kava Chain's underlying security was not compromised and individual user deposits were largely unaffected. Part of the stolen funds has been frozen, and tracing continues with exchanges and law enforcement. On November 16, proposal 223 opened a seven-day vote (through November 23) to set every Lend borrow cap to zero and restore the $10 minimum borrow so existing borrowers can make partial repayments; proposal 224 would restore some Stability Committee permissions on Lend markets. Kava's official taken-funds figure remains 53.9 million KAVA. A 55.2 million figure circulated in press coverage from Bitquery's reconstruction of gross borrowing; that is not the number in Kava's report.

[← Cybersecurity News](/news) · [markdown](/items/kava-hard-lend-incident-report-53-9m-kava-bust-collateral-accounting-flaw-lending-to-be-disabled.md)

official (Kava HARD Lend incident report, Nov 16, 2026; on-chain proposals 223 and 224); USD value and the 55.2M figure are not from Kava

2026-11-16 7:34 AM ET · updated

Nov 19, 2026, 12:45 PM ET

### Kava's HARD Lend incident report: an accounting flaw that inflated BUSD collateral let an attacker drain about 53.9M KAVA; lending and borrowing will be permanently disabled

- **Governance:** proposal 223 (freeze borrowing, restore the $10 minimum) and proposal 224 (Stability Committee Lend permissions) are on-chain votes closing November 23, 2026 at 19:29 UTC and 20:13 UTC respectively. Delegators who do not vote inherit their validator's vote.
- **Attacker addresses (per Kava):** `kava1uzx5924cqsutcw365ajs8kkc3rr4vtlyzms255`, `kava1v2s266sll8ca5xrs06swmsc00nwwt7u77eufk4`, BNB Chain `0x37d732914f86cc6eb1e87419e3046a739f011042`.
- **HARD Lend users:** wait for Kava's guidance on remaining positions; the protocol is being wound down, not relaunched.
- **Still not disclosed by Kava:** the exact accounting bug, how much has been frozen, and a dollar figure. Press estimates of about $3.8 million are not from Kava's report.

Sources: [Kava (HARD Lend Incident Response Team): HARD Lend Security Incident report (Nov 16, 2026)](https://medium.com/@Kava_Chain/hard-lend-security-incident-579888f8dd73) · [Kava on X: public incident report available (Nov 16, 2026)](https://x.com/KAVA_CHAIN/status/2122266605677580750) · [Kava on X: not an infinite mint, isolated to Kava Lend (Nov 14, 2026)](https://x.com/KAVA_CHAIN/status/2121574325765476462) · [Kava governance proposal 223: Freeze Kava Lend Borrowing and Restore the USD 10 Minimum (voting Nov 16–23, 2026)](https://www.mintscan.io/kava/proposals/223) · [Kava governance proposal 224: Restore Kava Stability Committee Lend Risk Permissions (voting Nov 16–23, 2026)](https://www.mintscan.io/kava/proposals/224)
