DeFi Intel

The $6.3 billion Binance hack paradox: Centralization made the hack possible, but also saved $3 billion

The Binance hack has revived debates about whether decentralization is the digital asset industry’s greatest security advantage or its biggest point of weakness.

TL;DR

On 29 October 2026 Binance lost about $6.3 billion after a compromised engineer’s laptop let attackers use an internal signing service and EIP‑7702 to sweep funds. Centralized stablecoin issuers froze roughly $3 billion, showing that while centralization creates vulnerabilities, it can also limit damage.

Key facts

  • The hack drained approximately $6.3 billion from Binance’s hot wallet across ten blockchains.
  • Attackers used a compromised DevOps engineer’s laptop to access a withdrawal‑signing service.
  • EIP‑7702 was employed on Ethereum to turn the wallet into a sweeper controlled by the attackers.
  • Stablecoin issuers Tether and Circle froze about $3 billion of the stolen assets.
  • Bitcoin and Ether, lacking freeze functions, saw roughly $2.4 billion escape.
  • Binance pledged to cover all losses from its SAFU fund and company reserves, setting aside over $6.34 billion.

On 29 October 2026 Binance suffered a coordinated cyber‑attack that drained roughly $6.3 billion from its hot wallet “Binance 14” across ten blockchains in about twenty minutes. The breach was traced to a compromised DevOps engineer’s laptop that gave attackers access to an internal withdrawal‑signing service. Using the newly‑added EIP‑7702 feature on Ethereum, the hackers turned the wallet into a sweeper that emptied it three times as Binance’s systems automatically refilled it. Stablecoin issuers Tether and Circle froze about $3 billion of the stolen assets, while roughly $2.4 billion in Bitcoin and Ether escaped.

Background

Binance, the world’s largest cryptocurrency exchange, stores large sums of user funds in hot wallets to facilitate rapid deposits and withdrawals. Such wallets are protected by internal services that generate withdrawal signatures without exposing private keys. In 2025 Ethereum introduced EIP‑7702, a mechanism that can designate a contract as a “sweeper” with exclusive execution rights. Stablecoins like USDT and USDC are issued by centralized entities that retain the ability to blacklist addresses and freeze tokens. Past exchange failures, such as Mt. Gox in 2014 and FTX in 2022, have underscored the risks of custodial models and fueled the “not your keys, not your coins” mantra. The Binance incident occurred after a two‑day preparation phase in which the attackers funded a wallet, rehearsed the sweeper contract on testnets, and waited before striking. The hack highlighted both the vulnerabilities inherent in centralized exchange infrastructure and the protective role that centralized stablecoin issuers can play when administrative controls are available.

What happened

According to cryptotimes.io, on 29 October 2026 an Ethereum transaction moved 167,464 ETH and 63 other tokens, including 1.615 billion USDT, out of Binance’s hot wallet “Binance 14”. Etherscan initially valued the receiving address at about $2.38 billion, but on‑chain investigators later traced matching outflows on Bitcoin, Tron, XRP Ledger, Solana, Avalanche, Arbitrum, Optimism, Base and Polygon, raising the estimate to $6.3 billion (TRM Labs reported $6.36 billion). Binance’s preliminary investigation identified a compromised DevOps engineer’s laptop that accessed a service container capable of submitting withdrawal requests and producing valid signatures without leaking private keys. On Ethereum the attacker employed EIP‑7702 to convert Binance 14 into a sweeper that could be operated only by the attacker, allowing the wallet to be emptied three times as Binance’s internal systems refilled it. Stablecoin issuers Tether and Circle used their administrative freeze functions to lock roughly $3 billion of the stolen stablecoins, while Bitcoin and Ether, lacking such controls, saw about $2.4 billion leave the exchange. Binance suspended all deposits and withdrawals at 22:15 UTC, pledged to cover all customer losses from its SAFU fund and company reserves – a sum Binance later said exceeded $6.34 billion – and set aside more than $2.3 billion of its own money for the purpose. TRM Labs attributed the attack with high confidence to North Korea’s TraderTraitor unit, though Binance has not named a perpetrator. The FBI and US Secret Service are reported to be working with Binance to trace the stolen funds.

Market impact

The hack triggered an immediate sell‑off in major cryptocurrencies, with prices falling overnight as reported by cryptotimes.io. The $6.3 billion loss represented a massive on‑chain outflow across ten blockchains, causing heightened volatility. Stablecoin issuers’ freeze actions immobilised about $3 billion, limiting further market disruption from those tokens. Bitcoin and Ether, which together accounted for roughly $2.4 billion of the stolen assets, continued to move on‑chain, prompting tracking by investigators but no direct price stabilization. Binance’s suspension of deposits and withdrawals lasted roughly 45 hours, delaying normal market activity on its platform. The incident also spurred discussions on the trade‑off between centralized controls that can freeze assets and the decentralized ethos of immutable transactions.

Why it matters

The Binance breach underscores a core paradox in crypto security: centralized exchange infrastructure creates a single point of failure that can be exploited, yet the same centralization enables rapid response mechanisms such as stablecoin freezes that can contain losses. The use of EIP‑7702 demonstrates how new protocol features can be weaponised when combined with internal access, highlighting the need for rigorous internal security beyond cryptographic safeguards. The freeze of $3 billion by Tether and Circle shows that administrative controls can act as a safety valve, but also raises concerns about the extent of issuer power over supposedly decentralized assets. The incident revives the debate over self‑custody versus custodial services, reminding users that “not your keys, not your coins” remains a critical risk mitigation strategy. Finally, the attribution to a state‑linked hacking unit, if confirmed, signals that nation‑state actors are increasingly targeting centralized crypto infrastructure, raising geopolitical stakes for the broader digital asset ecosystem.

DeFi Intel’s take

Editorial analysis, not a statement of fact.

DeFi Intel's take: the Binance hack suggests that while centralized exchanges can streamline user experience, they also concentrate attack surfaces that sophisticated actors can exploit, especially when internal tools like withdrawal‑signing services are compromised. The rapid freezing of half the stolen value by stablecoin issuers indicates that centralized administrative controls can provide a meaningful backstop, but they also introduce a layer of authority that runs counter to the trust‑less promise of blockchain. We read this as a signal that the industry must balance ease of use with hardened internal security practices and consider hybrid models that limit single‑point failures without sacrificing the ability to intervene when assets are misappropriated.

Frequently asked questions

How did the attackers gain access to Binance’s withdrawal system?

Binance’s preliminary investigation says a DevOps engineer’s laptop was compromised, allowing the attackers to reach an internal service container that could submit withdrawal requests and generate valid signatures without exposing any private keys.

What role did stablecoin issuers play after the hack?

Tether and Circle used administrative controls built into USDT and USDC contracts to blacklist the addresses involved and freeze roughly $3 billion of the stolen stablecoins, preventing further transfers of those assets.

Why were Bitcoin and Ether not frozen like the stablecoins?

Bitcoin and Ether have no issuer‑controlled freeze function, so once the attackers moved those assets they could not be immobilised by any central authority, allowing about $2.4 billion to leave Binance’s wallets.

Direct answers

Short answers, written to be quoted.

What caused the Binance hack on October 29, 2026?
A compromised DevOps engineer’s laptop gave attackers access to an internal service that could submit withdrawal requests and produce valid signatures, enabling them to drain the hot wallet.
How much of the stolen funds were frozen after the Binance hack?
Approximately $3 billion of the $6.3 billion stolen was frozen on‑chain by stablecoin issuers Tether and Circle using their administrative controls.
Did Binance lose any private keys in the hack?
Binance reported that no private keys were compromised; the attackers operated through the internal signing service without obtaining the keys.
Read full article on CoinDesk →

DeFi Intel is an entity-graph aggregator: we curate, tag and link crypto news to a typed knowledge graph of protocols, tokens, people and incidents. We do not republish the full article body. Use the link above to read the original report at CoinDesk.

Discussion

Comments are reviewed before publication.

No comments yet.

Want the full article?

Continue reading on CoinDesk →

Stay current on entity-tagged crypto news

Get the weekly DeFi Intel brief — entity-graph intelligence covering protocols, tokens and incidents, free to your inbox.