# Kava Lend attack prompts exchange transfer suspensions Author: Abdullah Özkurt Language: English Published: 2026-11-15T11:37:57+03:00 Updated: 2026-11-15T11:37:57+03:00 ![A red ceramic module releases metal spheres through an open seam beside an optical sensor; conceptual illustration.](https://kriptometa.com/uploads/kava-lend-saldirisi-borsalar-transferleri-durdurdu-362453953ea6_article.webp) ## Key takeaways - Kava said the November 14 incident was confined to Kava Lend. - KAVA trading remains available on Bithumb; no transfer restart time was set. - The 55.2 million KAVA cited in onchain analyses is the total borrowed during the attack. Following the Kava Lend attack, Bithumb suspended KAVA deposits and withdrawals. MEXC separately announced a halt to deposits only. [Crypto exchanges](https://kriptometa.com/en/best-crypto-exchanges) restricted KAVA transfers after the November 14 attack on Kava Lend. The [Kava team acknowledged](https://x.com/KAVA_CHAIN/status/2121574325765476462) that tokens had been bridged to BNB Chain and sold. It said the incident was confined to its lending application and did not involve unlimited token minting. Kava Lend is [a DeFi application](https://kriptometa.com/en/glossary/defi) where users supply assets to earn interest and borrow [against collateral](https://kriptometa.com/en/glossary/health-factor-collateral). Its [technical documentation](https://docs.kava.io/docs/cosmos/modules/hard/concepts/) says supplied assets are held in a shared protocol account and borrowing limits depend on collateral. ## How 55.2 million KAVA was borrowed [Bitquery’s investigation](https://bitquery.io/investigations/kava-hack) says the attackers manipulated interest accounting in the little-used BUSD market. The index used to calculate growth in deposits rose roughly 243,000-fold. The protocol lent against inflated deposit balances that lacked matching assets. According to [The Block’s analysis of onchain data](https://www.theblock.co/news/defi/2026-11-14-kava-lend-loses-roughly-3-8-million-to-hack-sending-kava-token-down-nearly-40-440350), about 55.2 million KAVA was borrowed in 127 transactions. The publication valued that amount at roughly $3.76 million using the pre-attack price of $0.068 per token. Bitquery reports that two wallets repeated borrowing and liquidation transactions, with the protocol clearing debt without collecting enough collateral. The analysts say existing KAVA was taken from the pool. Their technical findings use November 14 chain records and have yet to be confirmed in the team’s final incident report. The Block says about 49.2 million KAVA was bridged to BNB Chain through LayerZero. Sales brought in BNB and USDT worth roughly $2.09 million. The $3.76 million valuation and $2.09 million in proceeds must not be added as separate losses. ## Transfers halted, trading continues In its [official notice](https://feed.bithumb.com/notice/1655673), Bithumb set the suspension of KAVA deposits and withdrawals for November 14 at 19:35 KST, or 10:35 UTC. Trading remained available. The exchange warned that pending transfers could take longer to reach accounts and said transfers would resume after network stability checks. In a [separate warning](https://feed.bithumb.com/notice/1655674), Bithumb said the security incident could bring sharp KAVA price swings. That warning does not announce the closure of trading pairs. [MEXC’s notice covers KAVA deposits only](https://www.mexc.com/announcements/article/suspension-of-kava-deposits-17827791539759). It does not state whether withdrawals are restricted or give a reopening time. Service restrictions in the reviewed announcements | Platform | Announced restriction | Stated limit | |---|---|---| | Bithumb | KAVA deposits and withdrawals | Trading remains available | | MEXC | KAVA deposits | Withdrawal status unspecified | | Kava / Axelar | Bridge withdrawals | No reopening date | ## Axelar bridge withdrawals also paused [TokenPost reported](https://www.tokenpost.com/news/technology/57404) that Kava also paused asset withdrawals through [its Axelar bridge](https://kriptometa.com/en/glossary/blockchain-bridge) as a precaution. The team said it would publish an incident report when ready. The Axelar measure concerns a different bridge from the LayerZero transfers described above. The reviewed statements do not provide a final loss total from the Kava team, a repayment plan for affected users or a bridge reopening date. The onchain analysts’ estimates are not a compensation amount approved by the team.