Victim of Hack Worth 90 ETH Gets Hacker’s USDT Address Blacklisted

In a significant development in the world of cybersecurity, a victim of a hack worth 90 Ether (ETH) has successfully managed to get the attacker’s Tether (USDT) address blacklisted. With the help of law enforcement agencies and cyber authorities, this victim, who goes by the name L3yum on X (formerly Twitter), took a step towards justice after their hot wallet was compromised on March 16th. This article explores the details of the hack, the stolen assets, the blacklisting of the USDT address, and the potential for reimbursement.

Victim’s hot wallet compromised

The unfortunate incident occurred on March 16 when the hacker managed to get a hold of L3yum’s hot wallet seed phrase, granting them access to drain the victim’s wallet. The details of how the hacker obtained the seed phrase remain unknown. This breach allowed the attacker to carry out their malicious actions, resulting in significant losses for the victim.

Stolen assets

As a consequence of the hack, several high-value nonfungible tokens (NFTs) related to Yuga Labs, as well as cryptocurrencies and other NFTs from smaller projects, were stolen from L3yum’s wallet. The attacker promptly sold or exchanged these stolen assets, further compounding the victims’ losses.

USDT address blacklisted

The victim took to X on August 11 to highlight a major breakthrough in their fight against the hacker. L3yum revealed that the attacker’s Ethereum-based USDT address had been successfully blacklisted. By blacklisting the address, it effectively blocks any further activity related to that specific address, making it more challenging for the hacker to exploit their ill-gotten gains.

Value and Reimbursement

The hacked wallet contained an estimated 90 ETH, which, at the time of writing, is equivalent to roughly $166,000. Additionally, the blacklisted USDT address was found to be holding around $107,306 worth of USDT. The question of whether the victim will be reimbursed for their losses remains uncertain at this point.

Previous reimbursement cases

Fortunately, in previous instances where a USDT address has been blacklisted under similar circumstances, victims have been reimbursed. Tether, the issuer of USDT, has taken steps to burn the blacklisted USDT and reissue equal amounts of the asset to the original owner. However, it is worth noting that Tether typically takes such actions after a court order has been issued, ensuring legal grounds for the reimbursement.

Reimbursement status

When questioned about the reimbursement prospects in the comments, L3yum indicated that the likely path forward involves a court order, though it has not been confirmed yet. This suggests that the victim’s case is progressing in a positive direction, with the potential for reclaiming the stolen assets.

Methods of Seed Phrase Compromise

As investigators dig deeper into this case, the exact method by which the hacker obtained the seed phrase back in March remains uncertain. Establishing how this breach occurred is crucial not only for the victim but also for enacting effective preventive measures within the cryptocurrency ecosystem.

The successful blacklisting of the attacker’s USDT address marks a significant milestone in the victim’s quest for justice and recovery. With the aid of law enforcement agencies and cyber authorities, L3yum has taken concrete steps to ensure that the attacker’s activities are curtailed. While the stolen assets, including NFTs, have not yet been fully recovered, there is hope for reimbursement through Tether’s process of burning blacklisted USDT addresses. As the investigation into the method of seed phrase compromise continues, it underscores the ongoing need for heightened security measures within the cryptocurrency space to safeguard users from such hacks and breaches.

Explore more

Broadcom vs. AMD: Who Is Winning the AI Chip Sector Race?

The global race for artificial intelligence supremacy has fundamentally transformed the once-predictable world of silicon manufacturing into a high-stakes arena where trillion-dollar valuations hang on the efficiency of a single transistor. This silicon-centric revolution has redefined the semiconductor landscape, shifting the focus from standard processing units to the complex networking and custom hardware required to sustain massive model training. Broadcom

Global Governments Shift From Windows to Linux Systems

The familiar startup chime of Microsoft Windows has echoed through the corridors of power from Paris to Beijing for decades, but that ubiquitous sound is being replaced by the silent efficiency of the Linux kernel. This transition marks a profound departure from the long-standing software monoculture that once defined the digital operations of global bureaucracies. For years, public administrations accepted

How to Pay Employees in a Small Business: A 5-Step Guide

Full Payment Submissions must reach HM Revenue and Customs on or before each payday to avoid the penalties associated with real-time information reporting violations. Transitioning from a solo operation to a multi-person enterprise involves a significant shift in administrative responsibility, especially for those managing complex logistics and international supply chains. In the current economic landscape of 2026, small business owners

Optimizely Debuts AI Virtual Teammates to Automate Marketing

Marketing departments across the globe are rapidly transitioning away from using artificial intelligence as a simple text generator toward integrating it as a sophisticated, autonomous colleague capable of independent thought. This fundamental shift signals a departure from AI as a reactive tool that simply waits for a human prompt to a proactive digital coworker that understands organizational context. At the

How Did a Poisoned NPM Package Bypass Modern Security?

The digital foundations of modern software development were shaken to their core on August 28, 2026, when a highly trusted utility for automating API integrations became the delivery vehicle for a predatory supply-chain attack. For years, the developer community operated under a collective consensus that high-volume, well-maintained packages provided a layer of inherent security through sheer visibility. This consensus was