More than a year after orchestrating one of the most devastating decentralized finance exploits of late 2024, the hacker behind the Radiant Capital breach has continued to systematically launder stolen funds. On Oct. 31, 2025, blockchain intelligence tracks showed the Radiant exploiter transferred approximately 5,411.8 Ether to the privacy-focused mixing protocol Tornado Cash. Valued at roughly $20.7 million at the time of the transaction, the massive transfer marks yet another calculated step in an unhurried, methodical cashing-out process.
This latest movement follows a similar pattern observed just nine days prior. On October 22 and 23, 2025, the same cluster of addresses moved approximately 2,834.6 ETH, equivalent to $10.8 million, through the same mixer. Before routing the assets into Tornado Cash, the operator meticulously staged the funds across multiple blockchain networks and executed a series of decentralized exchange swaps to consolidate balances.
Neither of these recent financial bursts bore the hallmarks of a hurried or panicked actor trying to escape immediate detection. Instead, security analysts and on-chain investigators noted that both operations resembled a careful, seasoned entity testing liquidity depths, timing compliance monitoring windows, and parceling deposits into standard Tornado pool denominations. These predetermined amounts are inexpensive to blend within the protocol and purposefully designed to make downstream tracking tedious and annoying for compliance teams and law enforcement agencies.
How the Radiant Hack Unfolded
To understand the significance of these ongoing laundering operations, one must look back at the origins of the incident. The Radiant Capital exploit began on Oct. 16, 2024, when the cross-chain lending protocol suffered a catastrophic security failure. Attackers successfully drained lending pools operating across the Arbitrum and BNB Chain ecosystems, making off with an estimated $50 million to $58 million in user funds.
Early technical post-mortems conducted by various blockchain security firms quickly converged on a simple yet devastating vulnerability. Rather than a flaw in the fundamental smart contract logic, the breach was rooted in an operational compromise involving keyholders and multi-signature transaction approvals. Malicious transactions were successfully pushed through the protocol’s multi-sig administrative process because key-signing entities were reportedly induced into approving the wrong operational calls.
At the time, Radiant utilized a three-out-of-eleven threshold scheme for authorizing sensitive protocol actions. While this broad set of designated signers was intended to improve system availability and administrative responsiveness, it inadvertently widened the attack surface, increasing vulnerability to device compromise and sophisticated social engineering tactics. Detailed post-incident analysis from firms like Halborn reconstructed how targeted device hygiene lapses and manipulated approval workflows created narrow windows of opportunity that the attacker ruthlessly exploited. Radiant’s own subsequent incident updates gradually helped fix the precise timeline and ultimate financial scale of the disaster.
Later investigative reporting indicated that a state-backed threat group may have orchestrated the attack, utilizing advanced impersonation techniques to gain unauthorized access to signer environments—a hypothesis that Radiant leadership later echoed as the initial dust surrounding the protocol settlement began to settle.
CryptoSlate extensively covered the fallout at the time through a broader crypto crime trend lens. A prominent report published during the incident noted that total exploit losses across the decentralized finance sector for October 2024 plummeted to a six-month low of approximately $116 million. However, the Radiant incident alone accounted for nearly half of that entire monthly figure, concentrating an outsized share of industry pain into a single catastrophic event.
This framing remains crucial because it demonstrates how a single, highly coordinated cross-chain breach can profoundly skew an entire month’s risk profile for the broader digital asset economy, even during periods when the market environment otherwise appears calm and stable.
Over the subsequent year, the path of the stolen assets set a clear pattern that remains visible today. Funds were systematically moved away from Layer 2 scaling networks and bridged back to Ethereum mainnet, where market liquidity is deepest and most resilient. Subsequent token swaps consolidated fragmented balances into Ether to prepare the inventory for the most efficient possible entry into Tornado Cash.
The tranche of transactions recorded on October 22 and 23, 2025, provided a textbook example of this routine. Security firm CertiK flagged the movement of 2,834.6 ETH into Tornado deposits, noting that roughly 2,213.8 ETH of that total had arrived directly via the Arbitrum bridge from an externally owned account designated as 0x4afb, with the remaining balance sourced from prior conversions of DAI stablecoins.
The subsequent October 31 burst injected another 5,411.8 ETH into the mixing cycle, maintaining the exact modular deposit sizes that match standard Tornado pool norms. Because the blockchain ledger is entirely public, the route remains predictable, yet the underlying market incentives consistently reward patience over high-profile spectacle.
What the New Laundering Bursts Reveal
The recent mixer activity reads less like a panicked, singular exit strategy and more like a disciplined, slow-bleed campaign. Bridge hops originating from Arbitrum or BNB Chain successfully ferry accumulated balances into the highest-liquidity pools on the Ethereum mainnet. Decentralized exchange rotations then lock the treasury inventory securely into ETH, ensuring optimal efficiency upon entering Tornado Cash.
By batching these funds into standard, widely used denominations, the operator effectively fractures a clean public transaction graph into countless fragmented pieces that are computationally expensive and time-consuming to stitch back together. Despite these deliberate obfuscation tactics, specialized compliance and forensic teams still retain significant visibility. Investigators routinely cluster related addresses around shared gas spending patterns, specific timestamp windows, and telltale peel chains that characteristically start with small transfers, fan out widely across multiple intermediary wallets, and eventually re-aggregate near a designated final venue.
This cat-and-mouse posture remains pragmatic because the broader legal and regulatory environment continues to evolve. Recent court rulings have notably narrowed the scope of the government’s most expansive legal theories regarding the direct sanctioning of decentralized software code. Prosecutors have secured victories in some mixer-related proceedings while facing unexpected setbacks in others, highlighting an ongoing judicial learning curve.
The resulting landscape is a complex gray zone where privacy-preserving tools continue to function, and centralized exchanges increasingly rely on sophisticated, behavior-driven risk controls rather than blanket address labeling. Forensic investigations still manage to intercept illicit exits on regulated rails; the primary point of friction has merely shifted from software-level code restrictions to bureaucratic and procedural compliance processes.
For digital asset users, developers, and protocol architects, the overarching lesson is profoundly concrete: foundational design choices carry direct financial consequences. Bridges and cross-chain routers inevitably concentrate both systemic value and failure modes, which explains precisely why exploiters heavily rely on them during their exit strategies. Multi-chain applications require institutional-grade operational muscle memory—including emergency pause mechanisms, granular allowlist flips, and instant liquidity snapshots—rather than ad-hoc improvisation in the chaotic hours immediately following a security breach.
Radiant’s published post-incident documentation reflects how the project’s defensive response posture gradually tightened over time. Unfortunately, the real-world costs of that steep learning curve were severe, largely because the attacker maintained the initiative from the outset. The current ongoing fund flows through Tornado Cash represent the long tail of that exact same distribution curve.
The malicious operator continues to move assets because the underlying global financial and blockchain rails remain operational. The appropriate industry response requires hardened keyholder procedures, minimized contract approvals, real-time automated bridge monitoring, and an internal organizational culture that treats signer private keys with the same security reverence as crown jewels.
As conditions stand, the Radiant exploiter is likely to continue employing this tried-and-true playbook until market conditions or enforcement mechanisms shift. Additional Tornado deposits will undoubtedly arrive in familiar, predictable sizes. Further cross-chain bridge activity will likely materialize from addresses directly linked to the original October 2024 escape paths. Eventually, a cleaned tranche of capital will attempt to ping a regulated venue, prompting compliance desks to carefully weigh historical timing and behavioral heuristics against user narratives.
The broader consequence for the digital asset market remains entirely predictable. Every patient, methodical exit of this nature chips away at user confidence in cross-chain interoperability abstractions, forcing development teams to audit not just their smart contract code, but their core operational security as well. While retail users continually chase lucrative yields across disparate networks because the user experience feels seamless, the industry’s most sophisticated threat actors know with absolute precision where those structural seams are hidden.

