The Binance hack hit on October 29, 2026, when attackers drained about $6.3 billion from Binance hot wallets across several blockchains. According to Binance, the attack started with a compromised DevOps engineer’s laptop, which gave the attacker access to a service container used to submit withdrawals. About $3 billion has been frozen so far, and Binance says it will cover every loss from its SAFU fund and company funds.
This post mortem pulls together everything confirmed so far: the timeline, how the attack worked, who is likely behind it and what it means for users. Binance hasn’t published its full technical report yet. We’ll update this post mortem as soon as it does, or when more news follows.
Latest Updates
Update (November 16):
Binance says it has now covered 100% of the stolen assets. That closes the last 2% gap from its November 3 report, and a fresh Proof of Reserves snapshot backs the claim. Users still carry zero losses.
Meanwhile, the US Justice Department stepped in on November 12. Authorities and private partners have frozen more than $2.7 billion tied to the theft. A court also approved the seizure or restraint of over $1.2 billion of that amount. Investigators are still chasing the rest as the attackers push funds through exchanges, bridges and mixers.
The FBI also named a North Korean social engineering campaign “FaceStealer.” It used fake video calls, impersonated contacts and staged tech problems to trick victims into clicking a malicious link. The DOJ links it to over $400 million in thefts over 18 months. Agents also seized cloud servers holding 900+ webcam videos of targets. That playbook mirrors how the Binance breach began, with a fake job interview.
On the withdrawal side, Binance reopened 87 networks this week. It aims to bring back every remaining network and asset by the end of next week.
Finally, CZ pushed back on rumours that Binance dumped crypto to fund the payback. “No, Binance did not sell crypto,” he posted on November 15, as Bitcoin bounced off a four-month low near $62,000. Binance also named Justin Yek as its new CFO, a move it says it planned before the hack.
Earlier Updates
Update (November 9):
Binance has reopened withdrawals for HYPE and APT, two days ahead of its own target. On November 6 the exchange promised HYPE, APT, INJ, PLASMA, NEAR and LTC by the end of this week. Binance Alpha withdrawals are also back on BSC, Ethereum, Base and Arbitrum. The ETH and SOL lists keep growing, and Binance says further assets will follow as each security check is completed.
Meanwhile, Elliptic has found a new laundering trick. The attackers minted six meme coins on NEAR between November 5 and 7, each paired with NEAR in its own liquidity pool. One set of wallets bought the tokens, another set sold them, and around 117,000 stolen NEAR (roughly $430,000) came out the other side looking like trading profit. Elliptic saw the same pattern after the Bybit hack and says the trail is still fully traceable on-chain. The firm is now tracking more than 20,000 wallets across 16 chains, with about 7,000 ETH sent through Tornado Cash since November 8. Around 11.8 million stolen NEAR, worth about $43.7 million, has not moved yet.
Over the weekend a forum listing under the ShinyHunters name claimed 335 million Binance user records were for sale, including KYC documents, passwords and private keys, for $900,000 in BTC or XMR. Binance called it a likely scam on November 8. The exchange does not store passwords in plaintext, does not hold users’ external wallet keys, and says parts of the sample come from markets it has already left. Past listings like this turned out to be infostealer data scraped from users’ own devices, much like the Coinbase data breach fallout. CZ put it bluntly on X: anyone who really held private keys would move the funds, not sell a spreadsheet. The claim is unverified and separate from the October 29 hack, but expect phishing emails built around it. Only use the Binance app or a URL you typed yourself.
Update (November 5):
Binance has confirmed 98% of the stolen assets are replenished, with the last 2% in illiquid tokens still being bought through market and OTC channels. A new Proof of Reserves snapshot was taken on November 4 and now covers 44 tokens, up from 10. The full proof should be ready within 50 to 60 hours, so by around November 6 or 7. Phase three of withdrawals also started at 04:00 UTC today, again rolling out progressively as security checks clear.
Update (November 3, evening):
Binance has published its initial incident report. The attack started in September, when a wallet software engineer was lured into a fake job interview and downloaded a malicious “assignment” repository onto his work computer. On October 20, the attacker used a compromised internal AI tool to pivot to two more engineers, including a DevOps engineer holding a container deployment token. On October 29, that token was used to deploy a container and trigger the drain through Binance’s internal wallet signing service. Binance now puts the impact at $6.34 billion, says $2.85 billion is frozen or intercepted, and reports 98% of the stolen tokens replenished. It has rebuilt the affected wallet system and AI tool, replaced devices and is bringing in independent security firms. Full details below.
Update (November 3):
Phase two of withdrawals started at 04:00 UTC today, covering dozens of extra assets across BNB Smart Chain, Ethereum, Solana, XRP, SUI, Arbitrum, Optimism, Tron and Base, including every tokenized stock (bSTOCKS). As with phase one, assets come back progressively as security checks clear. Binance also launched a VIP Level Protection Program: VIP 1 to 9 users keep their highest level from October 21 to 30 for 30 days, through December 2, no matter their trading volume. Meanwhile, North Korea has denied any involvement. Our North Korea denial coverage has that story.
Update (November 2):
The FBI has officially attributed the hack to North Korea’s TraderTraitor unit, the same group behind the Bybit hack. Binance reopened withdrawals in phases on November 1, starting with the Bitcoin network and restoring 15 networks within six and a half hours. Coverage of the stolen assets is now at 95%.
In the first nine and a half hours, Binance processed $4.65 billion in withdrawals against $1.01 billion in deposits, a net outflow of $3.64 billion, or about 2.1% of its $171 billion in total assets. Fiat withdrawals are back as well, including USD, EUR and MXN. Circle has raised its frozen USDC figure to more than $1.1 billion. The zero-knowledge proof for the October 31 Proof of Reserves snapshot is now complete, so users holding any of the ten covered tokens can verify their balances are backed at least 1:1. A second snapshot covering more tokens follows on November 4. The technical post-mortem is still pending.
Update (October 31):
Binance has now replenished 90% of the stolen assets. BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC are all fully backed again. The money came from a partial use of the SAFU fund, part of its Futures insurance fund and Binance’s own treasury. The last 10% consists of less liquid tokens that will take longer to buy. Binance also took a new Proof of Reserves snapshot on October 31, with the full zero-knowledge proof due by Tuesday, November 3. Withdrawals remain on track to reopen on Sunday, November 1.
First Update
Update (October 30): In a new statement, Binance co-CEOs Yi He and Richard Teng say the hot wallets were compromised at around 20:05 UTC on October 29. Binance has already covered about 80% of the loss with the exact stolen tokens and is buying the rest. Withdrawals should start resuming in phases within roughly 34 hours. A new Proof of Reserves snapshot will follow, with results due by Monday, November 2. Binance also expects to share further technical findings within about 48 hours.
Binance Hack Timeline
Here’s how the biggest crypto heist in history unfolded, with all times in UTC:
- October 28 to 29: The attacker’s relayer wallet receives gas money through three 0.1 ETH Tornado Cash withdrawals.
- October 29, 15:59: That wallet deploys a malicious delegate contract.
- 20:05 to 20:09: Five Binance hot wallets send 233.46 million XRP to an attacker address. Hot wallets on Solana and Optimism follow with about 970,500 SOL and 44.2 million OP. Binance gets an internal alert on the large transfers and starts investigating.
- Shortly after: A Binance hot wallet sends 18,270 BTC to the attacker.
- 20:24: One “sweep” call empties Binance 14. Within 24 seconds, Binance 16 sends another 28,005 ETH to the same address.
- Shortly after: The attacker pulls 780 million USDC from Binance Hot Wallet 34. Binance hot wallets on Bitcoin and Tron get drained as well.
- 23:56: The last unauthorized transfer, 2,961.9 ETH, finalizes on-chain. The EIP-7702 authorizations kept working even after Binance paused withdrawals, so it took a special procedure to revoke them.
- Evening: Binance founder CZ says it “does look like a hack” and that user funds are safe.
- October 30, 00:10: Binance clears the malicious delegation on the Binance 14 wallet by pointing it at the zero address.
The Recovery Timeline
- October 30, 02:23: Binance officially confirms the incident, estimates the impact at $6.3 billion and suspends withdrawals.
- October 30, morning: Reuters reports Binance is working with the FBI and the US Secret Service. Binance reveals it has reserved over $6.34 billion to cover the losses.
- October 30, afternoon: Binance’s co-CEOs say about 80% of the loss is already covered and set a target of roughly 34 hours to start resuming withdrawals.
- October 31: Binance says 90% of the stolen assets are replenished, takes a new Proof of Reserves snapshot and confirms withdrawals should reopen on November 1.
- October 31, evening: The FBI names North Korea’s TraderTraitor as responsible and says the group is converting stolen assets into ETH.
- November 1, 06:00: Withdrawals reopen in phases, starting with the Bitcoin network, followed by Ethereum and BNB Smart Chain. Binance says 95% of the stolen assets are covered.
- November 2: Binance reports $3.64 billion in net outflows for the first day. It also publishes the full proof for its October 31 Proof of Reserves snapshot, and says the next withdrawal phase starts November 3.
- November 3, 04:00: Phase two of withdrawals begins, with stablecoins like RLUSD, USD1, TUSD, FDUSD and XUSD on Ethereum among the first to return. Binance also locks VIP levels for 30 days.
- November 4: Binance takes a second Proof of Reserves snapshot covering 44 tokens and confirms 98% of the stolen assets are replenished.
- November 5, 04:00: Phase three of withdrawals begins.
- Nov 9: HYPE and APT withdrawals reopened ahead of target, and Binance Alpha withdrawals returned on several chains.
- Nov 12: Binance reported 100% of stolen assets covered and shared a new Proof of Reserves snapshot. The DOJ confirmed over $2.7 billion frozen.
- Nov 14: Withdrawals went live again on 87 networks, with the rest targeted for the following week.
According to Reuters, the drain itself took only about 20 minutes.
How the Attackers Got In
Binance’s initial report, published on November 3, lays out a multi-stage campaign that ran for months. It describes a mix of social engineering, malware, a compromised internal AI tool and the EIP-7702 trick on-chain.
The first crack came in June 2026. A wallet DevOps engineer, called Engineer A in the report, downloaded a tampered Homebrew installer while trying to set up an AI coding tool. Binance’s security team caught it, replaced the device and rotated credentials. However, the attackers now knew who worked on Binance’s wallet infrastructure.
In September, a second person, Engineer B, was approached on a job platform by someone posing as a project director. He went through two video interviews, including one with a fake CEO. Near the end of the second one, he was told to download an “assignment” repository onto his work computer. That repository carried zero-day malware that replaced a legitimate pyenv component, opened a channel to an attacker server and then cleaned up its traces. Endpoint security didn’t catch it.
From One Laptop to the Signing Service
On October 20, the attacker used Engineer B’s compromised machine and an internal AI tool as a springboard to reach Engineer A and a third wallet engineer, Engineer C. On Engineer A’s computer, they found a container deployment token.
Nine days later, between 17:15 and 19:56 UTC, the attacker logged on to Engineer C’s machine, used Engineer A’s stolen token to deploy a container, and triggered a script that launched the attack through Binance’s internal wallet signing service. That service signed the withdrawals, which is why no private key ever leaked.
Binance says it blocked 57 suspected North Korea-linked attempts in 2026 alone, using the same playbook: fake interviews, trojanized developer tools and fake video apps. This one got through.
How the Funds Were Drained On-Chain
On Ethereum, the method was clever and fast. EIP-7702 lets a regular wallet temporarily run smart contract code. The attacker used it to point Binance 14 at their own contract, then called a “sweep” function. In one transaction, that function emptied the wallet of ETH and more than 60 tokens.
The biggest assets in that first sweep included about 1.6 billion USDT, 62.6 million RLUSD, nearly 30,000 wBETH and over 11,000 XAUt. Large chunks of UNI, ENA, PEPE, LINK and AAVE followed. After that, the attacker forwarded 195,460 ETH, worth around $450 million, to a fresh wallet.
Beyond Ethereum, independent tallies traced stolen funds on Bitcoin, Tron, the XRP Ledger and several Layer 2 networks. On Bitcoin alone, about 18,270 BTC left a Binance hot wallet.
Binance’s report adds a detail that explains why containment took hours. The attacker submitted 50 signing transactions to manipulate the wallet’s nonce and lock in the delegation. Because the hot wallet used multi-party computation, there was no single key to revoke it with, and pausing withdrawals did nothing to on-chain authorizations. Binance had to build a dedicated procedure to clear them.
How Much Was Stolen and Frozen
Binance now puts the total impact at about $6.34 billion. That’s roughly four times the $1.5 billion Bybit hack from February 2025, the previous record. For how it stacks up against every other exchange breach, see our biggest exchange hacks ranking.
The freezes came fast, and from more directions than usual:
- Tether has frozen nearly $1.57 billion in USDT linked to the hack, according to Reuters.
- Circle has frozen more than $1.1 billion in USDC, up from the $823 million it first reported.
- World Liberty Financial froze the $27 million in USD1 tied to the hack. Co-founder Zach Witkoff called stopping stolen funds a shared responsibility.
- The Arbitrum Security Council executed a transaction freezing about $30.5 million held by the exploiter on Arbitrum.
- In total, Binance’s report puts the frozen or intercepted amount at $2.85 billion, down from its earlier $3 billion estimate, pending reconciliation and price moves. The US Justice Department reports a slightly different number. It counts more than $2.7 billion frozen through government and private efforts, with court approval to seize or restrain over $1.2 billion. Binance and the DOJ count differently, so both figures stand side by side.
The Arbitrum move stands out. Usually, only stablecoin issuers can freeze funds. Here, a Layer 2’s security council stepped in directly, which shows how seriously the industry is treating this one.
Even so, around $3.5 billion remains outside the freezes. Most of it sits in assets no issuer can freeze, like BTC and ETH, and the FBI says the attackers are already converting what they hold into ETH.
On the bright side, Binance says the outflows stopped once it paused withdrawals. In other words, the losses aren’t growing.
How Binance Is Covering the Losses
Binance’s message has been consistent: users won’t pay for this. The exchange says it will cover all losses from its SAFU fund and company funds.
The details are more concrete than usual:
- Binance has reserved over $6.34 billion of company funds for the incident.
- Binance now says it has replenished 100% of the affected assets, including the illiquid tokens it had to source last. SAFU did only part of the work here, since the fund is far smaller than the loss. We break down how exchange protection funds like SAFU really work and who actually pays you back.
- Binance is buying the rest through market and OTC channels, which may take longer for low-liquidity tokens.
- Frozen funds come on top of this, so any recovery reduces the final cost.
- The full proof for the October 31 Proof of Reserves snapshot is live, covering BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC. A second snapshot from November 4 expands that to 44 tokens, with its proof due within 50 to 60 hours. Once it’s out, holders of any covered token can verify on Binance’s PoR site that their balance is backed at least 1:1.
- To pay for it, Binance tapped part of its SAFU fund and its Futures insurance fund. It has committed to topping SAFU back up to about $1 billion.
- Binance has rebuilt the affected wallet system and internal AI tool, replaced devices, revoked all related credentials, and is engaging independent security firms to review its findings. It also plans a security research fund focused on AI security in crypto.
Binance co-CEO Yi He summed up the confidence in a reply to Elon Musk. She said the company’s revenue for the year is enough to cover the losses.
Who Is Behind the Binance Hack?
The FBI has now officially named North Korea. In a statement on October 31, it attributed the attack to TraderTraitor, the state-sponsored unit also behind the Bybit hack in 2025 and the Bitget hack in September. According to the FBI, the group is converting the stolen assets into ETH and will likely launder them further through DeFi and instant swap services.
That confirms what the analysts said from day one. TRM Labs had already pointed to the same group with high confidence, Chainalysis named TraderTraitor as well, and 0xQuit flagged Lazarus early on. President Trump, asked about it on Saturday, said the US didn’t yet know if North Korea was behind it, but the FBI’s statement came the same day.
Binance’s own report now backs that up. It cites the FBI’s attribution and describes the fake recruitment interviews and trojanized developer tools that match North Korea’s known playbook. Binance says it stopped 57 similar attempts this year. Despite all that, North Korea has denied any involvement.
Elon Musk, CZ and the FTX Comparison
Not everyone stayed supportive. Elon Musk quoted a post about the hack with a short “Everyday is Zeroday.” Later, he replied with a grimacing emoji to a meme comparing CZ to SBF.
The meme hit a nerve for a reason. Before FTX collapsed in 2022, SBF famously tweeted that FTX had enough to cover all client holdings. So when CZ promised to cover the Binance losses, critics drew the obvious line.

CZ pushed back directly. He told Elon it was a bad time to troll. He also reminded him that Binance’s $500 million investment in his Twitter takeover is now worth over $1 billion in SPCX shares. Yi He followed up with her line about yearly revenue covering the loss.
The difference with FTX lies in the details. Binance has named a reserve amount, says most of it already sits in the exact stolen tokens, and has promised a public Proof of Reserves. If those numbers hold up, this is a costly hack, not a solvency crisis.
How We Alerted Our Community
When news like this breaks, minutes matter. As soon as the first rumours surfaced, we tweeted a warning to our community. Once the on-chain evidence was clear, our Binance hack coverage went live within minutes. After that, we kept updating it through the night as the numbers grew from $2 billion to $6.3 billion.
For me, this isn’t new. During the Bybit hack in February 2025, I tweeted the warning while pulling my own funds off the exchange. You can read that story in our Bybit hack breakdown. On October 29, we did the same with the Polymarket hack just hours before Binance got hit.
Every time, the routine is the same. I rush to my desk, watch the chain, warn our users first and trade the volatility when there’s a setup. That’s what AirdropAlert has always been about: looking out for our users.
Our coverage got noticed beyond our own community, too. Bloomberg featured me in its deep dive inside the Binance hack. That night, I was on a Discord call with six friends, working out how to trade the chaos as prices started to drop. When my wife walked into my office, I sent her straight back out. “Binance got hacked, babe,” I told her. “Need to lock in.”
What Binance Users Should Do Now
Withdrawals are back since November 1, rolled out in phases, and deposits never stopped. Here’s how to handle the next few days:
- Ignore fake links. Scammers will push “withdrawals are back” and “claim your refund” pages. Only use the official Binance app or website.
- Check your asset first. Withdrawals are coming back in phases: the 15 biggest networks on November 1, dozens of altcoins and all tokenized stocks on November 3, and a third batch from November 5. If your asset isn’t available yet, or a withdrawal fails, check Binance’s network status page and retry later.
- VIPs are covered. If you’re VIP 1 or higher, your level is locked at its October peak until December 2, so the withdrawal pause won’t cost you fee tiers.
- Diversify. If this hack made you rethink keeping everything on one exchange, our Binance alternatives list covers the platforms we trust.
- Brush up on safety. Our crypto safety guide covers phishing, drainers and wallet hygiene.
We’ll also refresh our Binance review next week with a full section on the hack and Binance’s response.
Keep This Content Free
Covering a $6.3 billion hack in real time takes a long night, and we keep every word of it free. One way to avoid exchange hot wallet risk altogether is to trade on-chain. On a perp DEX, your funds stay in a smart contract rather than a custodial hot wallet, although DEXs carry their own risks, as the Polymarket frontend hack showed.
If you want to try it, start with our Hyperliquid review and our Lighter review. Signing up through our Hyperliquid referral link or our Lighter referral link supports our work at no extra cost to you.
Final Words
The Binance hack started with a fake job interview and a malicious code repository, and turned into the biggest crypto theft ever recorded. Fortunately, fast freezes from Tether, Circle, WLFI and Arbitrum, plus Binance’s replenishment of 98% of the stolen tokens, mean users should come out whole. The bigger questions are how the attackers moved across so many chains and how Binance will lock down its systems from here.
It’s been a rough month for security. From the Keystone data breach to Polymarket and now Binance, attackers keep hitting the weakest link, which is rarely the code itself. We’ll update this post mortem as soon as Binance publishes its full technical report or more news follows.

FAQ
What caused the Binance hack?
According to Binance’s initial report, a wallet engineer downloaded malware during a fake job interview in September 2026. The attacker used that access and an internal AI tool to reach a DevOps engineer’s deployment token, then deployed a container that triggered unauthorized withdrawals through Binance’s wallet signing service. No private keys were leaked.
How much was stolen in the Binance hack?
Binance puts the total impact at about $6.34 billion. Roughly $2.85 billion has been frozen or intercepted, leaving around $3.5 billion outside the freezes.
Who froze the stolen funds?
Tether froze nearly $1.57 billion in USDT and Circle froze more than $1.1 billion in USDC. World Liberty Financial froze $27 million in USD1, and the Arbitrum Security Council froze about $30.5 million on Arbitrum.
Will Binance users be reimbursed?
Yes. Binance says it has covered 100% of the stolen assets using SAFU, its Futures insurance fund and its own treasury. Users carry no losses.
Who is behind the Binance hack?
The FBI has attributed the hack to TraderTraitor, a North Korean state-sponsored hacking unit. The same group was behind the $1.5 billion Bybit hack in February 2025.
When will Binance withdrawals reopen?
Most already have. Binance reopened 87 networks in the week of November 9 and aims to restore all remaining networks and assets by the end of the week of November 16.
Is the Binance hack the biggest crypto hack ever?
Yes. At about $6.3 billion, it’s around four times larger than the $1.5 billion Bybit hack in February 2025.
Has Binance published an official post-mortem?
Binance published its initial incident report on November 3, 2026, covering the attack path and its first fixes. It calls the investigation ongoing, says some technical details will stay confidential, and has engaged independent security firms for a further review.










