Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the multisite-clone-duplicator 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/wp-includes/functions.php on line 6114
[www-stage.newsbtc.com/news/new-report-two-million-ethereum-fee-fat-fingers-money-laundering/amp/]
[wp-includes/functions.php:6114 trigger_error(), wp-includes/functions.php:6054 wp_trigger_error(), wp-includes/l10n.php:1370 _doing_it_wrong(), wp-includes/l10n.php:1408 _load_textdomain_just_in_time(), wp-includes/l10n.php:194 get_translations_for_domain(), wp-includes/l10n.php:306 translate(), wp-content/plugins/multisite-clone-duplicator/include/lang.php:6 __(), wp-content/plugins/multisite-clone-duplicator/multisite-clone-duplicator.php:32 require_once('wp-content/plugins/multisite-clone-duplicator/include/lang.php'), wp-settings.php:471 include_once('wp-content/plugins/multisite-clone-duplicator/multisite-clone-duplicator.php'), wp-config.php:53 require_once('wp-settings.php'), wp-load.php:50 require_once('wp-config.php'), wp-blog-header.php:13 require_once('wp-load.php'), index.php:17 require('wp-blog-header.php')]

New Report: $2.5 Million Ethereum Fee is Neither Fat Fingers nor Money Laundering

New Report: $2.5 Million Ethereum Fee is Neither Fat Fingers nor Money Laundering

Unknown actors have paid over $5.6 million in Ethereum fees for sending out two transactions worth several hundred dollars

Ethereum

The two Ethereum transactions where senders paid millions of dollars in fees for transactions worth as little as $130 are widely believed to be blackmail. According to research from analytics company PeckShield, the hackers were reportedly blackmailing an unknown exchange by sending out transactions with exorbitant fees in order to circumvent the multi-signature security of the exchange and get away with the funds they stole through a phishing attack.

Over $5 Million Paid in Ethereum Transaction Fees

Earlier this week, separate transactions were sent on the Ethereum network that accrued over $5.6 million in fees for the mining pools that processed it. According to data from Etherscan, an unknown wallet sent out transactions worth just several hundred dollars, but paid tens of thousands of ETH in fees.

The news about the exorbitant Ethereum transaction fees spread fast through the crypto community, leading many to believe that it could be more than an honest mistake in which the sender switched the amount they wanted to send with the fee they wanted to pay. 

Many prominent voices in the industry noted that this could be a malicious act done by a hacker either to blackmail or cause another type of harm to a company. PeckShield, a blockchain analytics company based in China, believes that this is a classic case of blackmail, where the exorbitant Ethereum transaction fees were actually gas price ransomware attacks. 

What Most Likely Happened

According to PeckShield’s report, the “attacks” most likely began when an exchange’s hot storage fell victim to a phishing attack, in which hackers took over the company’s servers. However, as most exchanges have a private key that requires multi-signature verification, the hackers wouldn’t have been able to access its funds and transfer them to their own addresses. 

Instead, PeckShield researchers speculated, they realized that there was a group of addresses whitelisted by the exchange where funds could be sent without the need for multi-signature verification. By sending out minuscule transactions with exorbitant fees, the hackers were literally burning the exchange’s funds. According to ChainNews, this was most likely done in order to pressure the exchange to pay a ransom to the hackers. 

This, however, couldn’t last forever, as the address taken hostage by the hackers has a balance of 21,000 Ethereum. 

While certainly feasible, it’s important to note that this is still only a theory. PeckShield’s report didn’t identify the exchange they believe was affected, nor did they provide any other information about the hackers. 

Featured Image from Shutterstock
Exit mobile version