18 Nov 2026, Wed

Radiant Capital Exploiter Moves $20.7M in ETH to Tornado Cash in Ongoing Laundering Campaign

More than a year after suffering a devastating multi-million dollar exploit, the perpetrator behind the Radiant Capital attack continues to methodically launder stolen funds. On Oct. 31, 2025, the Radiant exploiter transferred approximately 5,411.8 Ether to Tornado Cash, a privacy-focused mixing protocol, in a move valued at roughly $20.7 million.

The transaction was not an isolated event. Just nine days earlier, the exact same cluster of addresses had moved approximately 2,834.6 ETH, equivalent to $10.8 million, following a complex sequence of cross-chain staging and token swaps designed to obscure the trail before interacting with the mixer.

Neither of the recent capital transfers appeared rushed or panicked. Instead, both bursts exhibited the hallmarks of a careful, disciplined operator testing market liquidity and compliance timing. The funds were meticulously parceled into common Tornado Cash denominations, an approach that minimizes blending costs while maximizing the difficulty of forensic tracing. This calculated drip of capital highlights the persistent challenges law enforcement and blockchain analytics firms face when dealing with sophisticated threat actors who possess both the patience and the capital to wait out market scrutiny.

How the Radiant Hack Unfolded

To understand the current movement of funds, it is necessary to examine the origins of the breach. The Radiant Capital incident began on Oct. 16, 2024, when the cross-chain lending protocol’s liquidity pools deployed across Arbitrum and BNB Chain were drained of an estimated $50 million to $58 million. Early technical post-mortems conducted by various blockchain security firms quickly converged on a simple yet devastating conclusion: the breach was the result of an operational compromise rather than a traditional smart contract vulnerability.

The attackers leveraged compromised keyholders and manipulated approvals to push malicious transactions through the protocol’s multi-signature authorization process. Subsequent security analyses, including reports from firms like Halborn, detailed how key signers were socially engineered or otherwise induced to approve erroneous calls. At the time of the exploit, Radiant utilized a three-out-of-eleven threshold scheme for sensitive administrative actions. While this broad set of signers was originally implemented to ensure high availability and decentralization, it inadvertently widened the attack surface, creating critical windows of vulnerability that the exploiter ruthlessly exploited through device compromise and advanced impersonation tactics. Later industry reporting suggested that a state-backed hacker group was behind the operation, a hypothesis that Radiant leadership echoed as the initial shock subsided.

The scale of the incident sent immediate shockwaves through the decentralized finance ecosystem. CryptoSlate covered the fallout at the time through a crime trend analysis, noting that October 2024’s total exploit losses fell to approximately $116 million. Radiant’s single incident accounted for nearly half of that monthly figure, placing an outsized share of industry pain onto a single project. This framing remains vital because it demonstrates how a single, well-executed cross-chain breach can profoundly distort a monthly risk profile, even during periods when the broader macroeconomic and regulatory environment appears relatively calm.

In the months following the exploit, the stolen assets followed a predictable trajectory across multiple blockchain layers. Funds were progressively shifted out of Layer 2 networks and routed back to Ethereum mainnet via cross-chain bridges, where protocol liquidity is deepest and most capable of absorbing large transactions. Once on mainnet, decentralized exchange swaps consolidated fragmented balances into native ETH, laying the necessary groundwork for the eventual mixing process.

The transactions recorded on October 22 and 23, 2025, provided a clear blueprint of this behavior. Blockchain security firm CertiK flagged 2,834.6 ETH in Tornado Cash deposits during that window, noting that 2,213.8 ETH had arrived via the Arbitrum bridge from an externally owned account, with the remainder sourced from decentralized conversions of DAI stablecoins. The subsequent October 31 burst added another 5,411.8 ETH to the running total, utilizing modular deposit sizes that matched standard Tornado pool norms. Because the blockchain is fundamentally public and the routing mechanics are transparent, the operator relies on patience and structural predictability rather than speed to achieve their goals.

What the New Laundering Bursts Reveal

The recent mixer activity reads much more like a slow, deliberate bleed strategy than a hurried attempt at a clean exit. Bridge hops originating from Arbitrum or BNB Chain successfully funnel dispersed balances into the deepest liquidity pools on the Ethereum mainnet. Meanwhile, decentralized exchange rotations establish the exact inventory of ETH required for the most efficient entries into Tornado Cash.

By batching these funds into standard denominations, the operator fractures the public transaction graph into countless smaller fragments that are exceptionally costly and time-consuming for analysts to stitch back together. Despite these sophisticated obfuscation tactics, compliance and blockchain intelligence teams still retain substantial visibility. Investigators routinely cluster related addresses by analyzing shared gas usage patterns and timing heuristics, matching deposit volumes to specific withdrawal windows, and monitoring for telltale peel chains that begin with small transfers, fan out widely, and eventually re-aggregate near a target destination venue.

This cat-and-mouse dynamic exists within a complex and shifting legal landscape. Courts in various jurisdictions have gradually narrowed the government’s broadest legal theories regarding the outright sanctioning of autonomous, decentralized software code. Prosecutors have secured victories in some mixer-related litigation while suffering notable setbacks in others, creating a persistent regulatory gray zone. Within this environment, privacy tools continue to function, and centralized exchanges increasingly rely on behavior-driven risk controls rather than blanket administrative labels. While sophisticated chain investigations still manage to catch illicit exits as they hit regulated endpoints, the friction for bad actors has largely shifted from software engineering to operational process.

For builders and everyday users in the decentralized finance space, the lessons of the Radiant exploit are concrete and unavoidable. Architectural design choices invariably carry direct financial consequences. Cross-chain bridges and multi-chain routers inherently concentrate value alongside critical failure modes, which is precisely why exploiters target them as primary escape routes. Modern multi-chain applications require institutional-grade operational muscle memory—including the ability to execute emergency halts, instantly flip allowlists, and take immediate liquidity snapshots—rather than relying on ad hoc improvisation during the chaotic hour following a security breach.

Radiant Capital’s own documentation illustrates how the project’s incident response procedures tightened over time, though the financial costs of that steep learning curve were borne entirely by the protocol and its users. The current asset flows winding their way through Tornado Cash represent the long tail of that exact same distribution curve. The operator continues to move capital simply because the underlying infrastructure of the multi-chain ecosystem remains operational. For the broader industry, the appropriate defensive response demands hardened keyholder procedures, narrower administrative approvals, real-time bridge monitoring, and an organizational culture that treats signer devices with the utmost security.

As conditions stand, the Radiant exploiter is likely to continue employing this patient playbook until external circumstances force a change. Additional Tornado deposits in familiar denominations will almost certainly arrive over time, accompanied by further bridge activity originating from addresses linked to the October 2024 exploit paths. Eventually, a portion of these laundered funds will attempt an exit to a regulated venue, where compliance desks will weigh transaction timing and behavioral heuristics against user narratives.

For the broader cryptocurrency market, the downstream consequences of such events are predictable. Every patient, successful exit diminishes overall user confidence in cross-chain abstractions, compelling development teams to audit not just their smart contract code, but their entire operational framework. Users naturally chase yield across disparate networks because the cross-chain user experience feels frictionless, but sophisticated threat actors understand precisely where those structural seams are hidden.

Leave a Reply

Your email address will not be published. Required fields are marked *