Ethereum Theft Continues: Hacker Moves Over $230 Million After WazirX Exchange Attack

  • The cryptocurrency exchange WazirX recently experienced a significant security breach involving $230 million in stolen assets.
  • This breach, which occurred in July, continues to affect the industry as stolen funds remain in circulation.
  • On-chain analysis indicates that hackers have been moving large amounts of Ethereum through Tornado Cash.

Discover the latest developments on the WazirX hack and how it’s impacting the cryptocurrency market.

Details of the $230 Million WazirX Security Breach

In July, WazirX suffered a severe hacking incident that led to the theft of over $230 million in various cryptocurrencies. This attack primarily targeted one of the exchange’s multi-signature wallets, exploiting a vulnerability that allowed the hackers to siphon off the funds. Most of the stolen assets included over $100 million in Shiba Inu (SHIB) and $52 million in Ethereum (ETH).

Continuous Movement of Stolen Funds

Recent data reveals that the perpetrators have been actively moving portions of the stolen Ethereum. This week alone, they’ve transferred 15,000 ETH in three separate transactions. As of Thursday morning, an additional 5,000 ETH was moved to Tornado Cash, a service that obfuscates transaction details to enhance privacy.

According to Arkham, an on-chain analysis platform, the hackers’ wallet still contains over $50 million in various tokens, predominantly Ethereum. This demonstrates that a substantial portion of the misappropriated assets remains under their control.

Implications for WazirX and the Broader Crypto Market

The implications of this breach are far-reaching, affecting both WazirX and the broader cryptocurrency community. The stolen funds accounted for more than 45% of WazirX’s total reserves as reported in their June 2024 financial statement. Consequently, the exchange has been undergoing extensive restructuring to address its financial liabilities.

Disputes Over Responsibility and Control

The fallout from the attack has also led to significant disputes over responsibility. Nischal Shetty, the founder of WazirX, initially blamed the security lapse on Liminal, the firm entrusted with asset custody. Liminal refuted these allegations. Later, Shetty claimed that Zettai Labs, the parent company of WazirX, had most of its funds managed by Binance, limiting WazirX’s ability to reimburse affected users.

Binance countered these claims, asserting that it never owned, controlled, or managed WazirX. Binance emphasized that their association did not extend to involvement in WazirX’s operations or the incident in question.

Conclusion

In summary, the WazirX hacking incident underscores significant vulnerabilities and challenges within the cryptocurrency sector. As hackers continue to move large sums through obfuscation services, the need for robust security measures and transparent operations becomes increasingly critical. Stakeholders within the crypto community must remain vigilant and proactive to safeguard against such attacks and maintain trust in digital asset markets.

Don't forget to enable notifications for our Twitter account and Telegram channel to stay informed about the latest cryptocurrency news.

BREAKING NEWS

Zetachain Listed on Coinbase Spot Exchange

**Zetachain Listed on Coinbase Spot Exchange** Zetachain has officially been...

Consensys’ Lawsuit Against SEC Over Ethereum Dismissed

**Consensys' Lawsuit Against SEC Over Ethereum Dismissed** In a significant...

Terraform Labs Secures Approval for Bankruptcy Completion in Settlement with SEC

Terraform Labs has received approval to finalize its bankruptcy...

Judge Failla Postpones Pre-Trial Conference in SEC vs. Coinbase Case to March 2025

**Judge Failla Delays Pre-Trial Conference in SEC vs. Coinbase...

Decentraland Restores Stolen X Account, Warns Against Fake Airdrops

On September 20, Decentraland, a leading Metaverse platform, announced...
spot_imgspot_imgspot_img

Related Articles

spot_imgspot_imgspot_imgspot_img

Popular Categories

spot_imgspot_imgspot_img