Not the official Binance website. Not affiliated with Binance. Content is compiled from public sources, may be incomplete or contain errors, and is updated as sources change.

Binance Attack Tracker

Status: incident confirmed; final net loss unconfirmed · sources up to 2026-10-31 07:09:10 UTC · last chain check 2026-10-31 02:21 UTC · price sample ends 2026-10-30 02:00 UTC · public sources only

Binance walletshot wallets, many chainsAttacker receiversfresh addressesHops and swapsmarket makers, lendingEnd statefrozen · held · rescued
  • 71 actions across Ethereum, Bitcoin, TRON, XRP Ledger, Solana and other chains
  • 150 addresses with labels
  • 37 actions re-read on the chain, 5 unverified
  • 0 transfers to an exchange found (Bitquery, to 06:43 UTC on 30 Oct)

Largest single action: Binance 14 → Main receiver, 167,464 ETH + 1.615B USDT + 62 other tokens.

Fund flow by stage. Amounts are copied from the checked fund-flow data; a label shows every claim that is not re-read on the chain.
StageAmountsMain walletsWhere it went
Preparation28–29 Oct
  • Three small withdrawals (gas money) transfer Two reports
  • 50 auths authorize
  • Tornado Cash
  • Operator wallet 0x7C8601…5CA0
  • Sweeper contract 0x63e842…6fAe
A mixer paid gas money to an operator wallet. That wallet signed 50 authorizations with the Binance 14 key and sent every later sweep.
Theft29 Oct
  • 167,464 ETH + 1.615B USDT + 62 other tokens transfer
  • 28,005.6 ETH transfer
  • 780M USDC transfer
  • 200M USDT + 13 other tokens transfer
  • 18,270.2 BTC transfer
  • 612,729,468 USDT transfer
  • 46,384,098 TRX transfer
  • 233.46M XRP in five payments transfer
  • 965,455.1 SOL in the first transfer transfer
  • Binance 14 0x28C6c0…1d60
  • Binance 16 0xDFd529…963d
  • Binance HW 34 0xEe7aE8…4055
  • Binance BTC hot bc1qm34l…7s3h
  • Binance TRON hot TDqSquXB…hSCf
  • Binance XRP ×5
  • Binance SOL hot 5tzFkiKs…uAi9
Funds left Binance wallets on many chains. On Ethereum nearly all of it went to one main receiver; Bitcoin, TRON, XRP and Solana each have their own first receiver.
Onward hops and swaps29–30 Oct
  • 500M USDT transfer
  • 200M USDT transfer
  • About 325M USDT sold for about 122,300 ETH swap Two reports
  • 60M USDT lend
  • USDT swapped for 638.2M TRX swap Two reports
  • Main receiver 0x5227f6…2f8c
  • USDT hop (500M) 0x974929…c762
  • USDT hop (200M) 0x0ddf04…697e
  • Aave borrower 0x8d5390…639a
  • TRON swap hop TPBkSjkC…bKN4
Hop wallets, market makers (USDT sold for ETH), an Aave market, and on TRON a swap to TRX and a lending market.
Frozen or rescued29–30 Oct
  • 971.1M USDT freeze
  • 823M USDC frozen freeze
  • 312.7M USDT frozen freeze Two reports
  • 175M USDT frozen freeze
  • 27.8M USD1 frozen freeze Two reports
  • 8,426 ETH + ARB rescue
  • Main receiver 0x5227f6…2f8c
  • First TRON receiver TG5iBMQP…zsGi
  • Frozen 175M USDT 0xaa246b…54a0
  • Frozen 30M USDT 0xb171ca…c8c3
  • Frozen 66M USDT TCzBTkqn…7Y62
Issuers blocked tokens in the receiver and hop wallets. The Arbitrum Security Council moved funds out of the attacker's reach.
Still held or unclearat check time
  • 195,460 ETH transfer
  • 122,310 ETH transfer
  • 18,270.2 BTC in 19 addresses transfer
  • $173.3M held after the split transfer One report
  • $149.6M (at the map's prices) transfer Unverified
  • $53.9M (at the map's prices) transfer Unverified
  • ETH stash 1 0x8532fa…43d4
  • ETH stash 2 0xc887af…286a
  • 19 BTC addresses
  • TRX split ×5
  • Downstream hops ×25
ETH stashes, 19 Bitcoin addresses and TRX wallets still hold funds. Some downstream hops and the NEAR collector are not verified. 2 unverified

Maps, every action and every address

Up to three latest posts about the attack from each Binance account, newest first. Swipe on a phone.

Changpeng Zhao (CZ)

Binance founder · @cz_binance

Saw a few discussions about size of hack, why impact to bitcoin price is small, etc. 👇 $6.3 billion is the biggest in USD terms, but not in BTC terms. MtGox was 650,000 BTC! Other important numbers to consider: % of bitcoin (in relation to BTC total supply), ie, market impact. MtGox is big there again at 5%+. Number of users impacted, and % of user assets impacted. MtGox (the largest CEX at the time) and FTX (not small) were all near 100% of users and their asseets. Most important: Who is impacted? Does the platform cover it all? (only one victim), as in recent two CEX cases and Binance. Obviously, still a major disaster for the industry, Binance (and me). It hurts, but we survive. Most importantly, we protect our users. (image from @MatthewRoszak)

post textOfficial sourceOriginal post ↗

Seems token recovery already began. Another little detail in addition to the effort described, users pay trading fees on Binance in the coins they trade, so Binance's naturally accumulates all tokens they list. Your funds are SAFU!

post textOfficial sourceOriginal post ↗

Rough math: $6.x b hack, $3b frozen, $1.x b SAFU fund Gap is about $2b, we have $1.x billion in SPCX alone. Remaining gap is (still painful, but) manageable. 🙏

post textOfficial sourceOriginal post ↗

Yi He

Binance co-founder · @heyibinance

User funds are SAFU.

post textOfficial sourceOriginal post ↗

Binance’s SAFU fund and Binance’s holdings include a large amount of assets such as BTC and ETH. We are currently buying, through OTC and on-exchange, all the stolen altcoins in fully matching amounts. We will update everyone again once the purchases are complete.

post excerptOfficial sourceOriginal post ↗

Reporting to the major shareholder: Our company’s revenue for the year is sufficient to cover the losses, so we do not yet need to sell the SpaceX shares you are bullish on.💁‍♀️

post textOfficial sourceOriginal post ↗

Binance (official account)

Company account · @binance

Binance has begun recovering affected assets for users and continues to work with law enforcement, issuers, blockchain intelligence firms and industry partners to trace, freeze and recover additional funds. The company has already publicly committed to cover losses through company funds in the prior announcement. Binance has already reserved over $6.34B of company funds to cover this incident. $5B of these funds are already held in the exact token assets that were impacted. We are completing the purchase of the remaining amount by buying token assets through market channels and OTC channels. We are doing this to match the format of the remaining token assets and address any asset shortfalls. This step can take longer because some tokens may have low liquidity and OTC settlement also takes time. We will share more progress as soon as we can. These figures do not include frozen or protected assets, which remain subject to ongoing recovery and verification. Currently, $3bn has been frozen, with thanks to our industry partners. We are working with partners and law enforcement to recover the frozen assets.We will continue to use company resources to cover confirmed shortfall and will provide further verified updates as recovery efforts progress. Ultimately, all user funds will be verified publicly through our Proof of Reserves. We will weather this storm. Thank you for the support.

post textOfficial sourceOriginal post ↗

Investigation update: Our initial investigation suggested that the security incident may have involved a compromised laptop, however our subsequent investigation has uncovered additional points of breach. This was a complex attack, and we are doing all we can in coordination with law enforcement to resolve it. We are still gathering the facts, and will share more directly as we have them. Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We are still on track towards the expected timeline to resume the withdrawal service in 45 hours. Deposits remain unaffected. The outflows ceased when we paused withdrawal service earlier. We are still working with partners to freeze many of the impacted assets, and have frozen around $3 billion thus far. We will continue to provide further updates through official Binance channels as more verified information becomes available.

post textOfficial sourceOriginal post ↗

Service Update Deposits remain unaffected and continue to operate as normal. Withdrawals remain paused while our team completes a security revamp of the withdrawal service and its related addresses. We expect to resume within 48 hours, and will update with further details. The incident stems from multiple factors. Our security team is tracing the full attack path through the compromised computer which may be the entry point of the incident. A comprehensive report with the root cause will follow. We will continue to share updates through official Binance channels.

post textOfficial sourceOriginal post ↗

6 more voices (experts, issuers, projects), 6 posts

Status: incident confirmed; final net loss unconfirmed. Times: sources up to 2026-10-31 07:09:10 UTC · last chain check 2026-10-31 02:21 UTC · price sample ends 2026-10-30 02:00 UTC.

Do not add these figures. They measure different things.

FigureSource typeAs ofSource
$2.84 billion (frozen, Elliptic)Analyst / chain data2026-10-30 19:30 UTCElliptic investigation
$6.43 billion (Elliptic)Analyst / chain data2026-10-30 19:30 UTCElliptic investigation
About $3 billion (frozen, via Blockaid)Analyst / chain data2026-10-30 18:46:41 UTCBlockaid (revised page)

3 of 12 current figures shown (1 earlier estimates kept on the Data page). Limits, timeline, addresses and prices

Latest 4 of 12. Newest publication first. Reports with no known publication time come after.

  1. Business Today · published
    Binance confirms $2.54 billion frozen amid potential crypto heist, Bitcoin tumbles below $78,000
  2. TechFlow · published
    币安 8 条链热钱包被盗 62.8 亿美元,复盘黑客攻击完整时间线与攻防始末 (original headline, Chinese)
  3. The Block · published
    Open the The Block report (headline not retrieved)
  4. Axios · publication time unknown
    Open the Axios report (headline not retrieved)