Binance Exchange Hack: What Is Confirmed and What Isn't
Confirmed: on 29 October 2026 an attacker took about $6.34 billion in assets from Binance hot wallets, the FBI attributes it to North Korea's TraderTraitor, and Binance says it will absorb the loss. Not settled: the exact total, which ranges from $6.3bn to $6.43bn, and how much is still recoverable, since about $2.85bn is frozen.
The Binance hack of 29 October 2026 is confirmed in its basics: an attacker drained Binance hot wallets of approximately USD 6.34 billion in digital assets, according to Binance, and the FBI attributes the theft to North Korea. What is not settled is almost everything people quote after that, from the exact total to how much is "recovered" to what actually caused it.
This article is a dated fact-check of the Binance hack. It sets out who said what and when, compares Binance's account with the FBI's and with the two blockchain analytics firms tracing the funds, Elliptic and TRM Labs, and marks where those accounts disagree. Sources were read on 9 November 2026 and updated on 14 November 2026.
Is Binance safe after the hack?
Binance says it has completed coverage of the impacted assets and will absorb the roughly $6.34 billion loss, but no independent audit of its reserves has been published as of 14 November 2026. Withdrawals are reopening in phases. This is not advice: check Proof of Reserves, your token's withdrawal status and Binance's announcements.
The table separates what is confirmed from what is not, as of 14 November 2026. "Reported by" means the primary page could not be read.
| Item | Figure or claim | Who stated it | Date | Status |
|---|---|---|---|---|
| --- | --- | --- | --- | --- |
| Size of the hack | About USD 6.34 billion impacted, on 29 October 2026 | Binance | 3 Nov | Stated by Binance; subject to reconciliation |
| Attribution | North Korea's TraderTraitor | FBI alert, reported by BleepingComputer; Binance cites the FBI; TRM Labs "high confidence" | 30-31 Oct | fbi.gov returned an error on 14 Nov, so reported by BleepingComputer |
| Frozen or intercepted | About USD 2.85 billion | Binance; Elliptic reports the same figure | 3 and 7 Nov | Stated, subject to reconciliation; frozen is not returned |
| Withdrawals | Reopened in phases from 1 Nov; no completion date | Binance Recovery Updates #4 and #9; 12 Nov announcement | 1, 6 and 12 Nov | Confirmed by Binance, ongoing |
| Coverage of losses | "Completed coverage" using more than $6.34 billion of company funds; earlier updates said 90%, about 95% and about 98% | Binance | 31 Oct to 12 Nov | Binance's own claim, unverified |
| Reserves | New Proof of Reserves snapshot covering 198 tokens; full zero-knowledge proof pending | Binance | 12 Nov | Binance-published, not an independent audit |
| Independent review | Third-party cybersecurity review of the incident | Binance says it is engaging experts | 3 Nov | No report published; unconfirmed |
How much was stolen in the Binance hack?
Binance says approximately USD 6.34 billion in digital assets was impacted by the 29 October 2026 hack (post of 3 November). Independent counts run from about $6.36 billion (TRM Labs) to $6.43 billion (Elliptic), both dated 30 October, and the FBI alert, as reported by BleepingComputer, says more than $6 billion.
The totals differ because each source counts differently. Binance reports the value "impacted" on its own books. TRM counted about $6.36 billion leaving wallets on ten blockchains, using on-chain figures as of 00:30 UTC on 30 October. Elliptic counts $6.43 billion across 11 blockchains. The FBI, as reported, says only "more than $6 billion."
None of these numbers is wrong. They count different chains at different times, and token prices moved in between. For a single figure, use Binance's USD 6.34 billion, dated 3 November, and name it as Binance's.
Elliptic and TRM agree on the comparison that makes the Binance hack the largest crypto theft on record. Elliptic calls it "more than four times" the $1.46 billion taken from Bybit in 2025. TRM calls it "about four times" the $1.5 billion Bybit hack of February 2025.
The Binance hack, dated: 29 October to 12 November
Each entry in this Binance hack timeline names its source. Times are UTC where the source states them.
- June 2026: A Binance wallet DevOps engineer ("Engineer A") downloaded a tampered Homebrew installation while searching for an AI coding tool. Binance's security team replaced the device and rotated credentials, but the engineer's role remained exposed (Binance, 3 November).
- September 2026: A second engineer ("Engineer B") was approached through a job-hunting platform, interviewed by people posing as a recruiter and a company CEO, and told to download an "assignment" that put a malicious code repository on his work computer. Binance describes the malware as a 0-day that its endpoint tools did not detect at the time (Binance, 3 November).
- 20 October: The attacker used Engineer B's computer and an internal AI tool to gain control over two more engineers, and found that Engineer A held a container deployment permission token (Binance, 3 November).
- 29 October, 17:15 to 19:56: The attacker logged into a third engineer's computer, deployed a container and gained access to "an internal wallet signing service" (Binance, 3 November; the post gives no time zone for this window).
- 29 October, 20:05 UTC: The Binance hack outflows began. Five hot wallets sent 233.46 million XRP by 20:09 UTC; other wallets sent about 970,500 SOL, 44.2 million OP and 18,270 BTC (Binance). TRM Labs says most of the value moved in about 20 minutes. Binance suspended withdrawals as part of containment.
- 29 October, 23:56 UTC: The last unauthorized transfer, 2,961.9 ETH, finalized on-chain. Binance cleared the attacker's Ethereum delegation at 00:10 UTC on 30 October.
- 30 October: TRM Labs attributed the theft to North Korea's TraderTraitor "with high confidence" and counted about $6.36 billion; Elliptic counted $6.43 billion. BleepingComputer reported that Binance linked the breach to a compromised DevOps engineer's laptop.
- 31 October: The FBI issued an alert attributing the theft to North Korea, as reported by BleepingComputer. The same day, Recovery Update #3 said 90% of the stolen assets had been replenished.
- 1 November: Recovery Update #4 raised that to about 95% and reopened phase one of withdrawals between 06:00 and 09:00 UTC.
- 3 November: Binance published its initial findings, citing the FBI and setting the cause as unauthorized access to the wallet signing service.
- 4 November: Recovery Update #7 reported about 98% replenished, with a new Proof of Reserves snapshot covering 44 tokens, up from 10.
- 6 November: Recovery Update #9 reopened withdrawals for more assets from 04:00 UTC and said "Not all listed assets will become available at once."
- 7 November: Elliptic's laundering tracker put frozen or seized funds at $2.85 billion and funds still in theft-linked addresses at about $3.13 billion.
- 12 November: Binance announced it had "completed coverage of assets impacted," committing more than $6.34 billion of company funds, published a Proof of Reserves snapshot covering 198 tokens and said withdrawals continue to reopen in phases. The announcement cites no independent audit.
Three accounts of the Binance hack, side by side
The table puts the same four Binance hack questions to each source. "No figure reported" means the source has not said, not that the answer is zero.
| Question | Binance says | FBI says | Independent tracers say |
|---|---|---|---|
| --- | --- | --- | --- |
| How much was taken? | "Approximately USD 6.34 billion in digital assets were impacted" (3 Nov) | "More than $6 billion USD in virtual assets" (31 Oct alert, as reported) | TRM: about $6.36bn across ten blockchains (30 Oct). Elliptic: $6.43bn across 11 (30 Oct) |
| Who did it? | Cites the FBI: the DPRK "is responsible for this incident" (3 Nov) | North Korea's TraderTraitor (31 Oct, as reported) | TRM: TraderTraitor, "high confidence" (30 Oct). Elliptic: first "likely" North Korea, then cites the FBI (30 Oct, updated) |
| How much is frozen? | "Approximately USD 2.85 billion" frozen or intercepted, subject to reconciliation (3 Nov) | No figure reported; asks service providers to block 628 listed addresses (31 Oct) | Elliptic: $2.85bn frozen or seized, rechecked about 07:40 UTC (7 Nov). TRM: nearly $2.7bn, mostly stablecoins (3 Nov) |
| What was the cause? | Unauthorized access to an internal wallet signing service after a multi-stage campaign against engineers (3 Nov) | No root cause reported | TRM: "points to a compromise of Binance's hot wallet signing infrastructure" (30 Oct) |
One caveat on the FBI column. Binance's 3 November post links to the FBI alert on fbi.gov, but that page returned an error on both 9 and 14 November. The FBI entries above are therefore as reported by BleepingComputer on 1 November: TraderTraitor, "more than $6 billion," 608 Ethereum, 19 Bitcoin and one Solana address, issued with the US Secret Service and IRS Criminal Investigation.
There is also one stale line among the tracers. TRM's 3 November update still says "no government has attributed the theft," three days after the FBI alert was reported. TRM's post does not explain the line, and it does not dispute the FBI's finding.
What does "replenished" mean in the Binance hack?
The distinction matters because headlines about the Binance hack merged the two. A figure of "98% replenished" sitting next to "$2.85 billion frozen" reads like a recovery story. It is really two separate facts: Binance has largely refilled the hole from company money, and third parties have frozen part of what was stolen.
Frozen is not returned, either. According to TRM's 3 November update, the freezes came from Tether, Circle, Ripple, World Liberty Financial and Arbitrum's Security Council, and most of the value is stablecoins locked by their issuers. No source read for this article reports any frozen Binance hack proceeds being handed back to Binance.
The replenishment percentage also has a dating problem in Binance's own channels. The 3 November post says 98% had been replenished "as of 31 October 2026." Binance's own Recovery Updates said 90% on 31 October and about 95% on 1 November, and first reported 98% on 4 November. This article uses 98% as of 4 November. Recovery Update #3 also commits Binance to restoring SAFU to approximately US$1 billion.
How the stated cause changed
The earliest version of the Binance hack's cause was a single device. On 30 October, BleepingComputer reported that Binance linked the theft to a DevOps engineer's compromised laptop, which led to a service container and unauthorized withdrawals. In the same report, co-CEO Richard Teng is quoted on X saying the attacker "did not simply use one engineer's permissions," and Binance said it had "uncovered additional points of breach."
The 3 November findings replace the one-laptop story with a campaign. The account runs from June to October, covers three engineers and two different lures, a tampered installer and a fake job interview, and ends at "an internal wallet signing service" used to "initiate transactions outside the normal withdrawal process." The post never uses the word "laptop"; it says "computer" and "devices."
The Ethereum leg used EIP-7702, an Ethereum feature that lets an ordinary account delegate execution to a smart contract. Binance says the attacker used the signing service to submit 50 transactions that gave an attacker-controlled contract partial execution rights over a hot wallet. Because that wallet used MPC (multi-party computation, where signing authority is split so no single key exists), Binance says it could not revoke the delegation with one key and needed "a specialized procedure."
The laptop report was not wrong, just early and incomplete. Anyone still quoting it as the cause of the Binance hack is quoting a 30 October preliminary account that Binance has since superseded. Binance calls the 3 November post an "initial report," says some technical details will stay confidential, and has commissioned an independent third-party review.
What is still not confirmed
Five parts of the Binance hack story remain open as of 9 November 2026.
- The final total. Binance's figure is subject to "reconciliation and market price volatility," in its own words.
- The final frozen amount. Binance's $2.85 billion carries the same caveat, and early press figures of about $3 billion and $2.67 billion are different snapshots.
- The full root cause. Binance's report is initial, and the third-party review has not been published.
- The FBI text itself. This article relies on tier-one reports of the alert because the fbi.gov page could not be loaded on 9 or 14 November.
- Where the rest of the money goes. As of 7 November, Elliptic tracked about 2,300 BTC ($175 million) converted into new bitcoin addresses and judged that "a negligible amount has likely been cashed out." TRM said on 3 November that the attacker still held about $2.4 billion in ETH and BTC.
What Binance users should check now
The Binance hack is not, on its own, a reason to buy, sell or move anything. It is a reason to check a few facts about your own account against Binance's published figures.
- Your balance against Proof of Reserves. Binance says the 4 November snapshot covers 44 tokens. If you hold a token outside that list, look for it specifically on the Proof of Reserves page.
- Your token and network in the latest Recovery Update. Withdrawals are reopening per asset and per network, so check the specific pair you need. If a withdrawal still will not go through after reopening, our guide to what to do when an exchange freezes a withdrawal covers escalation.
- Messages about refunds or "recovered funds." A large incident is cover for impersonation. Binance has published its updates on its own announcement pages, so treat direct messages as suspect and review our crypto security best practices, especially the phishing section.
- How much you keep on any exchange. An exchange that absorbs a loss has still had its hot wallets drained. If you hold long term, a hardware wallet for cold storage keeps keys off any exchange's infrastructure.
Exchange risk this month is not only about the Binance hack. In a separate case, FinCEN issued an order against MEXC on 6 November; our explainer on what FinCEN's order against MEXC actually does covers why it is not a ban.
Sources
Primary sources read on 9 and 14 November 2026, with tier-one reporting where no primary page could be read:
- 29 October 2026 Binance Security Incident: Initial Findings and Response Update (Binance, 3 November) (binance.com)
- Security Incident | Recovery Update #3: 90% of Stolen Assets Replenished (Binance, 31 October) (binance.com)
- Security Incident | Recovery Update #4: Withdrawals Resume in Phases (Binance, 1 November) (binance.com)
- Security Incident | Recovery Update #7: 98% of Stolen Assets Replenished (Binance, 4 November) (binance.com)
- Recovery Update #9: Withdrawals for More Assets to Reopen (Binance, 6 November) (binance.com)
- Binance Completes Coverage of Assets Impacted in Security Incident; New Proof of Reserves Published (Binance, 12 November) (binance.com)
- Proof of Reserves (Binance) (binance.com)
- North Korea responsible for $6 billion Binance attack (FBI alert, 31 October; could not be loaded on 9 November, contents as reported by BleepingComputer) (fbi.gov)
- North Korea Steals USD 6.36 Billion From Binance in the Largest Hack in History (TRM Labs, 30 October) (trmlabs.com)
- Binance Hack Update: North Korea Launders Proceeds Through Self-Minted Tokens and Chained Bridges (TRM Labs, 3 November) (trmlabs.com)
- The largest theft in history: North Korea behind the $6.4 billion Binance hack (Elliptic, 30 October) (elliptic.co)
- How North Korea is laundering the $6.4 billion stolen from Binance (Elliptic, updated 7 November) (elliptic.co)
- FBI links $6.3 billion Binance crypto heist to North Korean hackers (BleepingComputer, 1 November; tier-one report) (bleepingcomputer.com)
- Binance links $6.3 billion crypto theft to compromised DevOps laptop (BleepingComputer, 30 October; tier-one report) (bleepingcomputer.com)
This article is an editorial synthesis of the sources above. Figures are as stated by each source on the date given and may change as investigations continue. It is not investment or legal advice.
Key Takeaways
- Binance's 3 November 2026 findings put the impact at approximately USD 6.34 billion, with approximately USD 2.85 billion frozen or intercepted.
- The FBI's 31 October alert, as reported by BleepingComputer, attributes the theft of more than $6 billion to North Korea's TraderTraitor and lists 628 addresses to block.
- Independent tracers disagree on the total: TRM Labs counts about $6.36 billion across ten blockchains, Elliptic $6.43 billion across 11.
- "Replenished" means Binance refilled its reserves from SAFU, its Futures insurance fund and corporate treasury, not that the attacker returned anything.
- The stated cause moved from early 30 October reports of one engineer's compromised laptop to a June-to-October campaign against three engineers that reached an internal wallet signing service.
- As of Elliptic's 7 November update, about $3.13 billion still sat in theft-linked addresses and only a negligible amount had likely been cashed out.
Frequently Asked Questions
How much was stolen in the Binance hack?
It depends on who is counting. Binance's 3 November 2026 post says approximately USD 6.34 billion was impacted. The FBI, as reported by BleepingComputer, says more than $6 billion. TRM Labs counts about $6.36 billion across ten blockchains, and Elliptic counts $6.43 billion across 11. Each source counts different chains at different moments.
Did Binance users lose money in the hack?
Binance says no. Its 3 November post states that Binance will absorb the financial impact of the stolen funds, not its users, and its 4 November Recovery Update #7 reports that about 98% of the impacted amount has been replenished from Binance's own resources. Users can check their balances against Binance's Proof of Reserves page.
Who was behind the Binance hack?
The FBI attributes it to North Korea's TraderTraitor, according to tier-one reports of its 31 October 2026 alert, and Binance's own 3 November post cites that finding. TRM Labs and Elliptic reached the same view from on-chain evidence. This article does not go beyond the FBI's attribution.
Was a laptop really the cause of the Binance hack?
Only partly. Early reports on 30 October said Binance linked the breach to a DevOps engineer's compromised laptop. Binance's 3 November findings describe a longer campaign: a tampered installer in June, a fake job interview in September, and access to an internal wallet signing service on 29 October. The laptop was one entry point.
Can Binance withdrawals be made again?
Mostly, in phases. Binance reopened phase one of withdrawals on 1 November 2026 between 06:00 and 09:00 UTC and added more assets on 3, 5 and 6 November. Recovery Update #9 says not all listed assets will become available at once, and deposits remain open. Check Binance's announcements for the specific token and network.
Is any of the stolen crypto being recovered?
Some has been frozen, which is different from returned. Binance and Elliptic both put frozen or seized funds at about $2.85 billion, mostly stablecoins frozen by their issuers. As of 7 November, Elliptic tracked about $3.13 billion still in theft-linked addresses. No source read for this article reports funds being returned to Binance.
About the Author
David Kim
News & Analysis Editorial Desk
News & Analysis Editorial Desk · Web3AIBlog
David Kim is a pen name for our news and analysis editorial desk. Posts under this byline are written and reviewed by contributors covering emerging-technology policy, regulatory action, market events, and incident reporting across crypto and AI. The desk emphasizes primary-source reporting (court filings, regulatory text, on-chain data, official postmortems) over reaction-cycle commentary. Every news post links to the underlying source documents so readers can verify the facts.