I woke up and saw KAVA trending. I thought some old coin had come back from the dead and was pumping, but then I clicked in and—wow, it had been hacked.
Here’s what happened: A hacker exploited an arithmetic bug in a BUSD market in Kava Lend’s lending pool, inflating the value of the collateral by 243,000 times. They then borrowed 127 times, making off with 55.2 million KAVA in an hour and a half. The pool went from 55.33 million KAVA to just 0.19—literally drained dry. At the pre-hack price of $0.068, that was worth $3.76 million. The hacker moved the funds to BNB Chain and sold 48.4 million KAVA within 35 minutes, netting about $2.1 million. KAVA fell as much as 47% in a day. Binance’s price page now shows $0.04, and it hit a new all-time low today.
On one side, there’s the project team: Kava says the incident is under control, there was no unlimited minting, they’re investigating, and a full report will follow. On the other side, there are the people who deposited their money: the pool is empty, so how are they supposed to get their loans repaid? In South Korea, Upbit, Bithumb, and Coinone have already suspended KAVA deposits and withdrawals. And here’s the really troubling part: the attack began Friday night, but Kava didn’t acknowledge it until 6:30 Saturday morning—more than seven hours later.
I’m siding with the depositors: the bug can be fixed and a report can be written, but an empty pool is still an empty pool. The biggest fear with a lending protocol isn’t getting hacked once—it’s that people will never dare to put their money in again. This time, KAVA didn’t just lose price. It lost trust.
Which side are you on? Do you think a drained lending pool can bounce back once it’s fixed, or is trust impossible to rebuild once it’s broken?
#KAVA
Here’s what happened: A hacker exploited an arithmetic bug in a BUSD market in Kava Lend’s lending pool, inflating the value of the collateral by 243,000 times. They then borrowed 127 times, making off with 55.2 million KAVA in an hour and a half. The pool went from 55.33 million KAVA to just 0.19—literally drained dry. At the pre-hack price of $0.068, that was worth $3.76 million. The hacker moved the funds to BNB Chain and sold 48.4 million KAVA within 35 minutes, netting about $2.1 million. KAVA fell as much as 47% in a day. Binance’s price page now shows $0.04, and it hit a new all-time low today.
On one side, there’s the project team: Kava says the incident is under control, there was no unlimited minting, they’re investigating, and a full report will follow. On the other side, there are the people who deposited their money: the pool is empty, so how are they supposed to get their loans repaid? In South Korea, Upbit, Bithumb, and Coinone have already suspended KAVA deposits and withdrawals. And here’s the really troubling part: the attack began Friday night, but Kava didn’t acknowledge it until 6:30 Saturday morning—more than seven hours later.
I’m siding with the depositors: the bug can be fixed and a report can be written, but an empty pool is still an empty pool. The biggest fear with a lending protocol isn’t getting hacked once—it’s that people will never dare to put their money in again. This time, KAVA didn’t just lose price. It lost trust.
Which side are you on? Do you think a drained lending pool can bounce back once it’s fixed, or is trust impossible to rebuild once it’s broken?
#KAVA
