South Korean cryptocurrency exchanges Upbit, Bithumb and Coinone suspended KAVA deposits and withdrawals on November 14, 2026, after suspected exploitation of the Kava Lend protocol triggered large cross-chain token transfers and a price decline exceeding 40%.
The restrictions prevent customers from moving KAVA between the affected exchanges and external wallets, although spot trading remains available. Bithumb and Coinone confirmed that deposits received during the suspension may not be credited until security checks are completed and transfers resume.
Kava acknowledged unusual activity involving tokens transferred to BNB Smart Chain and subsequently sold. The blockchain project said the incident was isolated to Kava Lend, its lending protocol, and rejected speculation that an attacker had created unlimited KAVA tokens.
Independent blockchain investigations identified approximately 48.36 million KAVA transferred across chains, initially valued at roughly $3.3 million. A separate examination of Kava Lend’s accounting found approximately 55.2 million KAVA recorded as deposits, despite almost none remaining in the associated module account.
The larger accounting discrepancy has not been confirmed as a final financial loss by Kava. The company has promised a full incident report but has not disclosed the cause of the suspected exploit, the number of affected depositors or any recovery arrangements.
Bithumb, Upbit and Coinone suspend KAVA deposits and withdrawals
Bithumb announced its KAVA suspension at 19:35 Korea Standard Time (10:35 UTC) on November 14, citing indications of a security problem involving the cryptocurrency.
The exchange said the restriction would continue until network stability could be established. It did not provide a reopening date.
Upbit issued a comparable notice at approximately 19:36 KST, suspending deposits and withdrawals through the Kava network. The exchange subsequently published a trading-caution announcement at 20:00 KST, warning customers about increased volatility following the suspected security incident.
Coinone followed at 19:40 KST, with its announcement describing the interruption as a temporary measure for security verification and asset protection.
Trading carried on, just the transfers did not.
Coinone explicitly stated that other services, including trading and staking, would remain unaffected unless separately announced. Bithumb likewise confirmed that ordinary trading would continue during the deposit and withdrawal suspension.
The restrictions were announced before Kava provided its detailed public clarification. At 20:28 KST, the project initially acknowledged unexpected activity involving a decentralized application. Its subsequent statement at 21:01 KST identified Kava Lend and confirmed that KAVA had been transferred to BNB Smart Chain and sold.
Kava later paused its Axelar bridge as an additional precaution, temporarily preventing cross-chain withdrawals through that infrastructure. The company did not announce when the bridge would reopen.
The exchange decisions are narrower than the MANTRA trading-support terminations announced by Bithumb and Upbit on November 13. Those decisions followed an extended review of remediation measures after an earlier blockchain security incident.
KAVA has not been confirmed as delisted by the three exchanges. Their November 14 announcements concern transfer restrictions and trading cautions, not the termination of trading support.
Deposits made during suspension face delayed crediting
Bithumb’s announcement explains how the security measures affect transactions initiated before and after the suspension.
Withdrawal requests submitted before the cutoff but not completed when the restriction began may be delayed while the exchange verifies their processing status.
Incoming transfers face a different problem. Bithumb warned that transactions initiated before the suspension could remain uncredited if blockchain confirmation or internal processing was incomplete. Deposits arriving after the restriction takes effect will be reflected progressively after services resume.
And the notice was fairly specific about the queue.
Coinone published similar conditions, stating that transactions affected during the suspension would be processed or reflected after security measures and system-stability checks were completed.
The exchange specifically advised customers to avoid transferring KAVA during the interruption because some deposits might be delayed or encounter processing difficulties.
These arrangements create two different customer experiences. Traders with KAVA already credited to their exchange accounts can continue submitting eligible market orders, while customers sending tokens from external wallets may have to wait for those deposits to appear in their balances.
A blockchain transaction showing successful delivery does not establish that the receiving exchange has completed its internal account-crediting process. The exchanges have not disclosed how many incoming KAVA transfers are awaiting verification or the total token value involved.
A comparable operational separation appeared during Rakuten Wallet’s recent deposit restoration. The Japanese platform resumed accepting cryptocurrency deposits on November 12 after external security checks, but continued restricting outgoing transfers that had been unavailable since August.
Rakuten’s disruption was unrelated to Kava. Its customer notices nevertheless demonstrate how deposit verification, trading access and withdrawal availability can recover on different schedules.
Cross-chain selling leaves KAVA prices exposed to fragmented liquidity
KAVA’s market decline coincided with unusually large movements from the lending protocol to BNB Smart Chain.
Blockchain investigators reported that approximately 48.36 million KAVA crossed the bridge, including a transfer of roughly 48.21 million tokens shortly after 10:00 UTC on November 14.
At a reference price near $0.068, the combined transfers represented approximately $3.29 million in token value. Kava confirmed that bridging and selling had occurred but did not independently provide a complete transaction-by-transaction accounting.
Investigators also identified approximately 55.2 million KAVA recorded in the lending module’s deposit accounting, against a directly observable balance of less than two KAVA in subsequent snapshots.
The two numbers are not the same number, not yet.
The difference of approximately 6.8 million KAVA between the reported lending deposits and the initial bridged amount cannot automatically be classified as an additional theft. Establishing the final loss requires a reconciliation of borrowed assets, outstanding depositor claims, subsequent transfers and any recoverable holdings.
Price data showed KAVA falling from approximately $0.0687 on November 13 to around $0.0364 during November 14 trading, a decline of roughly 47%. The estimated dollar value of the bridged tokens consequently fell as the market repriced the asset.
The transferred amount should not be confused with the proceeds actually realised by the seller. Selling large quantities through decentralized liquidity pools can produce execution prices below the initial market quotation, and Kava has not disclosed a final sale-proceeds figure.
Exchange deposit restrictions add another market constraint. A trader holding KAVA on one venue cannot necessarily transfer it to another venue offering a higher price, even while trading continues on both platforms.
The price moved quickly, the plumbing did not.
With external deposits blocked, exchanges must rely primarily on existing customer balances and available order-book liquidity to meet trading demand. Price differences between venues may consequently persist longer than they would under normal transfer conditions.
The precise effect on Korean KAVA premiums cannot be quantified from the suspension notices alone. That would require synchronized exchange prices, order-book depth and transfer-status records covering the same period.
Extended transfer restrictions have previously affected other Asian cryptocurrency venues. DaveFinances reported that Binance Japan continued blocking withdrawals for 29 cryptocurrencies on November 9, more than ten days after a security incident involving Binance Global.
That case involved a different security event, but it documented how individual cryptocurrency withdrawal routes can remain unavailable even when an exchange maintains ordinary trading and fiat services.
Korean rules permit emergency transfer restrictions
Bithumb identified a specific legal basis for its November 14 suspension: Article 17, paragraph 2(b), of South Korea’s Enforcement Decree under the Virtual Asset User Protection Act.
The provision permits cryptocurrency service providers to restrict deposits or withdrawals when an incident affecting a virtual-asset issuer creates an urgent need for customer protection or security measures.
The official text of Article 17 of the Enforcement Decree distinguishes security-related emergencies from other grounds for restricting cryptocurrency transfers, including technical failures, account reconciliation and legal compliance requirements.
Bithumb’s reliance on the provision establishes the legal justification cited by the exchange. It does not establish that the regulator ordered the suspension or that the exchange itself suffered a security breach.
Neither Bithumb nor Coinone has disclosed that customer KAVA balances held directly by the exchanges were stolen. The confirmed security concern originates from Kava’s lending ecosystem.
Kava’s denial of an infinite-mint incident also narrows the reported problem. The available evidence concerns the suspected extraction and movement of existing tokens, rather than confirmed unauthorized expansion of native KAVA supply.
For customers waiting on pending deposits, the remaining uncertainty is mostly about procesing and timing. The exchanges have not published the number of transactions awaiting crediting, the verification criteria for those deposits or a timetable for clearing their queues.
Restoration may come exchange by exchange, and not all at once.
Each platform has said it will announce reopening after completing the necessary security and stability checks. Kava’s separate Axelar bridge suspension may require additional technical verification before cross-chain withdrawal services return.
The investigation also leaves unresolved whether the 55.2 million KAVA accounting discrepancy represents unrecovered depositor assets and whether any losses will be reimbursed. Neither Kava nor the Korean exchanges has announced a compensation scheme linked to the November 14 incident.
As of the latest notices reviewed on November 15, the exchanges had not provided confirmed resumption times. The immediate restrictions remain distinct from a delisting decision, while Kava’s promised incident report is still needed to establish the exploit mechanism, realised losses and potential recovery of the affected tokens.
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.