Binance Hack: $6.3B Theft Exposes Questions About Signing Access

Brendan Smith
Brendan Smith - Cybersecurity Analyst
9 Min Read
Gold vault leaking tokens beside Binance $6.3B heist headline

Billions left Binance’s wallets on October 29, but the exchange says investigators have found no evidence that wallet private keys leaked. That is the central puzzle of the Binance hack, with an estimated $6.3 billion impact: an attacker may have obtained something just as dangerous as the keys—the ability to make the exchange authorize transfers. Binance now says investigators have uncovered additional points of breach beyond the initially suspected employee laptop. [1][2]

As of October 30: Binance says deposits are operating normally, withdrawals remain suspended, and losses will be covered using its SAFU fund and company funds. Its latest investigation update gave an expected 45-hour timeline to restore withdrawals; that was a target from the time of that statement, not confirmation that service had resumed. [1]

The laptop explanation is only the beginning

Binance initially described a possible route from a compromised DevOps engineer’s laptop to a service container used to submit unauthorized withdrawals. Richard Teng subsequently stressed that the attacker did not simply use one engineer’s permissions and that the operation was not a single click. He said the investigation had not assigned responsibility to any individual. [2]

That distinction matters. A private key can stay inside protected infrastructure while an attacker abuses a system permitted to request signatures. The resulting transaction can be cryptographically valid and still unauthorized by the business. The missing explanation is which approval boundaries failed between a workstation, an internal service and the systems that move customer assets.

Fifty signatures prepared for a moving target

TRM Labs traces the main burst to roughly 20 minutes beginning at 20:05 UTC. It identifies a particularly revealing Ethereum transaction: the attacker submitted 50 pre-signed EIP-7702 authorizations, each prepared for a different consecutive transaction counter, or nonce. One matched the busy wallet’s current counter and delegated its behavior to an attacker-controlled sweeper contract. [3]

Think of the counter as a moving queue number. Preparing a range reduced the risk that ordinary withdrawals would advance the wallet past the number the attacker expected. The authorization changed what the wallet could do; a subsequent call moved the money. That is why looking only for the largest transfer misses an earlier, decisive change in control.

PublicAML’s separate reconstruction describes three rehearsals on attacker-controlled wallets before the real delegation. It timestamps the Binance 14 sweep at 20:24:23 UTC and an ordinary transfer from Binance 16 to the same collector 24 seconds later. It also identifies later sweeps of newly arriving funds. [4]

Ethereum delegation does not explain everything. TRM found ordinary signed withdrawals on other blockchains too, leading it to assess that Binance’s hot-wallet signing infrastructure was compromised. That remains an investigator’s assessment, not a published final root-cause report. [3]

Why $6.3 billion, $6.36 billion and $6.43 billion appear

These are attributed estimates with different scopes and observation times. They should not be combined into a new total.

  • Binance, October 30 update: about $6.3 billion affected and roughly $3 billion frozen.
  • TRM, snapshot at 00:30 UTC on October 30: about $6.36 billion taken across ten blockchains, valued when transferred.
  • Elliptic, October 30 report: $6.43 billion stolen across eleven blockchains; $2.84 billion verified frozen in its morning analysis.

TRM and Elliptic’s estimates both put the event far above the roughly $1.5 billion Bybit theft in 2025. Their different chain counts are another reason to keep the source beside the number. [3][5]

The race was to change what could be frozen

Elliptic’s 07:00 UTC snapshot distinguishes $2.84 billion frozen from about $3.33 billion beyond token issuers’ reach, at then-current prices. Those values are not a subtraction from the original theft valuation: prices and positions change. Its tracing shows stablecoins being exchanged for native assets such as ETH, including rushed swaps at unfavorable prices. [5]

Elliptic chart comparing $2.84 billion frozen with $3.33 billion beyond issuers’ reach on October 30
Elliptic’s snapshot at 07:00 UTC on October 30, 2026, at then-current prices. Frozen balances are separate from completed recoveries. Source: Elliptic.

The mechanism explains the urgency. Some token issuers can blacklist balances. Native bitcoin and ether have no equivalent issuing company that can simply freeze them. Investigators can still trace those funds, and services can act when they arrive, but that is a different intervention.

Frozen is not returned. Blocking a balance stops a particular movement; it does not by itself establish that Binance has recovered it or credited customers. Likewise, a promise to cover losses is a commitment whose fulfillment must be checked separately from the on-chain freeze total.

The North Korea link—and the limit of that evidence

TRM attributes the operation to North Korea’s TraderTraitor with high confidence. Elliptic also attributes the theft to DPRK actors and describes a shared destination for a small portion of Binance proceeds and funds linked to the earlier Bitget exploit. It cautions that a shared laundering service can handle money for different attackers. Its report says no government or law-enforcement agency had confirmed attribution at that point. [3][5]

October 31 update: The FBI has now officially attributed the October 29 theft of more than $6 billion to North Korea’s TraderTraitor. Together with USSS and IRS-CI, it observed the stolen assets being converted primarily into ETH and published addresses holding or previously holding proceeds. The agencies ask virtual-asset services, including swap services and node operators, to block transactions involving or derived from those addresses. This adds official attribution and laundering indicators; it does not establish the initial intrusion route or confirm that customer funds have been returned. [6]

PublicAML highlights another trap for amateur sleuths: apparent transfers involving look-alike addresses were copycat-token activity, not genuine USDT movements. A familiar ticker and matching address edges are not enough to reconstruct a money trail. [4]

November 3 update: Binance scheduled another staged reopening of withdrawals from 04:00 UTC on November 3. Its notice covers specified asset–network pairs, rather than every token on every network. Deposits remain available. Check the exact asset and network in Binance’s withdrawal interface before attempting a transfer; temporary delays can occur during rollout. This service-restoration milestone is separate from recovering stolen assets. [7]

November 3 findings: the route to the signing service

Update, November 3: Binance’s preliminary account links a June tampered Homebrew download, a September fake job-interview assignment and later access through an internal AI tool. The June device was replaced and credentials rotated, but the attacker learned which engineers worked on wallet infrastructure. The September assignment compromised another engineer’s computer. Binance says that access was used on October 20 to reach colleagues and discover a container-deployment token. On October 29, stolen credentials enabled a container and script that reached signing operations. These are the company’s initial findings, pending independent review. [8]

The report also explains why stopping withdrawals did not immediately end the attack: on-chain EIP-7702 permissions remained effective until revoked. Binance dates the final pending transfer’s confirmation to 23:56 UTC on October 29 and removal of the Binance14 delegation to 00:10 UTC on October 30. That partially answers the earlier access and containment questions; the exact failed approval controls and independent validation remain unpublished. [8]

For customers, check withdrawal availability inside the official app and preserve records of any affected transaction. No unsolicited caller or chat account can lift Binance’s exchange-wide suspension by asking you to send crypto elsewhere. The Coinbase impersonation case involving “safe” wallets shows why such instructions deserve immediate suspicion; it is a separate incident, not evidence of a Binance-specific recovery campaign.

Withdrawal availability, frozen assets and customer reimbursement remain separate questions. The November 3 account adds a preliminary access chain; it does not turn a frozen balance into completed recovery or replace an independent technical review.

November 12–18: frozen funds, court action and new transfers

On November 12, the U.S. Justice Department said government agencies and private-sector partners had frozen more than $2.7 billion linked to the Binance theft. The department had obtained court authorization to seize or restrain more than $1.2 billion of that amount. The authorization figure is part of the freeze total. The announcement also covered a separate operation against FaceStealer, a cryptocurrency theft scheme with its own loss figures. [9]

Other funds were still moving. Panoptic Protocol’s transaction analysis found about 74,880 ETH leaving two addresses linked to the October theft on November 17, followed by about 78,415 ETH from a third address on November 18. All three addresses had held their balances since late October. The transactions document movement of funds from the October theft. They establish where the funds moved at the time of tracking, while legal recovery and return to Binance are separate milestones. [10]

For a customer, the useful check is still the balance and the status of the exact asset and network inside the official app or site. A court action can affect control of stolen assets while withdrawal availability follows its own schedule.

References

  1. Binance. Investigation update: additional points of breach and service status. X, October 30, 2026; accessed October 30, 2026. Official investigation update.
  2. Richard Teng. Statement on the Binance security incident and withdrawal-service response. X, October 30, 2026; accessed October 30, 2026. Statement from Richard Teng.
  3. TRM Labs. North Korea Steals USD 6.36 Billion From Binance in the Largest Hack in History. October 29, 2026; data through October 30, 00:30 UTC; accessed October 30, 2026. Transaction and signing analysis.
  4. PublicAML. Binance hack: a Tornado-funded operator, three test runs, and about 430,737 stolen ETH parked on four wallets. October 30, 2026; accessed October 30, 2026. Ethereum and Tron reconstruction.
  5. Elliptic. The largest theft in history: North Korea likely behind the $6.4 billion Binance hack. Updated October 30, 2026, 08:00 UTC; accessed October 30, 2026. Loss, freeze and attribution analysis.
  6. Federal Bureau of Investigation. North Korea Responsible for $6 Billion+ Binance Attack. FBI Cyber Alerts, October 31, 2026; accessed November 1, 2026. Official attribution and laundering indicators.
  7. Binance. Security Incident | Recovery Update #6: Withdrawals Reopen for More Assets (2026-11-03). X. November 3, 2026; accessed November 3, 2026. Asset–network withdrawal rollout.
  8. Binance. 29 October Binance Security Incident: Initial Findings and Response Update. X, November 3, 2026; accessed November 5, 2026. Preliminary access chain and containment findings.
  9. U.S. Department of Justice. Actions on cryptocurrency theft and the Binance court authorization. November 12, 2026.
  10. Panoptic Protocol. Binance hack recovery and independent transaction analysis. November 18, 2026; accessed November 19, 2026.
Share This Article
Cybersecurity Analyst
Follow:
Brendan Smith has spent over 15 years knee-deep in cybersecurity, chasing down malware from the gritty reverse-engineering of old-school trojans all the way to wrangling full-blown incident responses for small-to-medium businesses that couldn’t afford a full-blown breach. Over at Gridinsoft, he’s the guy piecing together those double-checked guides on nasty stuff like AsyncRAT, a remote access tool used in malware campaigns—helping readers make sense of the threat and work through cleanup without the extra headache.
Leave a Comment

AI Assistant

Hello! 👋 How can I help you today?