Home / Blockchain Hacks & Exploits / Radiant Capital Exploiters Launder Millions Through Tornado Cash in Calculated Exit Strategy

Radiant Capital Exploiters Launder Millions Through Tornado Cash in Calculated Exit Strategy

The perpetrators behind the devastating October 2024 exploit of Radiant Capital have continued their systematic laundering operations, funneled through privacy protocol Tornado Cash. On October 31, 2025, blockchain intelligence tracked a massive transfer of approximately 5,411.8 Ether, worth roughly $20.7 million, into the privacy-preserving mixer.

This latest substantial movement followed a similar transaction just nine days prior, when the same cluster of addresses moved approximately 2,834.6 Ether, valued at roughly $10.8 million. Before reaching the mixer, those funds were meticulously staged across multiple blockchain networks and routed through decentralized exchanges to consolidate balances and obscure transaction paths.

Neither of the recent laundering bursts appeared rushed or panicked. Instead, blockchain security analysts observed that both operations resembled the behavior of a careful, calculated operator testing current liquidity depths and compliance timing. The funds were consistently parceled into standard, common Tornado denominations—a method designed to make the assets inexpensive to blend while ensuring they remain frustratingly difficult and resource-intensive for investigators to trace through the public ledger.

How the Radiant Hack Unfolded

The origins of this ongoing saga trace back to October 16, 2024, a dark day for the decentralized finance ecosystem when Radiant Capital’s lending pools operating on Arbitrum and the BNB Chain were aggressively drained. Estimates placed the total losses between $50 million and $58 million. Early technical post-mortems conducted by various blockchain security firms quickly converged on a simple yet devastating vulnerability at the heart of the project’s governance architecture.

The breach was ultimately attributed to a sophisticated operational compromise involving keyholders and approval mechanisms. This critical flaw allowed an attacker to push malicious transactions directly through a multi-signature process. Security researchers and auditors detailed how individual signers were psychologically induced or manipulated into approving incorrect or unauthorized calls.

At the time of the incident, Radiant utilized a three-out-of-eleven governance scheme for sensitive administrative actions. While this broad set of signers was ostensibly designed to improve operational availability and prevent single points of failure, it inadvertently widened the attack surface, making the project more vulnerable to device compromises and targeted social engineering campaigns. Comprehensive post-incident analysis from firms like Halborn successfully reconstructed the exact mechanism by which approvals and compromised device hygiene created narrow windows of opportunity that the attacker ruthlessly exploited. Radiant’s own subsequent incident updates helped fix the timeline and establish the true scale of the breach.

Later intelligence and investigative reporting suggested that a state-backed threat group may have orchestrated the operation, utilizing advanced impersonation tactics to gain unauthorized access to critical administrative keys—a claim that Radiant leadership frequently echoed as the initial panic settled across the decentralized finance community.

CryptoSlate extensively covered the fallout of the incident at the time, framing the disaster through a broader crypto crime trend lens. A prominent report published shortly after the breach noted that October 2024’s total exploit losses fell to approximately $116 million across the industry. Crucially, the Radiant incident accounted for nearly half of that entire monthly figure, placing an outsized and devastating share of the financial pain squarely onto a single project and its user base.

That contextual framing remains vital because it demonstrates how a single, well-executed cross-chain breach can profoundly distort and impact an entire month’s risk profile for the broader digital asset sector, even during periods when the rest of the market environment appears relatively calm and stable.

What followed over the subsequent year established the precise pattern of behavior that is clearly visible today. Stolen funds were systematically moved out of Layer 2 scaling networks and systematically bridged back to the Ethereum mainnet, where market liquidity is deepest and most accommodating for large-scale liquidations. Strategic decentralized exchange swaps consolidated fractured balances cleanly into Ether, setting the stage for efficient entry into mixing protocols.

The tranche of transactions recorded between October 22 and October 23, 2025, provided a textbook example of this methodology in action. Prominent blockchain security firm CertiK formally flagged 2,834.6 Ether entering Tornado Cash deposits, noting specifically that 2,213.8 Ether 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 burst of activity on October 31 increased the running total by another 5,411.8 Ether, utilizing the same modular deposit sizes that perfectly match established Tornado pool norms. Because the blockchain is entirely public, the laundering route is remarkably predictable, driven by economic incentives that reward patience, operational security, and methodical execution over flashy spectacle.

What the New Laundering Bursts Reveal

The recent mixer activity reads much more like a slow, deliberate bleed strategy rather than a hurried, single-event exit. Bridge hops originating from Arbitrum or the BNB Chain effectively ferry disparate balances into the deepest liquidity pools on the Ethereum mainnet. Decentralized exchange rotations then lock in the inventory in the form of native Ether, ensuring the most frictionless entries possible into Tornado Cash.

Batching transactions into standardized denominations systematically fractures the transparent public transaction graph into countless isolated fragments that are computationally costly and time-consuming for compliance teams to stitch back together. Despite these hurdles, blockchain intelligence and compliance teams still maintain significant visibility. Analysts routinely cluster addresses around shared gas usage patterns and timing heuristics, meticulously match specific deposits to corresponding withdrawal windows, and watch closely for telltale peel chains that begin with small amounts, fan out widely, and eventually re-aggregate near a designated target venue.

The current regulatory and legal posture across the industry remains distinctly pragmatic, as the broader legal environment has increasingly rewarded moderation. Federal courts have notably narrowed the government’s broadest legal theories regarding the outright sanctioning of decentralized software code. Prosecutors have experienced a mixed series of courtroom victories and defeats in 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 compliance controls rather than blanket address labeling. Comprehensive investigations still manage to catch illicit exits, but the primary friction has effectively shifted from software-level restrictions to operational enforcement and investigative processes.

For everyday users and smart contract builders, the ultimate lesson is entirely concrete: foundational design choices carry massive financial outcomes. Bridges and cross-chain routers inherently concentrate value alongside systemic failure modes, which explains precisely why sophisticated exploiters consistently rely on them during their exit strategies. Multi-chain applications require institutional-grade muscle memory for emergency halts, allowlist flips, and real-time liquidity snapshots, rather than relying on ad hoc improvisation during the chaotic hour immediately following a security breach.

Radiant’s historical documentation demonstrates how the project’s internal incident response tightened progressively over time. However, the financial costs of that steep learning curve were painfully real because the attacker held the operational initiative from the very beginning. The ongoing capital flows currently observable through Tornado Cash represent the final tail of that exact same statistical distribution.

The operator continues moving assets simply because the underlying infrastructure of the multi-chain ecosystem continues to operate without systemic interruptions. The appropriate industry response remains hardened keyholder management procedures, narrower administrative approvals, continuous real-time bridge monitoring, and an internal organizational culture that treats signer private keys like absolute crown jewels.

The Radiant exploiter will likely continue employing this exact playbook until macroeconomic or regulatory conditions shift significantly. Additional Tornado deposits will undoubtedly arrive in familiar sizes, and further bridge activity will likely emerge from addresses historically linked to the October 2024 exploit paths. Eventually, a clean exit will ping a regulated venue, forcing compliance desks to weigh rigid timing and heuristics against user narratives.

The broader consequence for the wider cryptocurrency market remains entirely predictable. Every patient, methodical exit of this nature chips away at user confidence in cross-chain abstractions, ultimately forcing development teams to audit not just their smart contract code, but their fundamental operational security. While everyday users enthusiastically chase attractive yields across disparate blockchain networks because the user experience feels seamless, the most skilled threat actors understand with absolute precision exactly where those seams are hidden.

Tagged: