KAVA token sinks 40% as exploit hits Kava Lend, exchanges halt withdrawals

54Importance
updatingStatus
4News media
Published
Updated

Kava Lend was hit by an exploit that moved tens of millions of KAVA, and several exchanges paused KAVA activity after the incident. The new coverage adds that the attack used inflated BUSD collateral to borrow KAVA, and one report says about 49.2 million KAVA was bridged to BNB Chain through LayerZero and sold for roughly $2.1 million in BNB and USDT.

Key claims & sources

✓
Kava Lend was hit by an exploit, and exchanges halted KAVA withdrawals after the incident.
✓
Kava said it was investigating suspicious on-chain activity as exchanges suspended KAVA transfers.
✓
About 49.2 million KAVA was bridged to BNB Chain through LayerZero and sold for roughly $2.1 million in BNB and USDT.
✓
Inflated BUSD collateral let attackers borrow 55.2 million KAVA, and bridge withdrawals and transfers at three Korean exchanges were suspended.
✓
The exploit drained roughly 55 million KAVA tokens from Kava Lend.

What it means

Kava Lend sits on Kava Chain, a Cosmos-based layer-1 with an Ethereum co-chain, and lets users borrow against deposited collateral including BUSD, the stablecoin Paxos stopped minting in February 2023 but which still circulates and still gets priced by lending protocols. Cross-chain transfers of KAVA out of the ecosystem ran through LayerZero, the messaging layer used by dozens of chains including BNB Chain, which is how the stolen tokens left before exchanges could react.

Three Korean exchanges suspended KAVA transfers and bridge withdrawals, meaning holders on those platforms could not move or sell tokens while the token's price fell as much as 47%. Kava Lend borrowers and depositors face a protocol with a confirmed hole of roughly 55 million tokens, and anyone who bridged KAVA to BNB Chain is now trading against a market that already absorbed millions of dollars of attacker-sold supply before the freeze took hold.

The exploit did not rely on a bridge hack or a minting bug; it used inflated BUSD collateral to borrow far more KAVA than the collateral was worth, exposing a gap between what an oracle reports and what a deprecated stablecoin is actually worth on-chain. That is a structural risk across DeFi lending markets, not a one-off bug, and it argues for collateral accounting that revalues legacy or thinly traded assets rather than trusting a static price feed.

Kava's own investigation into the attacker's wallets and the roughly $2.1 million converted into BNB and USDT will determine whether any funds can be frozen or clawed back, and whether exchanges restore KAVA withdrawals once they are satisfied the exploit path is closed. A protocol patch to how Kava Lend prices BUSD-style collateral, and any disclosure of exactly how the 55.2 million KAVA borrow was approved, will settle whether this was contained to one market or signals a wider lending-market flaw.

Market reaction i

KavaKAVA it is the asset of the company or protocol in the event

Kava fell 8.9% in the 4 hours after the first headline, after rising 9.9% in the 2 hours before.

$0.0421 price at the headline
+9.9% 2 h before
-8.9% 4 h after
-15.9% 12 h after
First headline

47 prices, one every 30 minutes · The move was larger before the first headline than after: an observation, not an explanation. The market also moves on things nobody publishes.

Coverage timeline

Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.

first
Nov 14 14:35
+5 min
Nov 14 14:40
Crypto Briefing echo
No new facts: investigates, emphasizing, suspicious
+8 h 32 m
Nov 14 23:07
+9 h 47 m
Nov 15 00:21
The Defiant context
Its angle: suspended, attackers, inflated
+1 d 7 h
Nov 15 22:00
NewsBTC context
Its angle: vulnerability, approximately, highlighting; with quotes

Thefts of a similar size

WhenWhat happenedFigure
2 months ago NEAR Intents · Bridge Logic Flaw incident $3.8M
2.1 years ago Onyx · Contract vulnerability incident $3.8M
3.6 years ago Rocket Pool · Phishing incident $3.8M
4.4 years ago XCarnival · Deposit Logic Flaw incident $3.8M
5.7 years ago DODO AMM · Improper access control incident $3.8M

4316 incidents stored · 570 were as large as this one or larger ($3.8M)