Binance potential hack: about $3bn frozen, loss not confirmed

What happened on 29 October 2026?

Binance says it is investigating a potential security issue. Its founder, Changpeng Zhao, wrote that the incident "does look like a hack on Binance" ^[5]. The exchange also temporarily suspended withdrawals on multiple networks as a precaution ^[1].

On-chain tallies showed at least $5.57 billion leaving wallets linked to Binance on Ethereum, Bitcoin and Tron ^[2]. Those tallies count movements of funds, so they do not by themselves prove a theft.

What do the reports agree on?

The reports differ on the totals, but they agree on the core facts:

• Binance has not explicitly confirmed a hack, and it says it is investigating ^[1][5].
• Withdrawals on multiple networks were paused as a precaution ^[1].
• Tether and Circle have frozen stablecoins tied to the incident ^[2][5].
• It is unclear who is behind the attack ^[1].

How much has been frozen?

The Guardian reports that Binance said cryptocurrency firms had frozen about $3bn in funds by Thursday evening ^[5]. This is the only total in the sources checked that is attributed to Binance, and no independent source checked for this article confirms it.

The issuers' own figures are lower. Tether's chief executive said the company froze more than $1.5bn, and Circle's chief executive said it froze more than $800m ^[5]. Together those come to about $2.3bn, so the rest of the $3bn may come from other parties or later freezes. The sources do not say which.

Figure	Reported amount	Source
Frozen by cryptocurrency firms, per Binance	about $3 billion	Guardian [5]
Tether frozen, per Tether's chief executive	more than $1.5 billion	Guardian [5]
Circle frozen, per Circle's chief executive	more than $800 million	Guardian [5]
Tether and Circle frozen in the main receiving wallet	about $1.8 billion	Decrypt [2]
Tether frozen in connection with the hack	about $1.56 billion	TechCrunch [1]
Left Binance-linked wallets, on-chain tally	at least $5.57 billion	Decrypt [2]
Drained from Binance hot wallets, per crypto watchers	at least $2 billion	TechCrunch [1]

How do freezes work?

Stablecoin issuers can block addresses from moving the tokens they issue. Tether and Circle both used this power here, but the attacker was moving funds quickly, so timing matters ^[2][5]. In the author's view, a freeze reaches only the issuer's own tokens, so funds converted into other assets sit outside it. Decrypt's frozen figure of about $1.8 billion is roughly a third of the $5.57 billion tally ^[2]. The sources do not say whether the rest was frozen.

Why do the numbers differ?

The figures measure different things. Decrypt counts the frozen stablecoins in the main receiving wallet, while the Guardian's figures are the totals reported by Thursday evening ^[2][5]. TechCrunch reports that Tether itself froze about $1.56 billion related to the hack ^[1]. The sources do not say how these amounts overlap. Loss estimates are also moving: TechCrunch says Binance may have lost upwards of $5.7 billion, but that figure has not been confirmed, and the theft may still be ongoing ^[1].

Markets reacted quickly too. Decrypt reports that Bitcoin fell below $79,000, down about 2.6% in 24 hours, while BNB dropped about 7% and Monero rose about 6% ^[2].

What is still unknown?

Who is behind the attack, how much was actually lost, and how much can be recovered. TechCrunch reports that it is unclear who is responsible, and that Binance did not say whether it had received any contact from the attackers ^[1]. The Guardian reports that Binance had not explicitly confirmed that funds had been pilfered ^[5].

The statements from Binance and Zhao are not a verified loss figure. Zhao wrote that as a shareholder he expects "all user funds will be fully covered" ^[5]. Binance has said that user funds are completely safe ^[1], and that it has not confirmed any impact to user funds ^[2].

TechCrunch describes the drained wallets as hot wallets, which are internet-connected wallets that store crypto ^[1]. In my view, that design suits customer withdrawals, and it is where this attack landed.

Why does this matter for crypto users?

If the theft is confirmed at this size, it would likely rank among the largest crypto breaches in history ^[1]. TechCrunch puts the 2025 Bybit theft at $1.4 billion, while Decrypt says about $1.5 billion ^[1][2].

In my view, an exchange holds other people's assets, so one weakness can affect many customers at once. That is why the confirmed loss matters as much as the frozen amount.

Binance has also told users to be cautious. Users should not trust unofficial links, messages, or requests for account information, the exchange said ^[1].

What does this say about AI security?

This section is the author's view. It is not a finding from the sources, but it follows from what they report.

The same speed problem applies to AI systems that can move money or change accounts. Google's 2026 forecast calls prompt injection "a critical and growing threat", meaning an attack that manipulates an AI into following a hidden command ^[3]. Bad actors now operate in hours, not weeks, according to Google ^[3]. A tricked agent with broad access can act at machine speed, which leaves little time to notice.

I see three practical controls for any AI tool that touches money or accounts:

1. Give each agent its own identity and the least access it needs. Google argues that identity and access management should treat AI agents as distinct digital actors with their own managed identities ^[3]. An agent with payment rights should not hold a standing key that never expires.
2. Assume the agent can be manipulated, and watch what it sends out. In a controlled simulation, Darktrace showed that after an attacker gets into an environment, a trusted enterprise agent could be abused to set up a command channel. Darktrace has not claimed it observed this technique in operational attacks ^[4]. Outbound traffic from agents should be logged and checked against what the agent is supposed to do.
3. Keep a brake that the agent cannot release. Put withdrawal limits, delays on large transfers, and a stop control that sits outside the agent. In my view, exchanges should treat this kind of pause as standard, and Binance used one here ^[1]. The lesson is not that AI should stay out of money movement. It is that the permission model has to be designed before the agent is trusted. A simple test is to ask whether the agent could move money if an attacker replaced its instructions. If the answer is yes, that action should need a human approval step.

What should readers do now?

Check Binance's official channels before acting on any message about the incident, and treat unofficial links as suspect ^[1]. In my view, incidents like this one attract fake support messages, which is why that warning matters more than the headline figure. Treat the $3bn figure as Binance's reported number, not a verified total, until a source you can open confirms it.

This article will be updated if Binance publishes a verified loss or frozen total. Until then, the figures above are as reported on 29 October 2026.

If you run AI tools that can move money or change account settings, list what each tool can do and set a limit for each one this week.