Binance Hack-Linked Wallet Shifts $142M in ETH Across Seven Transfers
A wallet linked to the Binance hack transferred $142 million in ETH across seven separate transactions, following ongoing fund-tracking efforts and previous bitcoin conversions by investigators and cybersecurity firms.
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, another linked wallet exchanged stolen funds for bitcoin on November 17, adding further complexity to the money trail.
This activity builds upon the ongoing fund-tracking efforts following the alleged October 29 theft. The recovery challenge for Binance and tracking investigators is now defined by large ether transfers, previous 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 address tied to the November 17 transfers executed bitcoin swaps, resulting in two distinct patterns for investigators to monitor: ether dispersal and asset conversion via a secondary address.
Read More: Binance Seeks ArbitrumDAO Release of Frozen ETH and ARB for Loss Reserves
Authorities and analysts are closely monitoring how these illicit funds are managed in the wake of the initial breach.
How Does the 60,000 ETH Movement Fit?
As reported by U.Today, Whale Alert detected the movement of 60,000 ETH split across five transactions. Each individual transfer of 12,000 ETH was valued between $21.75 million and $21.77 million, for a cumulative total of $108.78 million.
The origin wallet was flagged as connected to the Binance breach. No sales were detected at the destination addresses, marking another significant event in the tracking investigation.
Binance, Whale Alert and the Alleged Attackers
Who Has Been Linked to the Original Theft?
Cybersecurity firm Hacken has attributed the October 29 attack to North Korea-linked TraderTraitor. Their analysis outlines months of preparation aimed at Binance personnel and internal architecture, starting with compromised developer tools, progressing to employee workstations, and ultimately breaching the wallet signing service responsible for approving transfers.
This access path culminated in unauthorized commands reaching the infrastructure managing transactions across 11 different 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 wallet. Furthermore, Elliptic’s extensive tracing operations—highlighted by Shattered—uncovered an infrastructure touching more than 20,000 wallets, 16 blockchains, at least 36 services, and 65,000 transactions.
This vast scope highlights the immense difficulty involved in scattering the stolen capital. Multiple platforms and networks create numerous pathways to investigate, including conversion methods that transform stolen tokens into bitcoin.
How the Alleged Binance Breach Reached Its Wallet Systems
What Happened Before October 29?
In June, a wallet infrastructure engineer inadvertently downloaded a compromised version of Homebrew while searching for an AI coding utility. Binance security spotted the issue, swapped out the hardware, and reset the employee’s login credentials.
A second vector emerged in September, when another engineer was targeted through a job interview on a legitimate platform. They were given a coding task that installed malicious files onto their work device. The submission allegedly swapped out a developer tool with malicious code, establishing a backdoor for the perpetrator.
By October 20, the threat actor leveraged an internal AI tool from that compromised machine to infiltrate workstations belonging to two additional engineers—one holding a container deployment token, and the other working on the wallet software team.
### How Did the Attacker Reach Multiple Blockchains?
The stolen deployment token allowed a container to issue unauthorized requests to Binance’s internal wallet signing service on October 29. The system approved these commands outside of standard withdrawal protocols, compromising hot wallets across 11 distinct blockchain networks.
The sweep began on Solana, the XRP Ledger, and Optimism. Binance triggered internal alarms only after substantial transfers had already taken place. Tron, Bitcoin, and Ethereum followed, with the Ethereum extraction alone amounting to $2.53 billion.
Hacken places the overall theft at $6.34 billion. The breach originated from the signing service processing illegitimate requests, with that single service acting as a bridge between otherwise segregated blockchain ecosystems.
Binance’s Response Combined Asset Freezes and Replacement Funds
How Did Binance Try to Contain the Ethereum Access?
On the Ethereum network, the attacker established an EIP-7702 delegation on a hot wallet. This permission structure allowed the attacker’s contract to continue operating through the wallet even after Binance halted withdrawals.
Revoking this delegation required authorization directly from the impacted wallet. Because its signing architecture relied on multi-party computation, the incident response team had to improvise an emergency protocol during the attack rather than simply disabling a single private key.
The final unauthorized transaction involved 2,961.9 ETH, and the delegation was successfully cleared at 00:10:35 UTC on October 30, halting that persistent backdoor.
### What Did the Recovery Response Involve?
Binance deployed asset freezes and interceptions alongside its own capital to reimburse missing balances, gradually bringing withdrawal services back online in phases.
Each step targeted a distinct challenge: limiting the movement of stolen money, replenishing customer accounts, and restoring network access. The intervention tackled both external threats and internal operational restoration.
Earlier Bitcoin Swaps Put the ETH Movements in Context
What Happened to the Earlier $124 Million?
According to Elliptic’s findings, assets converted into bitcoin by November 6 totaled roughly $124 million, representing about 1,650 BTC. These swaps were designed to obscure the value and distance it from the originally stolen tokens.
The funds were scattered across thousands of wallets and dozens of service providers. Investigators determined that only negligible amounts had been liquidated for fiat, despite significant capital moving through various conversion channels.
### What Was Still in Linked Wallets Before the Latest Moves?
An update on November 16 indicated that approximately $2.55 billion—primarily held in ether and bitcoin—remained in addresses connected to the incident, while frozen or intercepted funds stood at $2.85 billion.
Substantial holdings remained tied to the exploitation as funds continued to be redistributed, with analysts keeping close tabs on both transfer paths and swap destinations.
ETH Recovery Risks Center on Dispersal and Persistent Access
Why Does the Wider Wallet Network Matter?
The operation encompasses 16 blockchains and a minimum of 36 platforms. Every single wallet hop and conversion increases the complexity of recovery efforts, presenting investigators with more endpoints to map and destinations to monitor.
Executing additional freezes would improve containment, while ongoing redistribution prolongs the analytical burden placed on tracking teams and cooperating entities.
### Which Security Failures Did the Reconstruction Identify?
Investigators found a deployment token left on an employee laptop, a signing service that processed requests outside authorized parameters, and compromised developer tools that bypassed endpoint security defenses.
The Ethereum delegation presented an extra hurdle, as pausing withdrawals did not automatically strip away on-chain permissions. Mitigation necessitated reaching past standard exchange controls to alter permissions embedded directly within a hot wallet.
Hacken advised implementing stricter oversight of developer hardware, rigorous validation of signing requests, and pre-planned emergency revocation protocols tailored to the specific vulnerabilities exposed during the event.
What to Watch After the Latest Binance-Linked Transfers
Which Movements Matter Next?
Observers should monitor where the redistributed ether travels and whether additional associated wallets perform bitcoin conversions. Conversion activities are critical because they alter the format of the stolen capital, forcing tracing specialists to adapt and follow new token trails.
Further asset freezes or interceptions would indicate positive headway, while continued wallet activity will generate new transactions to follow.
### What Matters for Binance Users?
The phased restoration of withdrawal functionality remains the primary operational milestone for customers. Binance covered depleted balances using its internal reserves while containment efforts regarding the stolen assets proceeded.
For users, the main practical concerns are withdrawal accessibility and account recovery, even as the ongoing wallet transfers run parallel to the exchange’s remediation efforts.
?FAQ
01What Date and Time Window Does Hacken Give for the Original Binance Theft?
Hacken dates the unauthorized event to October 29, 2026, between 20:05 and 23:56 UTC, encompassing illicit transactions across 11 blockchains.
02When Did Binance Begin Reopening Withdrawals?
According to Hacken, phased withdrawal services began reopening on November 1, 2026, following the October 29 attack and the platform’s containment measures.
03How Much of the Stolen Value Was Frozen or Intercepted?
Security analysts estimate the total frozen or intercepted sum at $2.85 billion, representing roughly 45% of the stolen capital due to interventions by Binance and external partners.
04What Share of the Frozen or Intercepted Funds Was in Stablecoins?
Stablecoins made up 94% of the total amount contained through these freezing and interception measures.
05What Proportion of Stolen Assets Did Binance Replace Using Its Own Funds?
Hacken reports that Binance utilized its own corporate reserves to replace 98% of the stolen funds, supporting customer recovery alongside ongoing asset tracing operations.
06Were Private Keys Stolen in the Attack Described by Hacken?
Hacken states that private keys were not compromised; instead, the breach occurred because the internal signing service was manipulated into authorizing fraudulent transfers.
07How Did EIP-7702 Feature in the Ethereum Theft?
Hacken explains that the perpetrator deployed a delegation on an Ethereum hot wallet, granting an external contract continuous operational privileges. Revoking this access required a specialized procedure utilizing the affected wallet’s multi-party signing configuration.
This article is for information only and is not financial advice.



