IPCRIME NEWSROOM | NOVEMBER 16, 2026
Kava’s November 16 response to a November 14 decentralized-finance attack says approximately 53.9 million KAVA tokens were removed from its HARD Lend lending application. The project says it blocked the identified accounting vulnerability and intends to propose permanently disabling new lending and borrowing. The security of the underlying Kava blockchain was not compromised, according to its statement.
The accounting weakness
The HARD Lend Incident Response Team says the attacker exploited incorrect lending-account accounting that inflated the value attributed to BUSD collateral. Repeated borrowing and liquidation transactions then withdrew existing KAVA from the lending pool. This is a flaw in application logic as described by the project’s report, not a claim that an attacker generated tokens out of thin air.
What happened to the tokens
Kava states that about 49.2 million of the removed KAVA were moved to BNB Chain using LayerZero. It says a portion of the funds was frozen with assistance from ecosystem partners and trading platforms, but has not given a verified recovered total. Dollar estimates in market reporting vary with timing and token price, so IPCRIME is reporting the project’s token count rather than treating a changing dollar equivalent as fixed.
Plans for the lending product
The project says it is accelerating the retirement of HARD Lend’s existing lending function. A governance proposal is to seek permanent closure of new lending and borrowing through a required seven-day vote. This is a proposed decision, not an already-approved governance outcome. Existing positions are to be handled separately, with further user guidance promised.
What users should know
Kava says the incident was confined to HARD Lend, that no new KAVA tokens were created and that individual user deposits were largely unaffected. That does not establish that every lender’s position is fully settled. Users should follow direct project announcements and confirmed governance notices, avoid unsolicited ‘recovery’ links and independently verify any request for wallet approval or signing.
Source documents and reporting
- Kava incident response as reported November 16
- CryptoSlate follow-up, November 16
- Earlier on-chain reporting by The Block, November 14
IPCRIME identifies confirmed company or agency disclosures separately from outside reporting and attacker claims. This article was prepared November 16, 2026; the original incident or disclosure may be earlier.