Kava responds urgently! Unusual cross-chain activity limited to Kava Lend; KAVA briefly plunged nearly 40%
Another alarming security incident has hit the DeFi market—this time, it’s Kava.
On November 14, Kava officially announced that unusual on-chain activity had occurred within its ecosystem, involving the cross-chain transfer of KAVA tokens to BNB Chain (BSC), where they were subsequently sold.
After an initial investigation, the team said the incident was limited to Kava Lend and did not involve unrestricted minting of KAVA. The unusual activity is now under control.
But the details of the incident are more complex than the initial announcement suggested.
According to The Block’s analysis of on-chain data, the attacker exploited a long-dormant BUSD lending market on Kava Lend, repeatedly borrowing KAVA by artificially inflating the value of collateral.
On-chain data shows that approximately 55.2 million KAVA were transferred out, worth around $3.76 million based on prices before the attack. About 49.2 million were bridged to BNB Chain, and some were sold for approximately $2.09 million in BNB and USDT.
Following the incident, some partner exchanges suspended KAVA deposits and withdrawals, and the price of KAVA also fell sharply.
One point needs special emphasis:
The absence of unrestricted minting does not mean there were no financial losses.
Kava officials stressed that the issue was contained to Kava Lend, but the cause of the vulnerability, the final amount of losses, and the number of affected users remain unclear pending a full investigation report.
This incident is another reminder to the entire DeFi industry: security risks don’t necessarily come from the underlying chain itself. Sometimes, a long-dormant lending market or an inconspicuous flaw in a contract’s calculations can become an attack vector.
I’ve always felt that DeFi’s real competitive edge isn’t just yields or the amount of capital—it’s whether users feel comfortable entrusting their assets to it.
Code can be upgraded continuously, but once users’ trust in a platform is damaged, it takes much longer to restore.
What do you think is the most important lesson DeFi projects should learn from this Kava incident: contract audits, management of dormant markets, or risk-monitoring mechanisms?
#Kavalend #DeFi #kava称异常跨链活动仅限kavalend
Another alarming security incident has hit the DeFi market—this time, it’s Kava.
On November 14, Kava officially announced that unusual on-chain activity had occurred within its ecosystem, involving the cross-chain transfer of KAVA tokens to BNB Chain (BSC), where they were subsequently sold.
After an initial investigation, the team said the incident was limited to Kava Lend and did not involve unrestricted minting of KAVA. The unusual activity is now under control.
But the details of the incident are more complex than the initial announcement suggested.
According to The Block’s analysis of on-chain data, the attacker exploited a long-dormant BUSD lending market on Kava Lend, repeatedly borrowing KAVA by artificially inflating the value of collateral.
On-chain data shows that approximately 55.2 million KAVA were transferred out, worth around $3.76 million based on prices before the attack. About 49.2 million were bridged to BNB Chain, and some were sold for approximately $2.09 million in BNB and USDT.
Following the incident, some partner exchanges suspended KAVA deposits and withdrawals, and the price of KAVA also fell sharply.
One point needs special emphasis:
The absence of unrestricted minting does not mean there were no financial losses.
Kava officials stressed that the issue was contained to Kava Lend, but the cause of the vulnerability, the final amount of losses, and the number of affected users remain unclear pending a full investigation report.
This incident is another reminder to the entire DeFi industry: security risks don’t necessarily come from the underlying chain itself. Sometimes, a long-dormant lending market or an inconspicuous flaw in a contract’s calculations can become an attack vector.
I’ve always felt that DeFi’s real competitive edge isn’t just yields or the amount of capital—it’s whether users feel comfortable entrusting their assets to it.
Code can be upgraded continuously, but once users’ trust in a platform is damaged, it takes much longer to restore.
What do you think is the most important lesson DeFi projects should learn from this Kava incident: contract audits, management of dormant markets, or risk-monitoring mechanisms?
#Kavalend #DeFi #kava称异常跨链活动仅限kavalend