Hack Database

Kava: A Missing Zero Check Let One Attacker Drain $3.76M From Its Lending Pool

An attacker drained 55.2 million KAVA, about $3.76 million, from Kava Lend through a nearly empty market. The token fell 63% and Kava has not said if lenders get repaid.

Kava: A Missing Zero Check Let One Attacker Drain $3.76M From Its Lending PoolLogo: Kava
Kava, whose lending service lost almost all its KAVA in about 90 minutes.

Key numbers

  • $3.76M

    Drained

  • -63%

    KAVA fall, pre-attack to low

  • 127

    Borrowings

  • ~$2.09M

    Sold on BNB Chain

At 11:01 on the night of Friday 13 November 2026, New York time, an attacker began emptying Kava Lend, the lending service on the Kava blockchain. About 90 minutes later the pool that held its KAVA coins had fallen from 55.33 million KAVA to 0.19 KAVA, according to The Block. The coins taken were worth about $3.76 million at the price before the attack, $0.068 each. Kava said nothing publicly for more than seven hours.

Kava is a blockchain, a shared public ledger that no single company runs, with its own coin, KAVA. According to CoinGecko its price peaked at $9.12 on 30 August 2021. Kava Lend works like a savings and loan desk built from code. Savers put coins into a shared pool and earn interest. Borrowers take coins out of the pool, but first they must leave other coins as collateral, the way a homeowner pledges a house against a mortgage. If the collateral is worth enough, the code lets the loan go through. Nobody checks by hand.

How it worked

Hourly KAVA price on Binance, falling from $0.068 to about $0.03 after the attackChart: CMZ, data from Binance
KAVA price, hourly, Binance

Kava Lend keeps a separate pool, called a market, for each coin. One of them held BUSD, a token meant to be worth one dollar. That market was nearly empty. The Block's reading of Kava's public code explains the flaw. The code works out interest by dividing by the market's net supply, the total deposited minus the total borrowed. To avoid dividing by zero it skips the sum when net supply is exactly zero. It did not skip the sum when net supply was a tiny number above zero.

At 11:01 pm ET, a small BUSD loan left net supply at a tiny positive amount. Within three minutes, deposit values in that market had risen about 243,000 times, so that roughly 1.25 billion BUSD of collateral appeared on the books. In stock-market terms, it is as if a broker's system valued a few pennies of shares at a billion dollars because of an arithmetic slip. The attacker then used that fake collateral to borrow KAVA from the pool 127 times. A second account cleared each loan so that a cap on KAVA borrowing was never hit, The Block reported.

The attacker did not need a password or a private key. Everything used the lending service as designed. The Block also reported repeated deposit and borrow cycles from 8 November onward, which suggests at least a week of preparation. Nobody has been named.

Where the money went

About 49.2 million of the stolen KAVA was sent at 4:59 am ET on Saturday to BNB Chain, a separate blockchain tied to the exchange Binance, through a bridge called LayerZero. A bridge moves coins from one blockchain to another. Most of it was sold within an hour for 3,006.5 BNB and 231,557 USDT, together about $2.09 million, because BNB Chain has far more buyers than Kava does. The BNB has since been moved. Another 4.58 million KAVA went to five unlabeled addresses on Kava. The Block's figure for the whole haul is 55.2 million KAVA. Bitquery, a blockchain data company, put the two attacker wallets' net take at 53.9 million KAVA, about $3.7 million.

The market reaction

The sale hit a thin market. Binance's public price data shows KAVA at $0.0683 in the hour that began at 04:00 UTC on 14 November, just before the attack. In the hour that began at 11:00 UTC it traded as low as $0.03355. It reached its low of $0.02507 in the hour starting 22:00 UTC. The latest reading, the close of the hour starting 19:00 UTC on 15 November, is $0.03059. That is 63% below the pre-attack price at the low and 55% below at the latest reading.

South Korean exchanges, where KAVA trades heavily, reacted fast. According to Cryptonews, Upbit suspended KAVA deposits and withdrawals on 14 November, citing signs of a security incident, and issued a separate trading caution for volatility. Bithumb and Coinone also halted transfers. Trading itself stayed open on Bithumb.

What Kava said

Kava's first post came on X at 11:28 UTC on 14 November, about seven hours after the attack began. It said the team was tracking "unexpected behavior originating from a dApp within the Kava ecosystem". A dApp is an app that runs on a blockchain. At 12:01 UTC a second post said: "This is not an infinite mint. The event is isolated and contained within Kava Lend." An infinite mint would mean the attacker could print new KAVA at will, which would be far worse. Kava also said partner exchanges had paused deposits and withdrawals "as a standard precautionary measure".

At 14:05 UTC, Kava paused its Axelar bridge, another cross-chain link, "out of an abundance of caution". The stolen coins left through LayerZero, not Axelar, so the pause was a safety step. Kava promised "a complete incident report as soon as it is ready".

Open questions

Bitquery found the lending pool owed savers about 55.2 million KAVA but held 0.19 KAVA, so anyone who deposited KAVA cannot get it back unless Kava acts. It also found the attacker's inflated BUSD claim was still outstanding, meaning later BUSD deposits could be withdrawn by that wallet. No source reports damage to deposits in other Kava Lend markets, but Kava has not confirmed that either.

Kava has not published an official loss figure or a post-mortem, and has not said whether it will repay savers. The Block notes the loss follows others at lending services this year, including about $75 million at Tectonic on Cronos in August and about $9 million at Hedera's Bonzo Lend in July.

The aftermath

As of 15 November, Kava had not published its incident report, an official loss figure or a repayment plan. KAVA traded near $0.031 on Binance, less than half its pre-attack price. Upbit's deposit and withdrawal freeze was announced on 14 November, and no notice that it had been lifted was found.

What this teaches

  • A check that guards against exactly zero does not guard against almost zero. Dormant, nearly empty markets need the same tests as busy ones.
  • Lending code that trusts the value of a thin market can be tricked into valuing a few pennies of deposits at billions.
  • Selling stolen coins on a bigger network, as here with BNB Chain, drags the victim's own price down.