Bitcoin Forum
May 31, 2026, 01:10:56 AM *
News: Latest Bitcoin Core release: 31.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Did North Korean Hackers Just Play Aave Twice?  (Read 32 times)
Alpen (OP)
Member
**
Offline

Activity: 378
Merit: 45


View Profile
May 29, 2026, 05:38:27 AM
 #1

The Lazarus Group's attack on the Kelp platform may have generated additional profits for North Korean hackers by shorting the AAVE token. Five days after the launch of the V4 protocol with its new 'hub-and-spoke' architecture, the attackers timed the deposit of 89,567 'non-existent' rsETH into the Aave death contract.

This triggered a five-day rally in AAVE, which ended with the Kelp hack. This allowed the hackers to earn a 26% profit on their short position. The Lazarus Group had previously employed a similar strategy with the Ronin bridge, where the hack was accompanied by short positions on AXS and RON in anticipation that the news would cause the price to crash.

In that case, however, Ronin validators remained unaware for a week that $600 million had been stolen, and the hackers’ short positions were closed via margin calls. In contrast, news of the AAVE hack became public instantly, sending prices plummeting to yearly lows.

The resulting crisis of user confidence led to an outflow of liquidity from the platform. DeFiLlama data shows a loss of $6.6 billion in TVL. According to Cryptomus analysts, investors are continuing to sell AAVE tokens and the inflow of coins to exchanges is growing.
shinratensei_
Legendary
*
Offline

Activity: 3850
Merit: 1053


Leading Crypto Sports Betting & Casino Platform


View Profile
May 29, 2026, 06:23:43 AM
 #2

They are trying to extract profit from all sides, but this kind of thing won't even become possible if the contract isn't hacked in the first place.

There has been tweets about how white hat bug bounty hunters are getting underpaid severely for their bug reports, I think they should work on that to prevent this kind of thing from happening.
It's better to pay white hat bounty hunters some money than getting entire contract drained.

..Stake.com..   ▄████████████████████████████████████▄
   ██ ▄▄▄▄▄▄▄▄▄▄            ▄▄▄▄▄▄▄▄▄▄ ██  ▄████▄
   ██ ▀▀▀▀▀▀▀▀▀▀ ██████████ ▀▀▀▀▀▀▀▀▀▀ ██  ██████
   ██ ██████████ ██      ██ ██████████ ██   ▀██▀
   ██ ██      ██ ██████  ██ ██      ██ ██    ██
   ██ ██████  ██ █████  ███ ██████  ██ ████▄ ██
   ██ █████  ███ ████  ████ █████  ███ ████████
   ██ ████  ████ ██████████ ████  ████ ████▀
   ██ ██████████ ▄▄▄▄▄▄▄▄▄▄ ██████████ ██
   ██            ▀▀▀▀▀▀▀▀▀▀            ██ 
   ▀█████████▀ ▄████████████▄ ▀█████████▀
  ▄▄▄▄▄▄▄▄▄▄▄▄███  ██  ██  ███▄▄▄▄▄▄▄▄▄▄▄▄
 ██████████████████████████████████████████
▄▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄
█  ▄▀▄             █▀▀█▀▄▄
█  █▀█             █  ▐  ▐▌
█       ▄██▄       █  ▌  █
█     ▄██████▄     █  ▌ ▐▌
█    ██████████    █ ▐  █
█   ▐██████████▌   █ ▐ ▐▌
█    ▀▀██████▀▀    █ ▌ █
█     ▄▄▄██▄▄▄     █ ▌▐▌
█                  █▐ █
█                  █▐▐▌
█                  █▐█
▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▀█
▄▄█████████▄▄
▄██▀▀▀▀█████▀▀▀▀██▄
▄█▀       ▐█▌       ▀█▄
██         ▐█▌         ██
████▄     ▄█████▄     ▄████
████████▄███████████▄████████
███▀    █████████████    ▀███
██       ███████████       ██
▀█▄       █████████       ▄█▀
▀█▄    ▄██▀▀▀▀▀▀▀██▄  ▄▄▄█▀
▀███████         ███████▀
▀█████▄       ▄█████▀
▀▀▀███▄▄▄███▀▀▀
..PLAY NOW..
Alpen (OP)
Member
**
Offline

Activity: 378
Merit: 45


View Profile
May 30, 2026, 06:27:26 AM
 #3

They are trying to extract profit from all sides, but this kind of thing won't even become possible if the contract isn't hacked in the first place.

There has been tweets about how white hat bug bounty hunters are getting underpaid severely for their bug reports, I think they should work on that to prevent this kind of thing from happening.
It's better to pay white hat bounty hunters some money than getting entire contract drained.

White hats wouldn't have helped here. There was no code bug; it was simply an issue of having too few validators.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!