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 tracked the transfer of approximately 5,411.8 Ether into the controversial cryptocurrency mixer Tornado Cash. At the time of the transaction, the moved assets were valued at roughly $20.7 million.
This multi-million-dollar push followed a similar sequence executed just nine days earlier. During that previous burst, the same cluster of addresses moved approximately 2,834.6 Ether, valued at roughly $10.8 million, into the privacy protocol. Much like the later transaction, the October 22 transfer was preceded by a careful staging phase involving cross-chain transfers and decentralized exchange swaps designed to consolidate funds and obscure their origins before entering the mixer.
Neither of these recent financial movements bore the hallmarks of a panicked or hurried operator. Instead, security analysts noted that both bursts displayed the characteristics of a patient, calculated actor systematically testing liquidity parameters and compliance timing. The funds were meticulously parceled into standardized Tornado Cash deposit denominations—amounts that are relatively inexpensive to blend through the protocol while remaining intentionally burdensome for blockchain forensic investigators to trace across public ledgers.
How the Radiant Hack Unfolded
The origins of this protracted money-laundering campaign trace back to Oct. 16, 2024. On that date, Radiant Capital suffered a catastrophic security breach that saw its lending pools on the Arbitrum layer-2 network and the BNB Chain completely drained. Initial 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 vector of attack: an operational compromise centered on keyholders and transaction approvals.
According to security analyses, the exploit relied on manipulating human elements within the project’s governance structure, ultimately allowing an attacker to push malicious transactions through a multi-signature process. Cybersecurity investigators detailed how authorized signers were effectively induced into approving unauthorized calls. At the time of the incident, Radiant utilized a three-out-of-eleven threshold scheme for authorizing sensitive administrative actions. While this broad set of keyholders theoretically improved operational availability and decentralization, it simultaneously widened the overall attack surface, making the project more vulnerable to sophisticated device compromises and targeted social engineering vectors.
Comprehensive post-incident reports reconstructed the precise mechanisms by which compromised approvals and faulty device hygiene created narrow windows of opportunity that the attacker ruthlessly exploited. Radiant’s own official incident updates gradually refined the operational timeline and the final accounting of the scale of the theft. Subsequent investigative reporting strongly suggested that a state-backed advanced persistent threat group utilized sophisticated impersonation tactics to gain unauthorized access to signer environments—a claim that project representatives later echoed as the initial panic subsided.
CryptoSlate closely covered the broader market fallout from the incident through the lens of emerging criminal trends. A prominent market report published in the wake of the breach noted that total exploit losses across the decentralized finance sector for October 2024 fell to approximately $116 million. Remarkably, the Radiant Capital incident alone accounted for nearly half of that entire monthly figure, placing an outsized share of industry financial pain into a single catastrophic event.
This framing remains crucial for understanding the systemic risk profile of the broader cryptocurrency market. It demonstrates how a single, well-executed cross-chain breach can profoundly distort a given month’s security metrics and sentiment data, even during periods when the rest of the decentralized finance ecosystem appears relatively calm and secure.
Over the subsequent twelve months, the post-hack activity established a clear, predictable pattern that culminated in the recent mixer deposits. Stolen funds were progressively moved away from layer-2 scaling solutions and funneled back onto the Ethereum mainnet via cross-chain bridges, capitalizing on the deepest available market liquidity. Decentralized exchange swaps were then utilized to consolidate fragmented token balances cleanly into Ether, establishing the optimal inventory required for efficient entry into Tornado Cash.
The transactions flagged by blockchain security firm CertiK on October 22 and 23, 2025, provided a transparent textbook example of this operational playbook. CertiK identified approximately 2,834.6 Ether entering Tornado Cash, noting that a significant portion—about 2,213.8 Ether—had arrived via the Arbitrum bridge from a specific externally owned account, while the remainder was sourced from the conversion of stablecoins like DAI.
The subsequent Oct. 31 burst added another 5,411.8 Ether to the running total, utilizing identical modular deposit sizes that matched the standard pool norms of the privacy mixer. Because the underlying blockchain ledger is entirely public, the digital route remains completely predictable; the economic incentives built into the system simply encourage patience over spectacle.
What the New Laundering Bursts Reveal
The steady stream of mixer activity observed recently reads less like a panicked, singular exit strategy and more like a deliberate, slow-bleed approach to asset liquidation. Bridge hops originating from Arbitrum or BNB Chain successfully transport fragmented balances directly into the deepest liquidity pools on the Ethereum mainnet. Subsequent decentralized exchange rotations lock the financial inventory firmly into Ether, ensuring the most seamless and efficient entry into Tornado Cash pools.
By batching these transfers into standard, uniform denominations, the operator effectively fractures the public transaction graph into countless isolated fragments that require substantial computational power and manual analysis to stitch back together. Despite these sophisticated obfuscation efforts, corporate compliance teams and blockchain forensics firms retain significant visibility. Investigators routinely cluster related addresses by analyzing shared gas consumption patterns and transaction timing, correlating specific deposits with corresponding withdrawal windows, and monitoring for telltale peel chains that begin with small transfers, fan out widely, and eventually re-aggregate near a designated target exchange or liquidity venue.
This ongoing cat-and-mouse dynamic persists within a pragmatic legal and regulatory environment that rewards strategic caution. Over recent years, various court rulings have notably narrowed the scope of government theories regarding the legal sanctioning and criminalization of decentralized open-source software. Federal prosecutors have experienced both notable victories and defeats across multiple high-profile legal battles concerning cryptocurrency mixing protocols and developer liability.
The resulting legal landscape occupies a complex gray zone where privacy-enhancing software tools continue to function, and centralized cryptocurrency exchanges increasingly rely on behavior-driven risk controls rather than blanket administrative labels. Independent forensic investigations continue to successfully intercept and flag illicit exits, shifting the primary friction point from immutable software code to procedural compliance and institutional monitoring.
For everyday users and protocol developers alike, the overarching lesson remains deeply concrete: foundational design choices carry profound financial consequences. Cross-chain bridges and routing protocols inherently concentrate immense value alongside centralized failure modes, which precisely explains why modern exploiters consistently rely on them during their exit strategies. Multi-chain decentralized applications require robust operational muscle memory—including automated emergency halts, immediate allowlist modifications, and rapid liquidity snapshots—rather than ad hoc improvisation during the chaotic hours immediately following a security breach.
Radiant Capital’s historical documentation reflects how its internal emergency response mechanisms gradually tightened over time, though the financial costs of that steep learning curve were severe, largely because the attacker maintained the strategic initiative throughout the assault. The ongoing flows of capital currently making their way through Tornado Cash represent the final tail of that exact statistical distribution.
The malicious operator continues moving funds simply because the underlying blockchain rails remain operational. Industry experts maintain that the appropriate defensive response involves hardened keyholder security procedures, significantly narrower administrative approvals, real-time cross-chain bridge monitoring, and an organizational culture that treats signer private keys with the utmost security protocols.
As conditions currently stand, the Radiant exploiter is expected to continue deploying this exact playbook until external circumstances shift. Additional deposits into Tornado Cash in familiar quantities will likely materialize over time, accompanied by supplementary bridge activity originating from addresses previously linked to the October 2024 attack paths. Eventually, a successfully laundered portion of the funds will inevitably ping a regulated trading venue, prompting compliance desks to weigh transaction timing and behavioral heuristics against user onboarding narratives.
The broader market consequence of these sustained operations remains predictable. Each patient, methodical exit diminishes institutional confidence in cross-chain abstractions, compelling development teams to rigorously audit not just their smart contract code, but their entire operational framework. Retail users continually chase lucrative yields across disparate blockchain networks because the user experience feels effortless, yet the most sophisticated threat actors remain acutely aware of where those cross-chain seams are hidden.




