Skip to content
TOP NOW Did a Russian Lab Worker's Death Spark a New Plague Pandemic? / Instagram's New AI 'Muse': Creativity or Algorithmic Exploitation? / UK “rape capital” claim — what police data actually allows you to say
Rent Free News home rentfreenews. Claims vs data
Subscribe

Binance and the $6.3B Hack: Testing the Insolvency Claim

A record $6.3 billion left Binance's hot wallets in about 20 minutes. The exchange says it covered 90% of the hole, then 98%, so the panic claim that it is insolvent does not match the record.

Verdict: false alarm.

W
By Wasim • Contributing Writer
Published • Updated
Share

Primary source: Binance incident update of November 3, 2026, as reported by BBC News →

Viral claim - Social media rumors, panic sell-off threads and online trading forums, October 2026
"Binance is insolvent and users will suffer major losses following the $6.3 billion North Korean cyber heist."
Binance and the $6.3B Hack: Testing the Insolvency Claim
Illustration: Rent Free desk — Reality Check
Why it matters

The hack is the largest crypto theft on record. Whether the exchange can cover it tests whether customer balances survive state-backed cyberattacks.

Short answer: Binance is not insolvent on the public record. The exchange says it restored backing for 90% of the $6.3 billion taken from its hot wallets on October 29, then 98% by early November, using its own reserves. The claim that users would lose everything is not supported. But “covered” is not “recovered.” Binance replaced customer balances from its balance sheet. It did not get most of the stolen coins back. The hack is real, the loss is real, and the financial hit is large. The insolvency claim is the part that fails.

Correction (2026-11-15): This article consolidates three companion pieces about the same hack. The earlier version said Binance had “replaced 90 percent of the stolen assets” and had frozen “around $3 billion” itself. Binance restored backing for 90% of customer assets; it did not recover 90% from the attacker. The freeze figure was about $2.85 billion of $6.34 billion, according to Binance. The earlier version also treated a single compromised DevOps laptop as the full attack path. Binance’s November 3 update describes a multi-stage campaign that began in June. The companion articles now redirect here.

1. The claim: a record hack proves Binance is insolvent

The panic started within hours of the breach. Social posts and trading forums said Binance had lost $6.3 billion of customer money. Some claimed the exchange was insolvent. Others said withdrawals would never reopen.

The fear had a basis. Crypto exchanges have failed before. FTX collapsed in November 2022 after executives insisted customer deposits were safe. A $6.3 billion hole is large enough to break a smaller platform.

The claim also had a logic problem. A theft from hot wallets is a loss to the company that holds them. Insolvency means the company cannot meet its obligations. Those are different tests. The record shows Binance met the first wave of withdrawals. It does not show a bankruptcy filing or a missed customer payment.

2. What happened on October 29

Chainalysis, the blockchain analytics firm, traced the first unauthorized transfers to about 4:20 p.m. Eastern Time on October 29. Funds began leaving Binance hot wallets across multiple blockchains.

The transfers totaled about $6.4 billion, according to Chainalysis. Binance and several news outlets put the figure at about $6.3 billion. The difference reflects timing and valuation, not a contradiction.

The attacker moved fast. Chainalysis says the thief swapped $325 million in stablecoins for $285 million in ether over nearly 20 minutes. Stablecoins can be frozen. Ether cannot. Freezes began by 5:14 p.m. ET.

Binance halted withdrawals and said it would cover the loss. The FBI said the theft was the work of TraderTraitor, a North Korean unit that is part of the Lazarus Group. The $6.3 billion haul surpassed the $1.5 billion Bybit hack in 2025, which the FBI also blamed on North Korea.

3. The 90% figure: coverage is not recovery

This is where the viral claim and the company’s statement diverge.

On October 31, Binance said it had restored backing for about 90% of the stolen assets. CNBC reported the figure with a key qualifier: the 90% did not mean Binance had recovered 90% of the funds from the attacker.

Binance said all BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC were fully backed at 100%. The outstanding 10% was made up of tokens outside its top 10. Those tokens are less liquid, so buying them in size takes longer.

The money came from the company, not from the hacker. Binance said it set aside about $6.34 billion. The pool drew on part of its $1 billion Secure Asset Fund for Users, a bitcoin reserve, part of its futures insurance fund and its corporate treasury.

By November 3, Binance said 98% of the affected token assets had been replenished. The company also said $2.85 billion of the $6.34 billion had been frozen or intercepted. Chainalysis put the frozen total at about $2.8 billion as of 11:30 a.m. ET that day.

Those two numbers describe different things. The 90% and 98% figures measure how much Binance had put back into customer accounts. The $2.85 billion measures how much of the stolen property had been stopped. One can be high while the other is low. That is exactly what happened.

4. The withdrawal test

A bank run is the real insolvency test. Binance reopened withdrawals on November 1 in phases. The first batch covered the Bitcoin network. Ethereum and BNB Smart Chain followed. The company said the first phase restored withdrawals across 15 networks and assets.

The outflow was large in dollars and small in proportion. Binance processed $4.6 billion in withdrawals and $1 billion in deposits by Sunday afternoon. The net outflow was about $3.6 billion. That equaled 2.1% of its $171 billion in assets under management, according to The Guardian.

Binance said withdrawal volumes declined and stabilized after the initial spike. Deposits remained substantial, the company said.

One weekend does not settle the question. The figures came from Binance’s own proof-of-reserves snapshot. A full report was expected the next day. The sources reviewed for this article do not include an independent audit of those reserves. A run that continued for weeks would be a harder test than a single Sunday.

5. Who the FBI blames

The FBI attributed the hack to North Korea on Saturday, October 31. It named TraderTraitor, which investigators describe as part of the Lazarus Group. The same unit was blamed for the $1.5 billion Bybit theft in 2025.

Chainalysis reached the same conclusion from on-chain evidence. The firm said the stolen Binance funds commingled with funds from an earlier Bitget theft that was also attributed to North Korea.

Pyongyang rejected the accusation. Kim Yo-jong, the sister of leader Kim Jong-un, called it “absurd rhetoric” and a “sinister attempt” by Washington to damage the country’s image, according to KCNA. North Korea has denied involvement in a series of major cyberattacks over the years.

The distinction matters for how the story is framed. The FBI attribution is an intelligence assessment, not a court verdict. Binance cited the FBI finding in its own update. The company did not present independent proof of its own.

6. How the attack actually worked

The first explanation was simple. Binance said a compromised DevOps engineer’s laptop may have allowed an attacker into a service container. That account circulated widely and became the “one laptop” version of the story.

The company’s November 3 update described a longer campaign.

Binance said the operation began in June, when an engineer inadvertently downloaded malware. That malware exposed the employee’s role and the roles of others on the wallet infrastructure team.

In September, a fake project director contacted a different engineer on a legitimate job-hunting platform. The engineer sat a first-round video interview with a sham HR representative. A second-round interview took place on a chat app with the “chief executive” of a fictitious company. During that interview, the engineer was tricked into downloading malware disguised as an assignment.

On October 20, the attacker used the compromised computer and an internal AI tool. That gave control of the engineer’s system and the system of a second wallet developer on the same team. On October 29, the attacker used the second developer’s computer and stolen credentials from the first engineer to trigger the malicious script.

Richard Teng, Binance’s co-chief executive, said more than one person carried out the hack. He also said the attackers used a “self-destruct mechanism” to delete evidence of their activity.

This detail matters because it changes the lesson. The breach was not a single click by one careless employee. It was a months-long social engineering campaign that crossed two engineers and an internal AI tool.

7. What the record still does not show

Several questions remain open.

The 90% and 98% figures are Binance’s own. The sources do not include an independent audit that confirms the replenishment. The $2.85 billion freeze figure is also the company’s. Chainalysis independently estimated about $2.8 billion, which is close.

The remaining 10% is less liquid. Buying it in size could move prices, which is why the company said it would take longer. Binance said it would keep buying through market and over-the-counter channels until coverage reached 100%.

The frozen funds are not automatically Binance’s. Returning them may require legal process. The attacker still held billions when the freeze estimates were published.

And the corporate promise is not a legal guarantee. Binance’s terms of service, like those of most exchanges, may limit liability for losses from cyberattacks. A statement on X does not rewrite a customer contract. That does not make the statement false. It makes it a promise rather than a court-enforceable guarantee.

8. The verdict: false, with context

The insolvency claim fails on the record.

Binance did not file for bankruptcy or tell users their balances were gone. It reopened withdrawals within three days and processed billions in customer payouts. It restored backing for 90% of the stolen assets, then 98%, and said it would cover the rest.

The context is substantial. The exchange absorbed a multi-billion-dollar loss. The attacker still holds a large share of the stolen crypto. The recovery depends on Binance’s balance sheet and on figures the company reported itself. A larger or longer run could test the exchange in ways one weekend did not.

The claim that Binance is insolvent is false. The claim that the hack was harmless is also false. Both things can be true at once.

That connects to a wider pattern. Crypto exchanges and banks now face the same class of state-backed intrusion, as seen in the Top 5 data leaks of 2026 and the State Bank data breach. The difference here is that the victim published a coverage plan within 48 hours.

Two related investigations on this site cover the same economy of stolen hardware. The physical side, where cargo crews took Nvidia GPUs off trucks between Oakland and Texas, is in the Nvidia cargo heist. The institutional side, where the State Bank of India’s filing count is the number that matters, is in the State Bank data breach.

Sources to check yourself

  • BBC News, November 1: the 90% coverage figure, the $6.34 billion set-aside and the FBI attribution.
  • BBC News, November 3: the fake job interviews, the internal AI tool and the 98% replenishment figure.
  • The Guardian, November 1: the withdrawal restart, Richard Teng’s commitment to cover the remaining 10% and the funding sources.
  • The Guardian, November 1: the $4.6 billion in withdrawals, $1 billion in deposits and 2.1% of $171 billion in assets.
  • The Guardian, November 3: the June malware download, the September recruitment scam and the October 20 and 29 intrusions.
  • CNBC, October 31: the distinction between restored backing and recovered funds, and the list of fully backed tokens.
  • Chainalysis, October 30: the 4:20 p.m. ET start, the $6.4 billion total and the $2.8 billion frozen by November 3.

Frequently asked questions

Q: Did Binance lose customer money? A: Customer balances were not wiped out on the record. Binance says it restored backing for 90% of the stolen assets, then 98%, and that its top 10 tokens are fully backed. The company covered the gap from its own reserves.

Q: Is Binance insolvent? A: The sources show no bankruptcy filing and no missed customer withdrawal. Binance reopened withdrawals on November 1 and processed $4.6 billion against $1 billion in deposits. Insolvency would mean it could not meet obligations. The first test was met.

Q: How much has actually been recovered from the hackers? A: About $2.85 billion of $6.34 billion had been frozen or intercepted by November 3, according to Binance. Chainalysis estimated about $2.8 billion. The rest remained with the attacker at that point. “Covered” means Binance replaced the customer assets, not that it got the coins back.

Q: Who is TraderTraitor? A: A North Korean cyber unit that the FBI blames for the Binance hack. Investigators describe it as part of the Lazarus Group, which was also blamed for the $1.5 billion Bybit theft in 2025. North Korea denies involvement.

How we checked: archived claim → primary dataset / VOD timestamp → quoted human with permission → verdict + corrections link. Report an error.

Reader discussion

Conversation for this story opens with memberships. Until then: found an error? Report it — we correct visibly.

The Sunday footnote — free

5 viral claims, what was missing.

Join the 2-minute Sunday read. One creator test inside. No spam.

AKM Loved by curious readers + quoted creators
Contextual Coverage

Related News — More in Reality Check

All Reality Check →

Keep reading

View all →