Binance suffers largest hack in crypto history, promises to 'cover all losses'
Binance1 has just confirmed2 what seems to be a historic hack that drained the exchange of assets worth up to ~$5.8 billion3, from which around $3b was already frozen by Tether, Circle and others in the industry4:
We are working non-stop to resolve this issue. Binance will cover all losses. [..] As a precaution, all deposits and withdrawals are temporarily suspended while our team conducts security checks, freezes funds, and works with law enforcement. [..] Update: The current verified total frozen amount is around $3 billion. (Binance)
User funds are safe! It does look like a hack on Binance. Appreciate the quick freeze from Tether (~$971m) and Circle (~$823m). (CZ)
The apparent attacker seemingly managed to trick the exchange into approving malicious transactions and drained multiple assets including USDT, RLUSD, wBETH and LINK. A possible connection to Tornado Cash is likely according to analysis by 0xQuit from Yuga Labs5.
Provided the numbers are accurate, this incident would surpass Bybit’s ~$1.5 billion record theft from 20256 to become the largest single crypto hack of all time.
The total crypto market cap lost 4% at press time: Bitcoin lost the $80K level (trading around ~$77K), while Monero temporarily spiked to ~$645 and is currently holding above $600.
This is an ongoing story and the report will be updated when new information is available.
Update 26/10/30: total loss up to $6.3B USD; subsequent investigation uncovered ‘additional points of breach’ (including a ‘compromised laptop’); Binance emphasised that it ‘will absorb the financial impact of these stolen funds’; investigation remains ‘ongoing’7.
Update 26/10/31: ‘up to 90%’ of the impacted amount ‘covered’ by the exchange; new Proof of Reserve (PoR) snapshot (2026-10-31 00:00 (UTC)) available8.
Update 26/11/2: 95% covered; withdrawals ‘resuming in phases’9.
Update 26/11/10: Binance warned about an unrelated ‘iOS-level’ vulnerability affecting iOS 26.7.1, 27.0.1, and 27.2 that could put ‘seed phrases, private keys, and login credentials at risk across the entire ecosystem’, recommends updating iOS and apps to latest versions, deleting any apps installed from untrusted sources and moving funds to a new wallet created on a clean device for users who suspect a potential breach10.
-
https://binance.com/ ↩
-
https://x.com/binance/status/2115918888429133902, https://x.com/cz_binance/status/2115915423174853077 ↩
-
https://x.com/officer_secret/status/2115923267425022429 ↩
-
https://x.com/paoloardoino/status/2115918000373346709, https://x.com/jerallaire/status/2115916207463481846 ↩
-
https://x.com/0xQuit/status/2115913970075009439 ↩
-
https://www.bybit.com/en/learn/this-week-in-bybit/bybit-security-incident-timeline ↩
-
https://x.com/binance/status/2116538196259684457, https://www.binance.com/en/proof-of-reserves ↩
-
https://x.com/binance/status/2117237539098521938 ↩
-
https://x.com/binance/status/2120093246399430770, https://github.com/forcequitOS/worse_query ↩


