0x2eac7b482eac…2eac7b4b

ConfirmedSecurity505 vB162 sat/vB3 min decode

Kava Lend Exploit Drained 55.2M KAVA via Inflated Collateral Bug

An attacker drained 55.2M KAVA from Kava Lend by inflating BUSD collateral 243,000-fold and repeating the borrow cycle 127 times, leaving the pool nearly empty.

Kava Lend Exploit Drains Millions as KAVA Falls 47%
WitnessKava Lend Exploit Drains Millions as KAVA Falls 47%Mohamed_hassan / pixabay

Outputs

  1. Attacker gross-borrowed 55.2M KAVA and kept ~53.9M (~$3.7M) after repayments, per Bitquery

  2. Interest-calculation flaw inflated BUSD collateral ~243,000-fold; cycle repeated 127 times

  3. Pool held 0.19 KAVA against ~55.2M owed to lenders as of Nov. 14, per Bitquery snapshot

  4. ~49.2M KAVA bridged to BNB Chain via LayerZero and mostly sold for ~$2.1M, per The Block

  5. Upbit, Bithumb and Coinone froze KAVA transfers; Kava paused Axelar withdrawals at 9:05 a.m. ET Nov. 14

An attacker extracted roughly 55.2 million KAVA from Kava Lend by exploiting an interest-calculation flaw that inflated the value of collateral deposits about 243,000-fold, according to blockchain data provider Bitquery and an analysis by The Block. Kava has called the incident "isolated and contained within Kava Lend" and "not an infinite mint," but that distinction offers lenders little comfort: their deposits funded the attack and the pool is now effectively empty.

How did the exploit work?

Kava Lend lets users deposit assets to earn interest and borrow against collateral. The attacker pushed the BUSD market's net supply close to zero, which caused the protocol's interest calculation to inflate deposit values roughly 243,000-fold. Kava's public source code divides newly earned interest by cash plus outstanding loans minus reserves. It skips that division only when the denominator is exactly zero — not when it is a tiny positive number. That gap let the attacker turn a near-empty market into oversized collateral.

The attacker then used the inflated collateral to borrow KAVA repeatedly. Bitquery's investigation described a second component: a helper wallet borrowed KAVA, and liquidations closed its loans even though almost no BUSD remained to cover them. Each liquidation reopened room under the borrowing cap, allowing the cycle to repeat 127 times.

Bitquery put gross borrowing at 55.2 million KAVA. After repaying other borrowers' loans, the two wallets kept about 53.9 million KAVA — roughly $3.7 million at the pre-sale price. The firm's analysis found existing pool assets funded the attack, consistent with Kava's characterization of the incident as "not an infinite mint."

The Block reported that roughly 49.2 million KAVA crossed to BNB Chain through LayerZero, where most of it was sold for about $2.1 million. That bridge was separate from Axelar, whose withdrawals Kava paused afterward.

What happens to lenders?

The damage is a liquidity shortfall, not just a falling token price. Bitquery said the pool owed lenders about 55.2 million KAVA but held only 0.19 KAVA when it checked on Nov. 14. It also warned that the attacker's inflated BUSD claim remained outstanding, meaning subsequent BUSD deposits could be withdrawn by that wallet. Those findings reflect a snapshot, not a completed incident report from Kava.

Which transfers are frozen?

Upbit suspended KAVA deposits and withdrawals on Nov. 14, citing signs of a security incident, and separately issued a trading caution over heightened volatility. Bithumb's suspension took effect at 5:35 a.m. ET that day, followed by Coinone's at 5:40 a.m. ET. Bithumb said trading would remain available during the transfer freeze; Coinone said other services were unaffected unless separately announced.

At 9:05 a.m. ET, Kava announced that cross-chain asset withdrawals through Axelar were paused as a precaution. The team said it will publish a complete incident report once it is ready — a document lenders will scrutinize for a recovery plan covering the missing 55 million KAVA.

via cryptonews.net (Source)

More from Daniel Okafor

Daniel Okafor

Show full bio

Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.

1,221 articles