After a breach as large as Binance's on 29 October 2026, rumours move faster than facts. This article lists five things any Binance user can check for themselves, using public sources only. It gives no advice about buying, selling, or moving funds; it only shows where the verifiable facts live.

1. What Binance itself has announced

Start with Binance's own announcements, not social media summaries. The confirmed company statements so far are: the breach began with a compromised DevOps engineer's laptop leading to a service container and unauthorised withdrawals; there is no evidence of a private-key leak; deposits and withdrawals were suspended; the affected address's authorisation was revoked; and co-CEO Yi He said losses would be covered from company funds and the SAFU fund, with user funds safe. If a claim does not appear in an official announcement, treat it as unconfirmed.

2. Your own account activity

Inside your own Binance account, your transaction and withdrawal history is the record that matters for you personally. Check whether any transaction appears that you did not make, and note its time and destination. This is a factual check of your own record; it does not change anyone else's situation, and it is the first thing to have ready if you ever need to contact support about a specific transaction.

3. The on-chain record

Public block explorers let anyone inspect wallet movements without trusting a summary. The documented movements in this breach include 167,464 ETH from Binance 14 and 28,005.6 ETH from Binance 16 at 20:24 UTC on 29 October, with about 204,500 ETH taken from Binance 14 in total. If someone quotes a different on-chain figure, ask for the transaction or address behind it; an explorer link is checkable, a screenshot alone is not.

4. What was frozen, and by whom

The freeze figures are also checkable against issuer statements: Tether froze more than $1.567 billion in USDT, Circle about $823 million in USDC, Ripple about $200 million, and World Liberty Financial $27 million in USD1, totalling about $3 billion frozen. Remember the distinction that matters most: frozen means stopped from moving, not returned. Anyone claiming frozen funds have already been paid back should be asked for the evidence.

5. The 1 November reserves checkpoint

The last check is dated, not immediate. Binance's next proof-of-reserves snapshot is due on 1 November 2026, and it should show whether ETH backing, down from 100 percent to about 94 percent after the theft, has been restored. Alongside it, watch whether deposits and withdrawals have fully resumed after the expected 48-hour window, and whether investigators revise the preliminary $6.3 billion estimate. Until those checkpoints arrive, the careful summary is: large breach, large freeze, cover pledged, investigation ongoing.

Frequently asked questions

FAQ: Where is the safest place to check? Binance's own announcements first, then your own account history and public block explorers. Does checking prove my funds are safe? No, it only verifies specific facts; the overall picture depends on Binance's cover pledge and the coming reserves snapshot. Should I trust viral posts about the hack? Only if they link to a checkable source such as an announcement, an explorer record, or an issuer statement.