joli-table-of-contents domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/news/wp-includes/functions.php on line 6121
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rank-math domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/news/wp-includes/functions.php on line 6121
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rank-math-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/news/wp-includes/functions.php on line 6121
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/news/wp-includes/functions.php on line 6121
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/news/wp-includes/functions.php:6121) in /var/www/html/news/wp-includes/rest-api/class-wp-rest-server.php on line 1896
{"id":6612,"date":"2023-10-09T09:36:23","date_gmt":"2023-10-09T09:36:23","guid":{"rendered":"https:\/\/lunu.io\/news\/?p=6612"},"modified":"2023-10-09T09:36:25","modified_gmt":"2023-10-09T09:36:25","slug":"htx-exchange-vs-hacker-a-tale-of-strategy-and-resolution","status":"publish","type":"post","link":"https:\/\/lunu.io\/news\/htx-exchange-vs-hacker-a-tale-of-strategy-and-resolution\/","title":{"rendered":"HTX Exchange vs. Hacker: A Tale of Strategy and Resolution!"},"content":{"rendered":"\nIn the waning days of September, HTX, previously known as Huobi’s global exchange, faced a significant breach. The assailant managed to siphon off a staggering 4,997 ETH, equivalent to roughly $7.9 million, directly from the exchange’s hot wallet. Justin Sun, the CEO of HTX, promptly identified the hacker and proposed a deal: return the stolen assets within a week and receive a 5% white-hat bounty, all while avoiding any legal repercussions.<\/p>\n\n\n\n
In the immediate aftermath of the breach, Sun took to the community to assuage concerns. He confirmed that the stolen ETH was fully compensated by the exchange’s reserves, ensuring that user assets remained secure. Sun emphasized, “HTX has fully covered the losses incurred from the attack and has successfully resolved all related issues. All user assets are #SAFU, and the platform is operating completely normally.” To put things into perspective, the stolen $8 million is a mere fraction compared to the $3 billion in assets held by HTX users, equating to just two weeks of the exchange’s revenue.<\/p>\n\n\n\n
While the funds were secured, the pursuit of the hacker was in full swing. Sun’s ultimatum to the hacker was clear: return the stolen funds within a week. Although the hacker missed this deadline, it’s speculated that negotiations were ongoing, with the hacker possibly seeking assurances against prosecution.<\/p>\n\n\n\n
As of yesterday afternoon, a significant development emerged. The stolen funds were fully restored to the exchange’s hot wallet, as evidenced by on-chain data. This return was corroborated by both security researcher ZachXBT and Sun. From my point of view, what’s intriguing is the sequence of transactions. The entire stolen amount was returned first, after which HTX transferred the promised bounty to the hacker. Sun remarked, “We have confirmed that the hacker has fully returned all funds, as promised, and we have also paid the hacker a white hat bonus of 250 ETH. The hacker made the right choice.”<\/p>\n\n\n\n