
Sophia Bennett
Crypto Analyst
TL;DR
Binance confirmed on Oct. 30, 2026 that about $6.3 billion was stolen, making it the largest crypto theft on record, roughly four times the Bybit hack. Tether and Circle froze over $2.36 billion within hours, and Binance says it will cover all user losses. How the attacker got in has not been reported.
Key takeaways
- Binance confirmed about $6.3 billion in assets were stolen, about four times the $1.5 billion Bybit theft of February 2025, per TRM Labs figures.
- Early estimates ran from $3.3 billion (Blockaid) to $5.84 billion (Arkham wallet holdings) before settling at $6.3 billion.
- Circle said it froze more than $800 million in USDC and Tether said it locked more than $1.567 billion in USDT, together over $2.36 billion.
- Binance says it will repay user losses from its SAFU fund plus company money, and Changpeng Zhao expects users to be made whole.
- How the attacker got in has not been reported, and the hack arrived hours after a Polymarket halt and a Chainalysis incident that have not been shown to be linked.
Four times. That's how much bigger the Binance theft is than the Bybit raid of February 2025, which held the record at $1.5 billion, according to figures from TRM Labs. Binance confirmed on Friday, Oct. 30, 2026, that about $6.3 billion in assets were taken. The Binance hack is now the largest cryptocurrency theft on record.
About $3 billion of it has been frozen. The exchange says it will cover every dollar of user losses.
How the Alarm Went Off
The first warning didn't come from Binance. A blockchain researcher who posts as Spreek noticed funds leaving an Ethereum wallet tied to the exchange and landing in a newly created address, and said so in a post on X. The move went through a contract call that was allegedly funded via Tornado Cash, the mixer regulators have chased for years.
Spreek then reported that wallets tied to those transfers were dumping Tether (USDT) through decentralized exchanges. The detail matters. Thieves who sell into stablecoins on DEXs are trying to make stolen tokens liquid before an issuer can act.
Later on Thursday, Arkham Intelligence tagged a cluster of wallets as "binance‑hacker‑1029" and said they held roughly $5.84 billion. That was a snapshot of what the wallets held, not a verified tally of what was stolen. Blockaid, a security firm, gave a more conservative early read: about $3.3 billion in suspicious transfers across Ethereum, Arbitrum and Avalanche.
So the estimates ran from $3.3 billion to $5.84 billion and landed at $6.3 billion. The picture moved fast. Nobody has said publicly how the attacker got in.
The Freeze That Changed the Math
This is the part policy people will care about. Two private companies did what a court order usually does, and they did it within hours.
As Cointelegraph reported, Circle chief executive Jeremy Allaire said his company froze more than $800 million in USDC, working with law enforcement. Minutes later, Tether's Paolo Ardoino said more than $1.567 billion in USDT was locked. Together that's over $2.36 billion. Binance co‑founder Changpeng Zhao gave slightly different splits, putting Tether's freeze at about $971 million and Circle's at $823 million. Nobody has explained the discrepancy. It may just be different snapshots in time.
Ardoino's one public comment was brief: "Protecting the industry and our partners is our main priority."
I'll admit this surprised me. Issuers have always held the choke point in crypto, but I did not expect the two biggest to move in near lockstep, on a Thursday, for a competitor's customers. That is a different scale of coordination. Regulators who argue that stablecoins can be supervised like payment rails just got a very large exhibit. Crypto purists who dislike a freeze button got one too.
Who Pays, and With What
Binance said it will repay all losses from its Secure Asset Fund for Users, known as SAFU, plus company money. Zhao said he expected users to be made fully whole.
The promise is easier to keep when about half the loot is locked. If the frozen $3 billion can be returned, the true hole shrinks to around $3.3 billion. Still enormous, but a number a company of Binance's size can plausibly absorb. If the frozen funds sit in legal process for months, the answer gets murkier. Who has first claim on recovered assets, the exchange that reimburses users or the users themselves? Those questions tend to surface after the headlines fade.
Then there's what's left unfrozen. Funds that landed in other tokens, or crossed other chains before the issuers acted, are harder to pull back. Bybit's attackers in 2025 moved fast through swaps and bridges, and they kept most of what they took.
A Rough Week for Security
The Binance breach arrived hours after Polymarket briefly halted trading because a third‑party provider was compromised. The prediction market said it fixed the problem, promised to reimburse affected users, and reported all systems running by 7:05 p.m. UTC on Thursday. Cointelegraph also noted a separate cybersecurity incident at the blockchain analytics firm Chainalysis, the kind of company investigators lean on after a theft like this one. Details on that incident were thin.
No one has shown the three events are linked, and calling them a pattern would be a guess. Still, a record theft, a vendor compromise and an incident at a leading forensics firm inside roughly a day is a bad stretch for an industry that wants lawmakers to see it as mature.
What to Watch
First, whether Binance publishes a technical account of the breach. Without one, other exchanges can't judge whether they share the weakness. Second, how much of the frozen $3 billion actually goes back, and on what timetable. Third, the political reaction. A theft this large, with Tornado Cash in the story and stablecoin issuers acting as de facto enforcers, hands ammunition to every side of the policy argument in Washington.
The market's reaction will be the quieter tell, and I'd watch it before the legal fights. If depositors stay put, the SAFU pledge worked. If withdrawals pick up, the real cost of this hack hasn't been counted yet.
