UPDATED 10:56 UTC, 17 Nov: The vote on proposal 223 is filling up. At about 10:47 UTC on 17 Nov, about 42.8 million KAVA had voted yes on the freeze of Kava Lend borrowing, with none against, abstaining or voting no with veto, up from 12.2 million at 04:45 UTC, according to the chain’s governance data. Voting ends at 18:29 UTC on 23 Nov. On proposal 224, which would add BitGo WBTC and Meson mBTC to the Kava Stability Committee’s lending risk permissions, about 19.2 million KAVA had voted yes and 20.9 million had abstained, with none against.
UPDATED 04:55 UTC, 17 Nov: A proposal to freeze Kava Lend borrowing went to a chain vote at 18:29 UTC on 16 Nov. Proposal 223, “Freeze Kava Lend Borrowing and Restore the USD 10 Minimum”, would set every Kava Lend borrowing cap to zero, blocking new borrowing while still allowing repayments. Voting ends at 18:29 UTC on 23 Nov. At 04:45 UTC on 17 Nov, about 12.2 million KAVA had voted yes and none against, according to the chain’s governance data. A separate proposal, 224, which Kava announced on X, would add BitGo WBTC and Meson mBTC to the Kava Stability Committee’s lending risk permissions.
SECURITY ALERT · UPDATE
Kava has put a number on it.
It sits close to the early on-chain estimates, and it is not small.
The chain said on X at 09:52 UTC on Monday that its public incident report on the 14 Nov HARD Lend incident was out. The report says about 53.9 million KAVA was taken from the lending application.
Kava’s earlier posts and our first report on the KAVA sell-off called the same market Kava Lend.
How did a market in wind-down get drained?
What Kava says happened
The attacker used a flaw in how the app does its lending accounting, the report says. It inflated the value of BUSD posted as collateral, which let the attacker borrow, liquidate and withdraw KAVA again and again from the lending pool.
About 49.2 million KAVA was then bridged to BNB Chain through LayerZero, a cross-chain messaging system.
Kava says no new KAVA was created, Kava Chain’s own security was not compromised, and individual user deposits were “largely unaffected”.
It says a portion of the attacker’s funds is frozen and that it is working with partners, exchanges and law enforcement to trace and freeze the rest. The report does not say how much is frozen, or where.
Who froze it?
How it compares with the early numbers
The Block counted about 55.2 million KAVA drained from on-chain data, worth about $3.76 million at the pre-attack price of $0.068. Crypto Briefing counted about 48.3 million KAVA crossing to BNB Chain.
Kava’s figures are about 53.9 million taken and about 49.2 million bridged.
The report gives no dollar value. At $0.068, 53.9 million KAVA would have been worth about $3.7 million, by our arithmetic. At CoinGecko’s $0.0338 at 10:50 UTC on Monday, it is about $1.8 million.
The token’s fall did that.
Which number do depositors care about?
The addresses Kava names
The report lists three addresses as the principal ones in the exploit and the movement of funds. We have not traced them.
kava1uzx5924cqsutcw365ajs8kkc3rr4vtlyzms255
kava1v2s266sll8ca5xrs06swmsc00nwwt7u77eufk4
BNB Chain: 0x37d732914f86cc6eb1e87419e3046a739f011042
The report says the investigation also seeks to identify those responsible. It names no one.
The market was already closing
Kava’s governance record shows the lending market was on its way out before the exploit. A chain vote, proposal 222, passed on 5 Oct. It ended incentives, stopped new borrowing in the chain’s minting system, set lending borrow limits “near outstanding balances” and told users to close positions before a later phase, according to the chain’s governance data.
Kava now says it is accelerating that retirement. It will submit a proposal to disable new lending and borrowing permanently, and it will go to a seven-day vote. Remaining positions will be handled in a separate “orderly process”, with guidance to come.
We found no such proposal on the chain at 10:55 UTC. The newest was still proposal 222.
If the market was nearly empty, why was there so much to take?
What we still don’t know
Kava has not said how a BUSD market came to carry weight in the collateral maths. It has not said whether depositors will be made whole.
It has not said whether the Axelar bridge pause or the exchange suspensions from Saturday have ended.
Protect yourself
- If you had KAVA in HARD Lend, wait for Kava’s own guidance on remaining positions. Do not follow links from direct messages offering recovery.
- Check any governance proposal on the chain itself before voting on it, not only in a post or a chat group.
- If you hold KAVA on an exchange, read that exchange’s notice before assuming deposits or withdrawals are open.
Corrections and new evidence: [email protected]
This article is for information only and is not investment advice.
