Binance Hack-Linked Wallet Shifts $142M in ETH Across Seven Transfers
A wallet associated with the Binance hack transferred $142 million in ETH across seven transactions, while another linked wallet converted stolen funds into bitcoin, continuing an ongoing money trail.

A wallet associated with the Binance hack transferred $142 million in ETH across seven separate transactions, according to a November 18, 2026 report by The Defiant. Additionally, a distinct linked wallet converted stolen funds into bitcoin on November 17, introducing another layer to the ongoing money trail.
This recent movement builds upon the fund-tracing efforts that followed the alleged October 29 theft. The ongoing recovery challenge for Binance and tracking teams now involves large ether movements, earlier bitcoin conversions, and the scattering of assets across multiple networks.
Binance Hack Wallets Move Ether in Large Batches
What Happened in the Seven-Transfer Movement?
The shifted ether amounted to $142 million. Meanwhile, a separate wallet tied to the November 17 transfers executed bitcoin swaps, resulting in two separate activities for investigators to track: the redistribution of ether and the conversion of assets through another address.
Read More: Binance Seeks ArbitrumDAO Release of Frozen ETH and ARB for Loss Reserves
The immediate focus centers on how the stolen capital is managed following the initial breach.
How Does the 60,000 ETH Movement Fit?
As reported by U.Today, Whale Alert identified 60,000 ETH moving across five transactions. Each transfer consisted of 12,000 ETH—valued between $21.75 million and $21.77 million—bringing the combined total to $108.78 million.
The originating wallet bore a Binance hack label. Because the recipient address showed no signs of a sale, this activity represents another major development in the investigation.
Binance, Whale Alert and the Alleged Attackers
Who Has Been Linked to the Original Theft?
Security organization Hacken attributes the October 29 incident to the North Korean group TraderTraitor. Their analysis outlines months of preparatory work aimed at Binance personnel and internal infrastructure, starting with compromised developer tools, moving to employee workstations, and eventually gaining access to the wallet signing service responsible for authorizing transfers.
This chain of access ultimately led to unauthorized requests reaching systems that manage transactions across 11 blockchains.
Which Organizations Are Following the Funds?
The breach was initially reported by Binance, while Whale Alert supplied the monitoring data for the five-transfer account. Furthermore, Elliptic’s broader tracing efforts, shared via Shattered, point to an operation encompassing more than 20,000 wallets, 16 blockchains, at least 36 services, and 65,000 transactions.
This scale highlights the complexity required to disperse stolen cryptocurrency. Multiple networks and services generate numerous paths to follow, including the conversion processes turning stolen tokens into bitcoin.
How the Alleged Binance Breach Reached Its Wallet Systems
What Happened Before October 29?
In June, a wallet infrastructure engineer downloaded a compromised version of Homebrew while searching for an AI coding utility. Binance’s security division identified the threat, swapped out the hardware, and reset the engineer’s credentials.
A second attempt occurred in September. Another engineer took part in a job interview via an authorized platform and received a coding test that installed malicious software on their work machine. The submission reportedly replaced a developer tool with malicious code, establishing a connection to the perpetrator.
By October 20, the attacker leveraged an internal AI tool from that compromised machine to infiltrate computers belonging to two other engineers—one holding a container deployment token and another on the wallet software team.
How Did the Attacker Reach Multiple Blockchains?
On October 29, the stolen deployment token allowed a container to dispatch unauthorized requests to the internal wallet signing service at Binance. This service cleared requests that deviated from standard withdrawal protocols, compromising hot wallets across 11 blockchains.
The sweep began on the XRP Ledger, Solana, and Optimism. Binance issued an internal alert only after substantial transfers had already taken place. Bitcoin, Tron, and Ethereum followed, with the Ethereum sweep alone amounting to $2.53 billion.
Hacken values the overall theft at $6.34 billion. The losses stem from the signing service processing illegitimate requests, with that single service acting as a bridge between otherwise segregated blockchain networks.
Binance’s Response Combined Asset Freezes and Replacement Funds
How Did Binance Try to Contain the Ethereum Access?
On the Ethereum network, the attacker applied an EIP-7702 delegation to a hot wallet. This permission enabled the attacker’s contract to continue operating through the wallet even after Binance halted withdrawals.
Revoking this delegation demanded authorization directly from the impacted wallet. Because its signing setup relied on multi-party computation, the response team had to formulate an emergency protocol during the event rather than relying on a single key revocation.
The final unauthorized transfer totaled 2,961.9 ETH. The delegation was successfully cleared at 00:10:35 UTC on October 30, bringing that ongoing access channel to a close.
<
What Did the Recovery Response Involve?
Binance intercepted and froze assets while utilizing its own capital to reimburse stolen balances. Platform withdrawals were subsequently restored in phases.
Each measure targeted a distinct challenge: limiting the movement of stolen funds, replenishing user accounts, and restoring platform access. The response addressed both external threats and internal operational recovery.
Earlier Bitcoin Swaps Put the ETH Movements in Context
What Happened to the Earlier $124 Million?
According to Elliptic’s findings shared through tracing reports, assets converted into bitcoin by November 6 totaled roughly $124 million, representing about 1,650 BTC. These conversions demonstrated an attempt to shift value away from the original stolen tokens.
The funds were scattered across thousands of wallets and numerous services. Tracing specialists concluded that only negligible amounts had been converted to cash despite significant volumes moving through conversion channels.
What Was Still in Linked Wallets Before the Latest Moves?
An update on November 16 indicated that addresses tied to the breach held approximately $2.55 billion, primarily in ether and bitcoin. Meanwhile, frozen or seized assets reached $2.85 billion.
Substantial holdings remained connected to the theft as distribution activities persisted. Analysts monitored both the trajectories of the transfers and the conversion pathways being employed.
ETH Recovery Risks Center on Dispersal and Persistent Access
Why Does the Wider Wallet Network Matter?
The operation spans 16 blockchains and a minimum of 36 services. Every wallet hop and conversion increases recovery complexity by introducing additional touchpoints and destinations to monitor.
Implementing more freezes would enhance containment efforts. At the same time, continued asset movement prolongs the tracking work required by analytics teams and partner services.
<
Which Security Failures Did the Reconstruction Identify?
A deployment token was left on an employee’s laptop. The signing service processed requests outside of approved withdrawal workflows. Furthermore, compromised developer tools bypassed endpoint security measures.
The Ethereum delegation presented an additional hurdle: pausing withdrawals did not eliminate on-chain permissions. Recovery necessitated reaching past exchange safeguards to address authorizations already linked to a hot wallet.
Hacken advised implementing stricter controls over developer hardware, validating signing requests, and practicing emergency revocation protocols—all aligned with the specific access points discovered during the attack.
What to Watch After the Latest Binance-Linked Transfers
Which Movements Matter Next?
Observers should monitor where the redistributed ether travels and whether additional linked addresses perform bitcoin conversions. Conversion activity is significant because it alters the form of the stolen assets, forcing tracking teams to follow new token pathways.
Further asset freezes or interceptions would indicate headway, while ongoing wallet activity generates new transactions to monitor.
What Matters for Binance Users?
The phased restoration of withdrawals serves as the primary operational milestone for users. Binance used its internal reserves to restore customer balances while ongoing containment measures targeted the stolen capital.
For clients, withdrawal accessibility and balance restoration remain the key practical updates, running alongside the asset-tracing efforts occurring parallel to Binance’s operational recovery.
FAQ
What Date and Time Window Does Hacken Give for the Original Binance Theft?
Hacken dates the alleged theft to October 29, 2026, between 20:05 and 23:56 UTC. Its reconstruction covers unauthorized transfers across 11 blockchains.
When Did Binance Begin Reopening Withdrawals?
Hacken says phased withdrawal reopening began on November 1, 2026. The restoration followed the October 29 attack and the exchange’s containment response.
How Much of the Stolen Value Was Frozen or Intercepted?
The security firm’s account puts the frozen or intercepted amount at $2.85 billion. It describes that as around 45% of the stolen value, involving action by Binance and other parties.
What Share of the Frozen or Intercepted Funds Was in Stablecoins?
Stablecoins accounted for 94% of the frozen or intercepted amount in Hacken’s account. That percentage applies to the funds contained through those measures.
What Proportion of Stolen Assets Did Binance Replace Using Its Own Funds?
Hacken says Binance replaced 98% of the stolen assets using its own resources. The replenishment supported the exchange’s recovery alongside efforts to locate and restrict stolen funds.
Were Private Keys Stolen in the Attack Described by Hacken?
Hacken says the private keys remained in place. Its explanation centers on an attacker allegedly causing the internal signing service to authorize unauthorized transfers.
How Did EIP-7702 Feature in the Ethereum Theft?
Hacken says the attacker placed a delegation on an Ethereum hot wallet that allowed an attacker’s contract to act through it. Removing that authorization required a procedure involving the affected wallet’s signing arrangement.
This article is for information only and is not financial advice.




Comments 0 responses