We analyzed this claim: is it true that

attackers compromised Binance's internal signing system and used standard Ethereum delegation rules to siphon funds rather than cracking the network itself?

How Stolen Signatures Turned Ethereum Code Against BinanceAI generatedConfirmed

public blockchain records confirmed the transactions used valid digital permissions, backing Binance's disclosure that internal access was stolen rather than Ethereum being hacked

Crypto
  • ClaraAuthorComing December 1
  • RafaVisual artistComing December 1
  • JolinaMarketingComing December 1

How Stolen Signatures Turned Ethereum Code Against Binance

Binance says thieves did not break Ethereum's core rules, but hijacked company approval keys to grant themselves lasting control over its wallets.

Published
Quantum Otter — crypto markets and AI trading bots

In a nutshell

Thieves stole $6.34 billion from Binance by tricking company staff and hijacking internal approval software rather than breaking Ethereum's blockchain code. The intruders used valid company digital signatures to activate EIP-7702, a standard delegation feature that let their own automated programs bypass ordinary exchange withdrawal freezes. While public records confirm the authorization signatures were genuine, outside auditors have not yet verified Binance's private system logs or confirmed its reported $2.85 billion asset recovery.

Highlights

  • Thieves took approximately $6.34 billion from Binance wallets on October 29, 2026.
  • Attackers bundled 50 valid account authorizations into a single Ethereum transaction at 20:20:59 UTC.
  • Binance reported that $2.85 billion of the assets were frozen or intercepted.
  • Binance stated that 98% of impacted customer tokens were replaced by October 31.
  • An independent audit of internal server logs has yet to verify how the approval keys were taken.

From the Editor’s Diary

When digital security fails, the breakdown almost always occurs in the human workplace that holds the keys, not the mathematical ledger that honors them.

Who's involved

  • Binance

    The world's largest online exchange for trading digital currencies

    goal → Trace the breach, restore customer balances, and prove its digital vaults are secure

  • The attackers

    Digital thieves linked by US investigators to North Korea's TraderTraitor cyber unit

    goal → Keep the stolen billions and slip past financial tracking networks

  • Global Cybersecurity Alliance (GCSA)

    An independent digital security watchdog that inspects public blockchain records

    goal → Verify what happened on the open public ledger without seeing Binance's internal logs

  • Jimmy Su

    The chief security officer at Binance

    goal → Explain how the break-in happened and show the exchange has fixed its safety controls

In short

The world's largest cryptocurrency exchange lost $6.34 billion not because the underlying blockchain failed, but because thieves stole the company's internal approval stamps to grant themselves lasting control over its funds. This finding matters because it clears Ethereum, the global digital ledger network, of a fundamental security flaw, shifting the blame entirely to how corporate custodians protect their master credentials.

An independent audit of Binance's private server logs is likely to follow next to determine exactly how staff computers let attackers slip through. That outcome is near-certain because the crypto industry and global regulators require third-party verification before accepting any company's internal explanation of a historic theft.

Ethereum includes a standard feature known as EIP-7702, which lets account holders delegate automated authority to software programs. When intruders managed to generate valid digital signatures from inside Binance, they used that delegation tool to authorize their own code to move money. Because the network saw legitimate permission slips, simply halting ordinary customer withdrawal buttons on the exchange website could not cut off the drain.

How it unfolded

01

Valid Digital Signatures Unlock Billions in Binance Wallets

2026-10-29 – 2026-10-29

On the evening of October 29, automated alerts showed digital tokens flowing out of Binance accounts across several networks. The first transfers began at 20:05 UTC, followed fifteen minutes later by a decisive permission transaction on Ethereum. The thieves did not need to crack Ethereum's underlying code; they used EIP-7702, an official feature added to the network to let accounts hand temporary tasks to smart contracts, or self-running software programs. Because the thieves produced valid digital signatures, the network obeyed the command.

1 source
02

Binance Traces the Theft to Hijacked Staff Approvals

2026-11-03 – 2026-11-03

On October 30, the Global Cybersecurity Alliance verified that the thieves' commands carried mathematically valid approval stamps. On November 3, Binance revealed how the intruders got them: the attackers had tricked employees with a fake job interview, tainted software downloads, and an internal artificial-intelligence assistant. That access let them reach the company's automated signing desk and approve transactions before safeguards intervened.

Chief security officer Jimmy Su explained that because Binance split its cryptographic master keys among several machines—a safety method known as multiparty computation—staff could not instantly pull an emergency plug once the malicious delegation took effect. Binance rebuilt its network, replaced employee machines, and pledged an independent review.

4 sources

Where things stand

As of November 4, 2026, the available facts confirm that Ethereum operated as designed, executing valid instructions supplied by attackers who had penetrated Binance's internal operations. Binance reports that it intercepted or froze $2.85 billion of the affected assets, restored 98% of customer tokens by October 31, and will cover the remaining losses itself.

Those recovery numbers come from Binance and have not been reconciled by outside accountants. It remains unproven whether the intruders stole complete private keys or merely tricked automated services into approving bad transfers. An upcoming independent review of Binance's private server records will be needed to settle how corporate protections broke down.

Sources

  • Binanceofficial-incident-investigation · 2026-11-03
  • Reutersintrusion-reconstruction · 2026-11-03
  • CoinDesktechnical-security-briefing · 2026-11-03