Kava Lend Hack Drains $3.8M, KAVA Crashes 40% — Will Lenders Recover?

Kava Lend hack KAVA token crash red chart

A lending market nobody used any more just emptied Kava Lend. An attacker drained about 55.2 million KAVA, worth roughly $3.8 million, in about ninety minutes late on Friday, and the token fell close to 40% in a day. The pool that held lenders' KAVA went from 55.33 million tokens to 0.19 — and Kava took more than seven hours to say a word about it.

Key points:

  • An attacker used a dead BUSD market to inflate a deposit about 243,000 times, then borrowed KAVA against it 127 times.
  • Most of the stolen tokens were bridged to BNB Chain and sold for about $2.1 million within the hour.
  • Kava has not published an official loss figure or a post-mortem yet, and partner exchanges have paused KAVA deposits and withdrawals.

Kava Lend is the native lending protocol of Kava, a Layer 1 chain. The attack ran late on Friday, November 13, into Saturday morning, November 14. KAVA traded near $0.068 before the attack. By the time The Block published its story on Saturday evening, the token sat near $0.042, down about 39% in 24 hours. On Sunday evening, it still traded near $0.034, about half its pre-attack price. It came on a weekend when the whole market was already sliding: Bitcoin fell to a four-month low near $62,000, and the Fear & Greed Index sat at 10, deep in extreme fear.

How did a market nobody used drain $3.8 million?

The flaw sat in how Kava Lend works out what depositors have earned. It divides the interest borrowers pay by a market's net supply, and its public code skips that division only when the supply figure is exactly zero. It does not check for a figure that is tiny but still above zero. That gap was the whole attack.

At 11:01 p.m. ET on Friday, the attacker used a small BUSD loan to push the BUSD market's net supply down to two hundred-millionths of a dollar. Over the next three minutes, Kava Lend multiplied the value of every BUSD deposit roughly 243,000-fold. That included BUSD the attacker had put in ahead of time, which the protocol now counted as about $1.25 billion in collateral. The attacker then borrowed KAVA against that deposit 127 times, using a second account to clear each loan and get around Kava Lend's cap on KAVA borrowing. This was not a rushed job: Onchain data shows the attacker ran repeated deposit and borrow cycles in the BUSD market from November 8, at least a week of practice.

BUSD is the Binance-branded stablecoin that Paxos stopped minting in 2023, and its Kava Lend market was all but empty before the attack. That is the point. Nobody was watching it, nobody was using it, and the code that ran it had a hole in it for years.

Read also: Bitcoin Core High-Severity Bug Could Have Stopped Miners Building Blocks

Where did the stolen KAVA go?

Starting at 4:59 a.m. ET on Saturday, the attacker bridged about 49.2 million KAVA to BNB Chain through Kava's LayerZero bridge. Most of it was sold within the hour for 3,006.5 BNB and 231,557 USDT, worth about $2.09 million combined, and the BNB has since been moved out. About 4.58 million more KAVA went to five unlabeled addresses on Kava. Onchain data firm Bitquery put gross borrowing at 55.2 million KAVA, with the two wallets keeping 53.9 million after repaying other borrowers' loans. The pool owed lenders about 55.2 million KAVA while holding 0.19. One small win for the good side: About 612,416 USDT of the laundering proceeds was blocked at the Relay bridge.

Two numbers in this story are easy to mix up, so here they are plainly. The $3.8 million figure values the stolen tokens at the pre-attack price of $0.068. What the attacker actually took home was about $2.1 million, because selling 49 million KAVA in an hour crushed the price. The gap between those two numbers is the cost of the crash itself, and it is also why the $3.8 million should be read as an estimate from onchain data, not an audited fact: Kava has still not published its own loss figure.

The pattern is the warning

Kava's first public word came at 6:28 a.m. ET on Saturday, more than seven hours after the attack started. "We are tracking unexpected behavior originating from a dApp within the Kava ecosystem," the team wrote on X. About half an hour later came a follow-up: The team knew about "the bridging and sale of KAVA tokens on BSC" and added, "To clarify: This is not an infinite mint. The event is isolated and contained within Kava Lend." At 9:05 a.m. ET, Kava said it had paused the Axelar bridge "out of an abundance of caution" — though the drained KAVA had left through LayerZero, not Axelar. Partner exchanges paused KAVA deposits and withdrawals "as a standard precautionary measure," and Upbit, Bithumb, and Coinone suspended KAVA transfers.

The "not an infinite mint" line answers the first wrong guess most people make about a hack like this. No new KAVA was printed. The pool's own 55.33 million KAVA was borrowed out against collateral that did not exist. And this is the third lending protocol hit this year where an attacker borrowed against collateral worth far less than the protocol believed: Cronos halted its network in August after an exploit of lending protocol Tectonic put at $75 million, and Hedera's Bonzo Lend was hit for roughly $9 million in July. Each time, the weak spot was the same — a market the protocol had stopped watching.

What should KAVA holders watch next?

My own read is plain: A lending market with no users in it is not a quiet corner of a protocol, it is an open door, and Kava left this one open for years. The question now is what Kava does with the door.

First, the incident report Kava promised. When it lands, read two things in it: whether lenders get made whole, and whether the BUSD market and other near-empty markets get shut down for good. A report that only explains the bug and moves on is not enough. Second, the exchanges. Upbit, Bithumb, and Coinone paused KAVA transfers, and their reopening will be the first sign the market trusts the fix. Third, the price. Write down three numbers: $0.030, the low KAVA hit on Binance, down 56% from the pre-attack close; $0.042, where it traded when The Block's story went out; and $0.034, where it sat on Sunday evening. A move back above $0.042 with real volume would be the first sign buyers are stepping back in. A fresh low under $0.030 would say the selling is not done.

Until that report lands, KAVA is a token with a hole in its lending pool and no official number on the damage. That is not a setup to rush into.

Read also: How to Check If a Crypto Exchange Is Safe Before You Deposit

— Muhammad Irfan

About the author: Muhammad Irfan is the founder and editor of BitByLine. He writes crypto news and beginner guides in simple, everyday language, so readers without a finance background can follow along. Read more about the editor.

This post is news only, not financial advice. BitByLine never tells anyone to buy or sell crypto — that call is yours, and the risk is yours too. Always do your own research before you buy or sell.

Read our full Disclaimer.

Sources: The Block, Blockchain Academics, Coindaro, CoinGecko.

Comments