CyberSIXT reportingUpdated
Kava Lend drained of 54 million KAVA, nearly all from Kava's own pool
Part of the Kava story · since 14 Nov
- Sat 14 Nov, 16:55 UTC. cybersixt, first report. Kava Lend drained of 54 million KAVA, nearly all from Kava's own pool. This article, 1st of 1.
Updated 16 November, 10:39 UTC. Kava's incident report: a BUSD collateral-valuation flaw let the attacker take 53.9 million KAVA; some funds are frozen and HARD Lend lending will be shut down.
Kava has published its incident report on the 14 November attack on Kava Lend, also called HARD Lend. It says the attacker exploited a lending-accounting vulnerability that inflated the value of BUSD collateral, then used repeated borrowing and liquidation transactions to withdraw the KAVA already in the lending pool. About 53.9 million KAVA was taken, and about 49.2 million of it was bridged to BNB Chain through LayerZero.
Kava says the exploit has been blocked, that some of the attacker's funds have been frozen, and that it is working with partners, exchanges and law enforcement to trace and freeze the rest. The incident was confined to the lending application: the Kava chain itself was not compromised and no new KAVA was created. Kava is also speeding up the retirement of HARD Lend's legacy lending: a governance proposal to permanently disable new lending and borrowing will go through the required seven-day vote, and remaining positions will be handled through an "orderly process" with further guidance for users.
The report names the addresses involved: kava1uzx5924cqsutcw365ajs8kkc3rr4vtlyzms255 and kava1v2s266sll8ca5xrs06swmsc00nwwt7u77eufk4 on Kava, and 0x37d732914f86cc6eb1e87419e3046a739f011042 on BNB Chain. It does not explain how the BUSD collateral value was inflated, how much has been frozen, or whether the community pool will be made whole.
Whose KAVA was taken
Kava says individual user deposits were "largely unaffected", which matches what on-chain records showed on Saturday. The Kava chain's community module, which holds the network's community pool, accounted for about 55.09 million of the 55.21 million KAVA recorded as deposited in Kava Lend, or 99.8%. Other depositors accounted for about 121,700 KAVA. The loss therefore falls mainly on the network's shared treasury, though the users' share also left the pool.
How the attack unfolded
Kava first said at 11:28 UTC on 14 November that it was tracking unexpected behaviour from a dApp in its ecosystem. At 12:01 UTC it said it was aware of KAVA being bridged and sold on BNB Chain, that "this is not an infinite mint", and that the event was contained within Kava Lend. At 14:05 UTC it paused the Axelar bridge, which stops cross-chain withdrawals. The KAVA token fell more than 40% that day and exchanges paused deposits and withdrawals; Upbit issued a trading warning, BeInCrypto reports.
By about 17:00 UTC the module's own accounting still recorded about 55.2 million KAVA as deposited and recorded KAVA borrows of only about 2,640 KAVA, while the module account that should hold those deposits contained 0.19 KAVA. That gap is consistent with the mechanism Kava now describes: KAVA leaving through borrowing and liquidation against inflated collateral rather than through ordinary loans.
What users should do
Kava Lend users should not assume balances shown in the app can be withdrawn and should wait for Kava's guidance on remaining positions, which it says will come through official channels. Holders of bridged KAVA should expect cross-chain withdrawals through Axelar to stay paused until Kava says otherwise. Exchanges and services can screen for the three attacker addresses above.
What is not known
Kava has not said how much of the stolen KAVA has been frozen, why its figure of 53.9 million differs from the 55.2 million recorded as deposited, whether the community pool or other depositors will be repaid, or when partner exchanges will reopen KAVA deposits and withdrawals.
How the story developed
1 article from 1 outlet since 14 Nov. Quiet since 14 Nov. This was the first report.
- Sat 14 Nov, 16:55 UTC. cybersixt, first report. Kava Lend drained of 54 million KAVA, nearly all from Kava's own pool. This article, 1st of 1.
- No CVE
- Larger: an outlet’s first report
- Coverage over time
- Quiet time, folded
Show all 1 articles as a listHide the list
- Sat 14 NovDay 01
- Kava Lend drained of 54 million KAVA, nearly all from Kava's own pool16:55 · cybersixt · First report · This article, 1st of 1
Sources
- Kava: HARD Lend security incident reportPrimary sourcemedium.com
- Kava on X: tracking unexpected behaviourPrimary sourcex.com
- Kava on X: not an infinite mint, contained within Kava LendPrimary sourcex.com
- Kava on X: Axelar bridge pausedPrimary sourcex.com
- BeInCrypto on X: KAVA falls, Upbit warningx.com
- Kava chain: community module accountPrimary sourcekava-api.polkachu.com
- Kava chain: Kava Lend deposits of the community modulePrimary sourcekava-api.polkachu.com
- Kava chain: Kava Lend total KAVA depositedPrimary sourcekava-api.polkachu.com
More reporting
- Suspected Optimizely breach planted card stealer on 186 websites16 Nov
- BundID cyberattack locks German accounts, email codes now required16 Nov
- Trezor data breach at shipping partner exposes 27,000 orders16 Nov
- Fugaku supercomputer hit by cyberattack, users' SSH keys stolen16 Nov
- Lighter DEX exploit drains $10.4M via a trader's leaked API keys16 Nov
Written by CyberSIXT from the sources above.How we reportCorrectionsRSS