The Binance hack of October 29, 2026 drained an estimated $5.3 billion to $5.9 billion in cryptocurrency from Binance, the world's largest crypto exchange by trading volume, forcing a freeze on customer deposits and withdrawals. If the analyst estimates hold, it would rank as the largest crypto theft ever recorded — well above the roughly $1.5 billion taken from Bybit in February 2025. Even the low end of the range is more than three times the Bybit haul.

Binance confirmed the security incident on Thursday afternoon, US time, and said user funds are safe. The exchange has pledged to cover all losses through its SAFU emergency insurance fund, a reserve financed by a portion of trading fees since 2018, together with company funds. Co-founder Yi He said the exchange will cover every loss from the hack. A final figure has not been published.

Key Facts at a Glance

• When: Thursday, October 29, 2026. Binance confirmed the security incident that afternoon, US time.
• How much: Chainalysis put the theft near $5.9 billion, while Glassnode tallied about $5.3 billion in outflows. Binance's own first estimate of the total impact was about $6.3 billion, according to CoinDesk, which is tracking the running figures. The exchange has not confirmed a final number.
• Frozen so far: About $3 billion, including more than 1.567 billion USDT frozen by Tether and over 800 million USDC frozen by Circle.
• Transfers: Deposits and withdrawals are temporarily suspended, with no restart date announced.
• Losses: Binance says it will cover them with its SAFU fund and company money.

How the Hack Happened

Binance's initial findings point to a hacked laptop belonging to a DevOps engineer. The attacker reportedly used the device to reach an internal service and push through unauthorized withdrawals. The exchange said it found no sign that wallet private keys were exposed.

Blockchain intelligence firm TRM Labs tied the attack to TraderTraitor, a North Korea-linked group, with high confidence. On-chain investigator ZachXBT named the Lazarus Group as the likely attacker, another name long tied to North Korea's state-aligned hacking operations. The attributions converge on the kind of actor analysts have repeatedly connected to record-setting exchange thefts. These are analyst findings; nobody has been officially charged.

Where the Stolen Funds Sit Now

The movement of the stolen coins can be followed on-chain. Blockchain tracker Arkham Intelligence has grouped the attacker's addresses into a single entity labeled binance-hacker-1029. When checked early on October 30 (UTC), the entity showed about $5.79 billion spread across 71 addresses, held mostly in USDT, bitcoin, ether and USDC.

The balance is not standing still. Part of it has already been frozen by Tether and Circle, and Arkham data shows some of the funds moving through Uniswap, CoinDesk reported. Issuer freezes carry real weight here: Tether and Circle can blacklist addresses at the token level, blocking the frozen USDT and USDC from being moved or redeemed. Set against the entity's roughly $5.79 billion tracked balance, the roughly $3 billion already frozen means about half the haul is locked up — though the bitcoin and ether portions fall outside the issuers' control.

What the Freeze Means for Players Who Move Funds Through Binance

Most crypto players use an exchange as a bridge: they buy coins there, send them to a gaming account, then send winnings back to cash out. With Binance paused, that bridge is down in both directions.

Funding a gaming account from Binance is not possible right now. Coins sitting in a Binance wallet will stay there until the exchange lifts the pause, so players should plan around the suspension. Anything already moved to a gaming account or a personal wallet is untouched.

Cashing out winnings to Binance should wait as well. Deposits are suspended too, so a payout sent to a Binance deposit address could sit in limbo. Players may prefer to send winnings to a self-custody wallet they control, or to hold off until Binance announces that deposits are open again.

Binance has urged users to ignore unofficial links, messages and requests for account details. Fake "refund" or "verify your account" emails are a classic follow-up to major hacks, and users should stay alert to phishing attempts, urgent verification requests and unsolicited refund offers.

Binance.US Says It Is Unaffected

Binance.US operates separately from Binance.com, and the company stressed that it is an independent platform. It said customer funds and services are secure and operating normally, The Block reported. US customers can continue using it as usual.

Crypto Prices After the Hack

The broader market took a hit. Bitcoin fell 4.8% to below $77,000, ether dropped 5.7%, and BNB, Binance's own token, slid 8%, according to CoinDesk. Stablecoins held their dollar peg. Anyone holding a gaming bankroll in BTC or ETH is carrying less in dollar terms than before the hack.

What Comes Next

Binance has promised a full post-mortem once its investigation ends, and that report is expected to settle the final loss figure. The exchange has not offered a timeline for restoring transfers. The frozen total may still grow as Binance works with law enforcement and stablecoin issuers. Until withdrawals restart, the company is directing users to its official app, website and X accounts for updates.

Binance founder Changpeng Zhao, who no longer runs the exchange but remains its biggest shareholder, backed the pledge: "as a shareholder, I expect all user funds will be fully covered."

Play Responsibly

Real-money online casinos in the US are for players 21 and over. If gambling stops being fun, call 1-800-MY-RESET for free, confidential help from the National Council on Problem Gambling.

Sources

• CoinDesk, Binance hack coverage, October 29, 2026
• The Block, Binance investigating hack, October 29, 2026
• TechCrunch, Binance pauses withdrawals, October 29, 2026
• AFP via Yahoo Finance, Binance confirms major hack, October 30, 2026
• Bitcoin.com News, What is confirmed and what is not, October 29, 2026

Figures as of 03:30 UTC, October 30, 2026. This article first appeared on Cryptsy and was written by Ethan Blackburn.