The $6.3 Billion Binance Hack: What Happened, How It Worked and What It Means for Traders

On 29 October, attackers took about $6.34 billion from Binance's hot wallets, the largest crypto theft on record. Binance's post-mortem shows how they got in: a tampered download, a fake job interview and an internal AI tool. Here is what happened and what it means for traders.

Share
A cracked exchange vault door bursting with violet and blue energy, next to the headline The $6.3 Billion Binance Hack

Updated 10 November 2026: Binance published its initial findings on 3 November. This post now covers how the attackers got in, Binance's final figures, the reopening of withdrawals and the FBI's attribution.

On Thursday, 29 October, starting at about 20:05 UTC, attackers moved roughly $6.34 billion out of Binance's hot wallets on ten blockchains. Most of it left in about 20 minutes.

That makes it the largest crypto theft on record, about four times the $1.5 billion taken from Bybit in February 2025. Binance says its users won't bear the loss: it had replenished 98% of the affected assets by 31 October, and withdrawals have been reopening in phases since 1 November.

On 3 November, Binance published its initial findings. They show the theft was the last step of a campaign that began in June, built on a tampered download, a fake job interview and an internal AI tool. Below: how the attackers got in, what happened on the night, where the money went, who is responsible, and what it means if you keep funds on any exchange.

How the attackers got in: a four-month campaign

Binance's report describes three engineers on its wallet team, compromised one after another:

When What happened, according to Binance
June 2026 A wallet DevOps engineer searched online for a popular AI coding tool and installed a tampered Homebrew package. Binance caught it, replaced the device and rotated credentials, but the attacker had already learned about the engineer's role and wallet-team colleagues.
September 2026 A second engineer was approached on a legitimate job platform by a fake recruiter. After two interview rounds, he downloaded an "assignment" repository onto his work computer. Its malware replaced part of pyenv, a Python tool, and endpoint security didn't catch it.
20 October 2026 From that computer, the attacker used an internal AI tool to take control of two more wallet engineers' machines, and found a container deployment token on one of them.
29 October 2026 In the hours before the theft, the attacker logged in to a wallet engineer's computer with stolen credentials, deployed a container and ran a script that reached Binance's internal wallet signing service.

Co-CEO Richard Teng told CNBC the attackers "spent months building their way in". Binance says it detected and stopped 57 suspected North Korea-linked threats in 2026. This one got through.

The night of 29 October, hour by hour

With the signing service in hand, the attacker could start transactions outside Binance's normal withdrawal process and its checks. Times are UTC, from Binance's report and on-chain analysis by TRM Labs.

When What happened
20:05 to 20:09 Five Binance hot wallets send 233.46 million XRP to the attacker
From 20:10 Hot wallets on Solana and Optimism send about 970,500 SOL and 44.2 million OP
20:20 A bitcoin hot wallet sends 18,270 BTC; within two minutes a Tron hot wallet sends 612.7 million USDT
20:20 One Ethereum transaction carrying 50 signed authorizations hands Binance's main Ethereum hot wallet to the attacker's contract
About 3 minutes later That wallet is swept: 167,464 ETH, about 1.6 billion USDT and dozens of other tokens
21:01 to 21:04 Tether freezes 971 million USDT and Circle freezes 823 million USDC
23:56 The last ETH transfer goes through
30 Oct, 00:10 Binance cancels the attacker's control of the Ethereum hot wallet

How the theft worked

The post-mortem confirms what on-chain analysts suspected in the first hours: no private key leaked. The attacker took over the system that uses the keys.

  • Most chains: ordinary signed transfers. Through the signing service, the attacker started withdrawals from hot wallets that skipped Binance's normal withdrawal flow.
  • Ethereum: an EIP-7702 delegation. EIP-7702, added in Ethereum's Pectra upgrade in May 2025, lets a wallet hand some execution rights to a smart contract without exposing its key. The attacker had the signing service sign 50 such authorizations, one for each likely value of the busy wallet's transaction counter (its nonce). One matched, and the wallet was handed to a contract that swept it.
  • Why it took hours to stop. Pausing withdrawals didn't end the Ethereum drain, because the delegation stayed live. Binance's wallets use MPC, where the key is split across several parties, so there was no single key that could cancel the authorization at once. It took a special procedure, finished at 00:10 UTC.

Where the money went

TRM counted about $6.36 billion at the time of the theft, across Ethereum, Bitcoin, Tron, the XRP Ledger, Solana, Arbitrum, Optimism, Base, Avalanche and Polygon. The largest pieces were Ethereum (about $3.79 billion), Bitcoin (18,270 BTC, about $1.47 billion), Tron (about $628 million) and XRP (about $296 million). Binance's own figure for the total impact is $6.34 billion.

Issuers froze what they could. Tether, Circle, Ripple, World Liberty Financial and First Digital froze tokens linked to the attack, and Arbitrum's Security Council moved about $30 million out of an attacker wallet. Circle's freeze has since grown to more than $1.1 billion in USDC, according to CNBC. Binance puts the total frozen or intercepted at about $2.85 billion, subject to reconciliation.

The rest raced out of reach. Within hours the attacker sold stablecoins for ETH, taking more than 10% below the market price to beat the freezes, and TRM estimated about $2.4 billion sat beyond any issuer's reach, mostly ETH and BTC. The FBI says the attackers are converting the assets mainly into Ethereum.

Who is behind it

On 31 October, the FBI said North Korea's TraderTraitor group was responsible, the same group it blamed for the 2025 Bybit hack, as TechCrunch reported. That matches what TRM Labs and Chainalysis concluded in the first hours. Binance's report doesn't name a group, but it cites the FBI's finding that North Korea is responsible. North Korea has denied any involvement.

If you have funds on Binance

  • Losses are covered. Binance says it will absorb the financial impact, "not our users", has set aside more than 100% of the funds needed, and had replenished 98% of the affected assets by 31 October. It's still buying the remaining, less liquid tokens, and points users to its Proof of Reserves page to check.
  • Withdrawals are reopening in phases. They resumed on 1 November from 06:00 UTC, starting with bitcoin and the most-requested networks, as CoinDesk reported, and more assets began reopening on 6 November, per Binance's recovery update. Deposits stayed open. Check Binance's announcements for the asset you need.
  • Most users stayed. Net outflows in the first nine hours of reopening were about $3.64 billion, around 2.1% of Binance's $171 billion in assets, according to CNBC.

The practical points still hold: use official channels only, ignore anyone offering to "help" recover funds, and never share a seed phrase, private key or 2FA code.

What Binance is changing

Binance says it has rebuilt the affected wallet system in a new environment, rebuilt the internal AI tool and its access controls, replaced the affected devices, cancelled the engineers' credentials and tokens, scanned every employee device and tightened the risk controls on its wallet service. Next come an independent review by outside security experts and more investment in endpoint protection, developer-environment security and AI-based anomaly detection. Some measures, it says, will stay private.

The bigger lesson: the attack went through people, not code

There was no smart contract bug and no cracked key. The way in was a search result, a job interview and an AI tool with wide access, and each step led closer to the one system that could sign for millions of users.

That's the pattern of the last two record hacks. At Bybit in 2025, attackers compromised the interface the signers used. At Binance, they reached the signing service itself. Splitting a key with MPC, or adding signers, protects the key, but not a signing system that's been taken over; here MPC even made the attacker's authorization slower to cancel. (We covered what multisig does and doesn't protect against in Multisig Wallet Explained.)

For traders, the lesson is the same as before. When an exchange holds the keys, a breach at the exchange is a breach of your funds, and being made whole depends on its balance sheet and its choice to pay. Binance had the reserves and has covered the loss. Not every exchange could. We wrote about the harder version of that story in AscendEX Collapse: Why KalqiX Users Can Always Withdraw.

How KalqiX approaches custody

We built KalqiX so that there is no exchange hot wallet holding traders' funds. (More background in Self-Custody Trading: Trade Crypto Without Giving Up Your Keys.)

  • Funds sit in the KalqiX contract on Base, not with an operator. Nobody at KalqiX holds your keys.
  • Withdrawals always go back to your own wallet. You request a withdrawal in the app, then claim it on Base when the proof is ready.
  • There's an escape hatch. You can withdraw directly on-chain even if every other part of KalqiX goes offline.
  • Every batch of trades is proven with a zero-knowledge proof and verified by a smart contract on Base, so settlement doesn't rest on trusting our servers.
  • The contracts were audited by Hexens: 9 findings, zero critical, zero high, and all medium findings fixed.

To be clear, self-custody moves risk; it doesn't remove it. You are responsible for your own wallet's security, smart contracts carry their own risk (which is why audits matter), and KalqiX settles on Base, so Base's own rules apply when you move funds onward. But a compromised engineer's laptop at KalqiX can't sign away traders' balances, because there's no hot wallet of user funds for it to reach.

The takeaway

Binance's post-mortem turns a record theft into a clear story: four months of patient social engineering, ending at the one system that could sign for everyone. Binance has covered the loss and is reopening withdrawals, the best outcome its users could hope for.

The lesson for everyone else hasn't changed: know who holds your keys, and how you get out if something breaks.

If you want to trade on an order book where your funds stay in a contract you can exit on your own, try KalqiX at app.kalqix.com.