Daily news

Kava Lend Exploit Drains About 55 Million KAVA as Token Hits Record Low and Upbit Halts Transfers

About 55.2 million KAVA was drained from Kava Lend on November 14, 2026, according to on-chain analysis by Bitquery, which says attackers inflated the supply index of a nearly dead BUSD pool and borrowed KAVA in 127 loans that liquidations erased. Kava says the event is contained within Kava Lend and is not an infinite mint. KAVA fell to a record low, Upbit suspended deposits and withdrawals, and Kava paused the Axelar bridge. A full incident report has been promised.

MyTraderBot DeskPublished: 11 min readخواندن به فارسی
Share
The illuminated blue Upbit sign above the entrance of the exchange's office in Seoul at night, with MyTraderBot branding in the corner
Entrance of South Korean exchange Upbit in Seoul (2019). Upbit suspended KAVA transfers on Nov. 14. Photo: Altostratus / Wikimedia Commons, CC BY 4.0
Table of Contents

About 55.2 million KAVA was drained from Kava Lend, the lending app built into the Kava blockchain, early on November 14, 2026, according to on-chain analysis by blockchain data firm Bitquery. Most of the tokens were later bridged to BNB Chain and sold, and KAVA fell to a record low. South Korea's Upbit suspended KAVA deposits and withdrawals, and Bithumb and Coinone reportedly did the same.

The Kava team says the event is "isolated and contained within Kava Lend" and that it is "not an infinite mint," meaning no new KAVA was created. It has not yet explained the root cause or said how affected depositors will be treated. A complete incident report has been promised but had not been published at the time of writing (00:25 Tehran time, November 15).

All times below are given in UTC and in Tehran time (UTC+3:30).

What Kava has said officially

Kava has made three public statements on its official X account, @KAVA_CHAIN, all on November 14:

  • 11:28 UTC (14:58 Tehran): "We are tracking unexpected behavior originating from a dApp within the Kava ecosystem. Our teams are investigating with high priority - stand by for an official update shortly." (post)

  • 12:01 UTC (15:31 Tehran): "We are aware of recent on-chain activity involving the bridging and sale of KAVA tokens on BSC. To clarify: This is not an infinite mint. The event is isolated and contained within Kava Lend. Partner exchanges have paused deposits/withdrawals as a standard precautionary measure. More information to follow soon." (post)

  • 14:05 UTC (17:35 Tehran): "Out of an abundance of caution, the @Axelar bridge has been paused. As a result, cross-chain asset withdrawals through the Axelar bridge are currently paused. We will share a complete incident report as soon as it is ready." (post)

Kava has not said how much was lost, which code path failed, who carries the loss or whether depositors will be compensated. Everything about the mechanics below comes from independent on-chain analysis and should be read as such until Kava confirms or corrects it.

Timeline of November 14

The table combines Kava's posts, Upbit's notices and on-chain findings from Bitquery and Altcoin Reporter. On-chain items are those firms' readings of public data, not confirmed by Kava.

UTC

Tehran

Event

Source

04:00

07:30

All 37 open BUSD loans in Kava Lend are repaid by one wallet

Bitquery

04:01

07:31

BUSD pool's "money supplied" figure set to 2 base units; supply index starts to jump

Bitquery

04:04–05:42

07:34–09:12

127 KAVA loans totalling about 55.2 million KAVA; each loan erased by liquidation

Bitquery, Altcoin Reporter

06:10–10:06

09:40–13:36

About 4.4 million KAVA sent to exchange and swap-service deposit addresses

Bitquery

09:59 and 10:02

13:29 and 13:32

About 48.36 million KAVA sent into a cross-chain bridge to BNB Chain

Altcoin Reporter

10:07–10:42

13:37–14:12

48.4 million KAVA sold on BNB Chain for about $2.09 million

Bitquery

10:36

14:06

Upbit suspends KAVA deposits and withdrawals

Upbit notice

10:53

14:23

Relay bridge blocks a 612,416 USDT transfer from the seller

Bitquery

11:00

14:30

Upbit issues a trading caution notice for KAVA

Upbit notice

11:28

14:58

Kava's first public statement

Kava on X

11:57

15:27

KAVA hits a record low of about $0.0356

CoinGecko

12:01

15:31

Kava: "not an infinite mint," event contained within Kava Lend

Kava on X

12:05

15:35

Another 849,081 KAVA sent into the bridge

Altcoin Reporter

14:05

17:35

Kava pauses the Axelar bridge; incident report promised

Kava on X

How the exploit worked, according to Bitquery

Bitquery published a detailed investigation on November 14, based on Kava node data read up to about 16:20 UTC (19:50 Tehran). Its central finding is that the attackers did not break the KAVA pool directly. They broke an almost unused BUSD pool in the same app and used it to borrow KAVA without ever repaying. Kava has not confirmed this account.

A nearly dead BUSD pool

BUSD was Binance's dollar stablecoin. Its issuer, Paxos, stopped minting new BUSD in February 2023. Some BUSD still sat on Kava from years ago. According to Bitquery, just before the attack the Kava Lend BUSD pool owed lenders about 440,145 BUSD but held only 0.003 BUSD in cash, had 5,084 BUSD out on loan across 37 loans, and carried 7,618 BUSD of reserves on its books. In other words, the pool's books no longer added up.

The supply index and the 243,000x jump

Kava Lend pays lenders through a number called the supply index. When the index rises by 1%, every deposit in that pool is worth 1% more. Each block, the app divides the interest earned by the "money supplied," which is cash plus loans minus reserves.

Bitquery says one wallet first repaid all 37 open BUSD loans, then made a deposit, a loan and a withdrawal with amounts chosen so that the money supplied came to just 2 base units, the smallest piece of BUSD the chain can count. The code guards against a value of exactly zero, but not against a value close to zero. Dividing even a tiny amount of interest by 2 base units made every BUSD deposit grow 8,380 times in one block. Within about three minutes the index rose from 2.76 to 671,187, roughly 243,000 times. The wallet's small deposit now read about 1.26 billion BUSD on the pool's books.

127 loans erased by liquidation

With that inflated claim, the first wallet could withdraw any BUSD put into the pool. A second "helper" wallet deposited BUSD as collateral, the first wallet withdrew the same BUSD and sent it back, and the loop repeated several times. The helper's collateral grew on paper while the real BUSD kept returning. The helper then borrowed KAVA, up to about half the credited collateral value, at roughly 445,720 KAVA per round, just under the 448,358 KAVA borrowing cap that, according to Altcoin Reporter, governance set in October.

In the next block, the first wallet liquidated the helper. The app looked for BUSD to seize, found almost none, put 0 to 2 base units up for auction, paid the liquidator a reward and closed the loan. The helper kept the KAVA and owed nothing. Because each erased loan freed room under the cap, the loop could run again. Bitquery counts 127 rounds in 98 minutes and 55,205,051 KAVA borrowed. The KAVA pool fell from about 55.3 million to 519 KAVA.

Bitquery notes that those coins belonged to the people who had lent them, and that the result is consistent with Kava's statement that nothing was minted. Altcoin Reporter also reports that total KAVA supply is unchanged at about 1.083 billion. The 55.2 million KAVA is about 5% of that supply.

Where the money went

Bitquery says the KAVA price did not move for about six hours. A third wallet then sold 48.4 million KAVA on BNB Chain in 35 minutes for about $2.09 million, mostly through an aggregator, and the price on BNB Chain fell 36% during the sale. According to Bitquery, $1.17 million of proceeds was used to buy about 2,190 XMR1, a Monero-named token on Hyperliquid, across eight accounts, and none had moved as of 16:14 UTC (19:44 Tehran). The Relay bridge blocked 612,416 USDT, about 29% of the proceeds, with the reason "BLOCKED_WALLET." Bitquery also says the wallets rehearsed with small BUSD transactions between November 8 and 10.

Bitquery stresses that links between wallets are money links and do not prove who controls them. MyTraderBot does not publish the addresses involved.

Market and exchange impact

According to CoinGecko data cited by Altcoin Reporter, KAVA traded near $0.068 until about 10:05 UTC (13:35 Tehran) and touched a record low of $0.0356 at 11:57 UTC (15:27 Tehran). Crypto Briefing reported an intraday fall of more than 40%. At our check on CoinGecko at 00:22 Tehran on November 15, KAVA was about $0.0364 (USD), down about 46.5% over 24 hours.

Upbit's notice, timestamped 19:36 Korea time (10:36 UTC, 14:06 Tehran), suspended KAVA deposits and withdrawals because of signs of a security incident, citing Korea's virtual-asset user protection rules. It said service will resume only after transfer stability is confirmed. A second notice at 20:00 Korea time (11:00 UTC, 14:30 Tehran) urged caution, saying a suspected security problem had been found on the Kava chain and volatility could increase. Crypto Briefing described Upbit's step as placing KAVA on a watch list; Upbit's own text is a caution notice. Bithumb and Coinone also halted KAVA transfers, according to Crypto Briefing and TokenPost; we could not view their notices directly.

The broader market backdrop is a nervous one for security. Recent incidents include the $6.34 billion Binance hack and the Initia L1 halt after unauthorized escrow transfers.

Context: Kava Lend was already being wound down

Kava Lend was in the middle of a planned shutdown. Kava governance Proposal 222, titled "Phase 2: End Incentives, Limit Borrowing, and Signal Protocol Wind-Down," passed with voting ending on October 5, 2026. It ended incentives, closed reward claims on November 1, set Lend borrow limits near outstanding balances and asked users to close positions before Phase 3.

Analysis: a protocol in wind-down can be riskier, not safer. Activity and monitoring fall, old pools like BUSD sit almost empty, and odd balances can remain. Altcoin Reporter notes that this left a thin, little-watched pool still holding tens of millions of KAVA in recorded deposits.

What it means for users and depositors

  • Kava Lend depositors: the KAVA pool is close to empty according to on-chain data. Kava has not said whether or how losses will be covered. Watch only official Kava channels for any recovery process.

  • Exchange holders: KAVA held on Upbit, Bithumb or Coinone is not affected by the on-chain drain itself, but it cannot be moved on or off those exchanges until they reopen transfers.

  • Bridge users: withdrawals through the Axelar bridge are paused. Do not resend funds or try workarounds.

  • Scam risk: incidents attract fake "refund" or "claim" sites. Do not connect a wallet to links shared in replies or direct messages, and review your token approvals if you used Kava apps.

  • Volatility: sharp moves and thin liquidity are likely while questions remain. Our risk management guide explains position sizing in such conditions.

This article is news and analysis, not investment advice or a trading signal.

Glossary

  • Kava Lend: a lending and borrowing app built into the Kava chain, where lenders deposit tokens and borrowers post collateral.

  • Supply index: a per-pool number that tracks how much each deposit has grown from interest.

  • Base unit: the smallest unit of a token the chain can record; for BUSD here, one hundred-millionth of a coin.

  • Collateral: assets a borrower locks to secure a loan.

  • Liquidation: a process that closes an under-collateralized loan by seizing and auctioning collateral.

  • Borrowing cap: a limit on the total amount of a token that can be borrowed from a pool.

  • Infinite mint: an exploit that creates new tokens out of nothing; Kava says this did not happen.

  • Bridge: a system that moves a token's value from one blockchain to another.

What to watch

  • Kava's full incident report: root cause, confirmed loss and a plan for depositors.

  • When the Axelar bridge and exchange transfers on Upbit, Bithumb and Coinone reopen.

  • Whether Upbit's caution notice leads to further review of KAVA.

  • Whether the USDT blocked at Relay or funds on Hyperliquid are frozen or recovered.

  • Whether other wind-down protocols review old, low-liquidity pools.

FAQ

Was new KAVA minted?

Kava says no, and on-chain data shows total supply unchanged at about 1.083 billion KAVA. The tokens came out of existing deposits in Kava Lend.

How much was taken?

Bitquery counts about 55.2 million KAVA borrowed and never repaid. Kava has not published its own figure.

Has Kava confirmed the cause?

No. The BUSD supply-index explanation comes from Bitquery's analysis. Kava has promised a complete incident report.

Can I move KAVA on Upbit?

Not at the time of writing. Upbit says it will announce a restart after confirming transfer stability.

Sources

Share

See the signals and their results

Browse publicly logged signals and how they performed, or create a free account to follow them.

Kava Lend Exploit Drains 55M KAVA; Upbit Halts Transfers