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 Chain0x37d732914f86cc6eb1e87419e3046a739f011042. - 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) · Kava on X: public incident report available (Nov 16, 2026) · Kava on X: not an infinite mint, isolated to Kava Lend (Nov 14, 2026) · Kava governance proposal 223: Freeze Kava Lend Borrowing and Restore the USD 10 Minimum (voting Nov 16–23, 2026) · Kava governance proposal 224: Restore Kava Stability Committee Lend Risk Permissions (voting Nov 16–23, 2026)