South Korean cryptocurrency exchange Bithumb has formally designated KAVA as an investment-warning asset following the November 14 security breach affecting Kava Lend, opening a review that could result in the cryptocurrency losing its trading support on the platform.
The designation, announced on November 16 at 14:00 Korea Standard Time (05:00 UTC), follows Bithumb’s earlier suspension of KAVA deposits and withdrawals. The exchange expects to announce whether it will extend the warning, remove it or terminate trading support between December 14 and December 18, 2026.
The decision introduces a seperate listing risk for KAVA holders while the project attempts to contain the consequences of an exploit that removed approximately 53.9 million tokens from its lending application. Kava has since confirmed the amount taken, identified the vulnerability and announced plans to accelerate the retirement of the affected lending service.
First a transfer freeze, then a formal listing review, all within two days.
Bithumb sets December deadline for KAVA review
Bithumb said its designation was based on confirmation of a security incident involving a cryptocurrency wallet or distributed-ledger infrastructure used to issue, transfer or store digital assets, where the cause remained unidentified or the incident had not been adequately remedied.
The exchange applied its cryptocurrency trading-caution policy, which operates under South Korea’s industry standards for supporting digital-asset trading. Its trading-support review committee will assess whether the conditions behind the warning have been resolved.
Bithumb identified three possible outcomes for its December review: an extension of the warning, removal of the designation or termination of trading support. The exchange also said the announced schedule could change for internal reasons.
The warning does not constitute an immediate delisting. KAVA trading remains supported, although deposits and withdrawals are still suspended. Bithumb has not announced a date for restoring either service.
The exchange said a warning can be removed before the scheduled review concludes if the underlying concerns are satisfactorily resolved. It has not disclosed the specific evidence it will require from Kava, nor whether the project’s newly announced security measures will satisfy its review committee.
That leaves the formal warning in place despite a more detailed explanation of the attack from Kava itself. The exchange has not yet published a subsequent assesment of those disclosures.
Kava confirms 53.9 million tokens taken from lending pool
In a November 16 incident update, Kava confirmed that approximately 53.9 million KAVA had been taken from HARD Lend, the decentralized lending application previously known as Kava Lend.
The project identified a vulnerability in the lending application’s accounting system. An attacker manipulated calculations involving BUSD collateral, artificially increasing its recorded value before repeatedly borrowing KAVA and triggering liquidations that allowed existing tokens to leave the lending pool.
Earlier blockchain investigations identified approximately 55.2 million KAVA involved in repeated borrowing transactions. DaveFinances previously examined the 55.2 million KAVA accounting discrepancy, which emerged when the lending module’s recorded deposits substantially exceeded the tokens remaining in its directly observable account.
The two figures describe different measures. The approximately 55.2 million KAVA represents the gross borrowing activity identified in transaction records, while Kava’s newly disclosed 53.9 million figure represents the amount removed from the lending application.
The accounting was the weak part, and a rather expensive one.
Kava also confirmed that approximately 49.2 million KAVA were transferred to BNB Chain through LayerZero. Independent transaction analysis indicates that much of the bridged amount was subsequently sold, generating approximately $2.1 million in proceeds.
At a pre-incident reference price of approximately $0.068, the 53.9 million stolen tokens would have been worth about $3.67 million. Their dollar value declined as KAVA lost more than 40% during the November 14 selloff. The initial token valuation should therefore not be confused with the amount realised through subsequent sales.
Kava said the exploit was confined to HARD Lend and did not compromise the underlying security of the Kava blockchain. The attack also did not create additional native KAVA tokens, according to the project.
The team reported that the identified vulnerability had been blocked, protective measures were operating and some attacker-controlled funds had been frozen. It did not quantify the frozen amount or disclose how much of the stolen cryptocurrency had been recovered.
Kava is also preparing a governance proposal to permanently disable new lending and borrowing through a seven-day voting process. The proposal would accelerate an existing wind-down of HARD Lend, with additonal guidance promised for users holding outstanding positions.
Its incident update stated that individual user deposits were largely unaffected, but did not provide a detailed reconciliation of outstanding lender claims or specify arrangements for compensating any remaining losses.
KAVA trading continues despite transfer restrictions
The formal warning follows a sequence of exchange interventions that began on November 14.
Bithumb initially scheduled the suspension of KAVA deposits and withdrawals for 19:35 KST that day, citing indications of a potential security problem. At 20:00 KST, it issued a further cautionary notice warning customers about increased volatility following the suspected incident.
Upbit and Coinone introduced comparable transfer restrictions. DaveFinances previously reported how Upbit, Bithumb and Coinone suspended KAVA transfers as unusually large cross-chain movements and token sales emerged.
The market stayed open, the movement of tokens did not.
Bithumb’s November 14 suspension allowed existing spot trading to continue while external deposits and withdrawals were restricted. Its November 16 notice confirmed that the transfer suspension remained in effect.
The restrictions affect how customers can access exchange liquidity. Tokens already credited to Bithumb accounts can be traded, but customers transferring KAVA from external wallets cannot recieve normal deposit credit while the suspension remains in force.
Bithumb warned that blockchain congestion and confirmation delays could also prevent some transactions initiated before the cutoff from being reflected in customer balances. Deposits received during the restriction will be processed according to the arrangements applicable when trading support is restored or terminated.
With external transfers unavailable, traders cannot freely move KAVA between venues to exploit price differences. The resulting market fragmentation could allow exchange prices to diverge, although the available notices do not quantify any sustained premium or discount on Bithumb.
The exchange’s restrictions also have a defined legal context. Bithumb’s November 14 suspension cited Article 17(2)(b) of South Korea’s Enforcement Decree under the Virtual Asset User Protection Act, which addresses circumstances permitting restrictions on cryptocurrency deposits and withdrawals.
Its November 16 warning separately referred to Article 17(1)(e), concerning deposit restrictions during procedures to terminate trading support. That reference does not establish that Bithumb has already decided to delist KAVA or that a financial regulator ordered the warning.
Previous Korean delistings put KAVA’s review in focus
Bithumb’s decision comes three days after the exchange announced that it would terminate trading support for MANTRA and RECALL on December 14.
In the MANTRA case, Bithumb concluded that follow-up measures, including compensation arrangements after an earlier blockchain security incident, did not satisfy its continued listing standards. Upbit also announced plans to terminate MANTRA trading support on the same date.
DaveFinances covered the MANTRA delistings announced by Bithumb and Upbit, which followed an extended period of security-related warnings and review.
MANTRA’s experience demonstrates that addressing a technical vulnerability does not automatically resolve every issue considered during an exchange’s trading-support review. The adequacy of recovery measures and explanations submitted by a project can also influence the outcome.
Some parts are fixed, the exchange review isn’t.
Kava’s November 16 disclosure provides new evidence about the exploit mechanism, its scope and the steps taken to prevent its recurrence. Yet the project has not established a final recoverable-loss figure, disclosed a comprehensive compensation arrangement or completed the proposed governance process for retiring HARD Lend’s borrowing functions.
Bithumb has not stated that these outstanding items must all be completed before its warning can be lifted. The exchange’s published decision identifies the security incident as the reason for the designation without providing a detailed checklist for reinstating normal asset status.
There is also no announced trading-termination date for KAVA. December 14–18 is the expected window for communicating the next decision, rather than an automatic deadline for removing the cryptocurrency.
For now, KAVA holders face two unresolved operational questions: when external transfers will resume and whether the token will retain access to Bithumb’s trading markets. The project’s security update has narrowed the technical uncertainty surrounding the attack, but the exchange’s listing decision remains pending.
Johan Shamshad is Editor-in-Chief at Dave Finances, covering financial markets, digital assets, trading platforms, brokers, fintech, payments and regulation. Since 2023, he has also worked as an editor at Gulf News, the UAE English-language newspaper published by Al Nisr Publishing LLC. His work focuses on market-moving developments, company disclosures, regulatory changes and trading infrastructure, with an emphasis on primary-source verification and practical context for traders and investors.

