block #0051 in --:--:--Join the pool
PENDING…
hype projects ✓ confirmed 6/6 6d ago · 4 min read

kava lend hack: Attacker Drains 55.2M KAVA via Dead BUSD Market Bug

The kava lend hack let an attacker borrow about 55.2 million KAVA, worth roughly $3.76 million before the attack, by inflating a nearly empty BUSD market 243,000-fold and selling most of the loot on BNB Chain.

kava lend hack: Attacker Drains 55.2M KAVA via Dead BUSD Market Bug
tl;dr
  • About 49.2 million KAVA was bridged to BNB Chain and sold for roughly $2.1 million in BNB and USDT.
  • Kava said the event is "not an infinite mint" and is "isolated and contained within Kava Lend."
  • KAVA traded near $0.030 on Binance at 05:55 UTC on November 15, down about 56% in 24 hours.
in this block
  1. What actually happened
  2. Why the kava lend hack matters
  3. What to do as a reader

The kava lend hack drained almost every KAVA token from the chain's native lending app in about 98 minutes. An attacker borrowed roughly 55.2 million KAVA, worth about $3.76 million before the attack, after inflating the value of a nearly dead BUSD market, The Block reported.

What actually happened

According to The Block, the attack started late Friday, November 13, Eastern time, which was early Saturday in UTC. The target was Kava Lend's BUSD market. BUSD is the Binance-branded stablecoin that Paxos stopped minting in 2023, so the market was nearly empty.

Here is the bug in plain English. Kava Lend calculates what depositors earn by dividing interest by the market's net supply. The code skipped the math when supply was exactly zero, but did not guard against tiny numbers above zero. The attacker pushed supply down to two hundred-millionths of a dollar. Over three minutes, the protocol multiplied every BUSD deposit roughly 243,000-fold, and the attacker's own BUSD suddenly counted as about 1.25 billion BUSD in collateral.

The loop

The attacker then borrowed KAVA 127 times against that fake collateral, using a second account to clear each loan and dodge a borrowing cap. Bitquery, which reconstructed the transactions, said each loan was liquidated without recovering the borrowed KAVA, and the pool fell from about 55.3 million coins to almost nothing. The Block said the attacker had been testing the BUSD market since November 8.

Where the money went

Most of the tokens left through Kava's LayerZero bridge to BNB Chain. The Block said they sold for 3,006.5 BNB and 231,557 USDT, about $2.09 million. Bitquery said the Relay bridge blocked 612,416 USDT of the proceeds and that much of the rest ended up on Hyperliquid. Those are third-party onchain findings, not an official Kava report.

Why the kava lend hack matters

Dormant markets are an attack surface. A pool nobody uses still runs code, and an edge case in that code can price collateral at nonsense levels. The Block noted this follows other lending exploits this year where attackers borrowed against collateral worth far less than the protocol believed. We covered similar cracks in initia second exploit and keplr web3auth exploit.

The cheapest way to rob a bank is through the vault nobody checks anymore.

The exchange response

Kava first acknowledged "unexpected behavior" more than seven hours after the attack began, per The Block, and later paused its Axelar bridge. Korean exchanges Bithumb and Coinone suspended KAVA deposits and withdrawals while keeping trading open, according to Coinburn's review. Kava said it will "share a complete incident report as soon as it is ready," but had not published an official loss figure at the time of these reports.

The kava lend hack also hits KAVA holders who never used the app. Supply did not grow, but a large block of tokens hit the market at once, and the price fell from about $0.068 before the attack to around $0.03.

Timeline in UTC

  • November 8: The attacker starts running deposit and borrow cycles in the BUSD market, per The Block.
  • November 14, about 04:01: The attack begins as the attacker drains BUSD supply to a tiny number.
  • 04:04 to 05:42: Bitquery counts 127 KAVA loans in 98 minutes.
  • About 09:59: The attacker starts bridging KAVA to BNB Chain through LayerZero.
  • About 10:07 onward: One wallet sells 48.4 million KAVA in 46 transfers over 35 minutes, Bitquery says.
  • About 10:35: Bithumb suspends KAVA deposits and withdrawals; Coinone follows five minutes later.
  • About 11:28: Kava posts its first public acknowledgment on X.

The gap between the drain and the first official word is a big part of the story. Holders found out from onchain sleuths and exchange notices before hearing from the team.

What to do as a reader

The kava lend hack is still developing, so stick to official updates.

  1. Wait for the post-mortem. Loss numbers differ slightly between The Block, DefiLlama and Bitquery.
  2. Check your positions. If you supplied KAVA to Kava Lend, follow Kava's channels for any recovery plan.
  3. Ignore "refund" links. Hacks attract fake compensation sites and DMs.
  4. Watch exchange notices. Deposits and withdrawals may stay paused for days.
  5. Audit old markets. Builders should retire or patch idle pools, not just ignore them.

Nothing here is financial advice.

Not financial advice. DYOR, ser.

More in the pool

all hype projects
gm ser

Get confirmed before the crowd

Daily block at 07:00 UTC. No spam, just the block, ser.