Nearly a year and a half after a devastating multi-million-dollar breach crippled Radiant Capital, the perpetrators behind the exploit are continuing a slow and calculated process of laundering their ill-gotten gains. On Oct. 31, 2025, blockchain intelligence tracked the transfer of approximately 5,411.8 Ether to the privacy-enhancing protocol Tornado Cash. Valued at roughly $20.7 million at the time of the transaction, the substantial movement underscored the persistent and methodical approach hackers often take to obscure the origins of stolen digital assets.
This latest development follows a similar tranche moved just nine days prior. On that occasion, the same cluster of addresses shifted approximately 2,834.6 ETH—equivalent to $10.8 million—following an intricate series of cross-chain staging maneuvers and token swaps designed to prepare the capital for the mixing process.
Neither of these recent bursts appeared hurried or panicked. Instead, both operations exhibited the traits of a careful, experienced market operator testing liquidity depths and compliance timing. The funds were meticulously parceled into common Tornado Cash denominations, a strategy that minimizes the costs of blending funds while maximizing the friction required for blockchain investigators to trace the transaction paths effectively.
How the Radiant Hack Unfolded
To understand the significance of these ongoing laundering movements, one must look back at the origins of the breach. The crisis surrounding Radiant Capital began on Oct. 16, 2024, when the decentralized finance project’s lending pools operating on the Arbitrum and BNB Chain networks were systematically drained. Losses were initially estimated between $50 million and $58 million. Early technical post-mortems conducted by various blockchain security firms quickly converged on a simple yet devastating operational failure.
Rather than a flaw in the fundamental smart contract logic, the breach stemmed from an operational compromise involving keyholders and transaction approvals. This compromise allowed an unauthorized attacker to push malicious transactions through a multi-signature process. Security researchers detailed how authorized signers were social-engineered or otherwise induced to approve incorrect calls, effectively granting the bad actors the permissions they needed to hollow out the protocol’s liquidity pools.
At the time of the incident, Radiant utilized a three-out-of-eleven threshold scheme for sensitive administrative and protocol actions. While this broad set of signers was designed to improve operational availability and decentralization, it simultaneously widened the attack surface, increasing vulnerability to device compromises and sophisticated social engineering campaigns. Detailed analyses from security firms such as Halborn reconstructed how specific approvals and lax device hygiene created narrow windows of opportunity that the attacker ruthlessly exploited. Radiant’s own incident updates gradually refined the official timeline and scale of the attack as investigations progressed.
Subsequent reporting and security intelligence suggested that a state-backed hacker group may have utilized advanced impersonation tactics to gain the necessary access, a narrative that Radiant leadership echoed as the crypto community processed the aftermath.
CryptoSlate covered the extensive fallout through the lens of broader crime trends. A retrospective report published at the time noted that October’s total exploit losses across the broader cryptocurrency ecosystem fell to approximately $116 million. Notably, the Radiant incident accounted for nearly half of that monthly figure, concentrating an outsized share of the industry’s financial pain into a single catastrophic event.
This framing remains crucial because it highlights how a single cross-chain breach can profoundly distort a given month’s risk profile, even during periods when the macroeconomic or general security environment appears relatively calm.
The events that unfolded over the subsequent year established the predictable pattern visible in the recent blockchain data. Stolen funds were progressively moved out of Layer 2 networks and routed back to Ethereum mainnet via cross-chain bridges, where market liquidity is deepest and most accommodating for large-scale liquidations. Decentralized exchange swaps were then utilized to consolidate fragmented balances entirely into Ether, preparing the inventory for the most efficient entry into privacy mixers.
The transactions flagged between Oct. 22 and 23, 2025, provide a clear case study of this playbook. Blockchain security firm CertiK flagged 2,834.6 ETH flowing into Tornado Cash deposits, noting that 2,213.8 ETH of that total had arrived via the Arbitrum bridge from a specific externally owned account, with the remainder sourced from stablecoin conversions.
The subsequent Oct. 31 burst expanded the running total by another 5,411.8 ETH, utilizing modular deposits that precisely matched standard Tornado pool norms. Because the blockchain is public, the overarching route remains entirely predictable, relying on economic incentives that favor patience and methodical execution over rapid, high-visibility movements.
What the New Laundering Bursts Reveal
The recent mixer activity reads much more like a slow bleed strategy than a frantic exit. Bridge hops originating from Arbitrum or BNB Chain funnel balances directly into the deepest liquidity pools on the Ethereum mainnet. Decentralized exchange rotations establish the inventory in native ETH assets, ensuring seamless and efficient entry into Tornado Cash vaults.
By batching these funds into standard, uniform denominations, the operator fractures the public transaction graph into countless isolated fragments that are computationally costly and time-consuming for analysts to stitch back together. Nevertheless, compliance teams and blockchain forensics units retain significant visibility despite these obfuscation tactics. Investigators routinely cluster related addresses around shared gas usage patterns and timing heuristics, match specific deposits to corresponding withdrawal windows, and monitor for telltale peel chains that begin with small transfers, spread wide across multiple wallets, and eventually re-aggregate near a target destination venue.
This cat-and-mouse posture remains pragmatic because the evolving legal and regulatory environment rewards pragmatism. Over recent years, court rulings have narrowed the government’s broadest regulatory and legal theories regarding the outright sanctioning of decentralized software and privacy tools. Prosecutors have experienced a mixed record of winning and losing various legal cases related to cryptocurrency mixers and developer liability.
The resulting landscape is a complex gray zone where privacy-preserving tools continue to function, and centralized exchanges increasingly rely on behavior-driven monitoring controls rather than simple, blanket labels. While sophisticated investigations still successfully catch and flag illicit exits, the primary friction has largely shifted from the underlying software code to the administrative and compliance processes of regulated platforms.
For developers and everyday users, the underlying lesson is stark and concrete: structural design choices carry profound financial consequences. Bridges and cross-chain routers inherently concentrate both value and failure modes, which is precisely why exploiters target them when moving capital out of compromised ecosystems. Multi-chain applications require established operational muscle memory—including predefined protocols for emergency halts, allowlist flips, and rapid liquidity snapshots—rather than ad hoc improvisation during the chaotic hours immediately following a breach.
Radiant’s official documentation and post-incident communications demonstrated how the project’s defensive response tightened over time. However, the costs of that steep learning curve were severe because the attacker maintained the initiative from the outset. The current flows observed moving through Tornado Cash represent the lingering tail of that exact distribution.
The operator continues to move funds because the underlying financial rails continue to operate. Mitigating these risks requires hardened keyholder procedures, narrower and more restrictive approval parameters, real-time bridge monitoring systems, and an internal culture that treats signer devices with the utmost security.
The Radiant exploiter will likely continue employing this established playbook until market conditions or enforcement mechanisms fundamentally change. Additional Tornado deposits in familiar, modular sizes are expected to appear over time, accompanied by further bridge activity originating from addresses linked to the original October 2024 transaction paths. Eventually, a clean exit will likely attempt to ping a regulated venue, where compliance desks will carefully weigh transaction timing and behavioral heuristics against customer narratives.
The broader consequence for the digital asset market remains entirely predictable. Every patient, methodical exit of this nature chips away at user and institutional confidence in cross-chain abstractions, forcing development teams to audit not only their smart contract code but their day-to-day operational security as well. As everyday users eagerly chase yield across interconnected networks because the user experience feels seamless, sophisticated threat actors remain acutely aware of where those structural seams are hidden.






