Binance suspected hack: $5.57 billion tally and $1.8 billion frozen

What the two reports establish

The story has two figures that answer different questions. The $5.57 billion figure is the on-chain tally cited by Decrypt for assets leaving wallets associated with Binance. The roughly $1.8 billion figure describes stablecoins reported frozen at the receiving address. Neither figure, by itself, tells an individual customer what has happened to their balance or whether a particular withdrawal has completed.

Odaily's shorter dispatch focuses on Circle. Published at 05:16 SGT on October 30, it reports $823 million of USDC frozen in connection with the suspected Binance incident. That amount matches the Circle figure in Decrypt. The independent overlap is therefore specific: both reports carry the $823 million USDC figure. Odaily's dispatch does not independently establish every part of Decrypt's wider cross-chain tally. Read Odaily's dispatch.

The wording around Binance's response also matters. Decrypt reports that the exchange acknowledged a potential security issue and was investigating. It reports that Binance had not confirmed any impact on user funds at that point. That is a description of the exchange's statement at the time of the report, rather than a fresh confirmation of the account or withdrawal system's condition now.

For readers following a rapidly developing incident, keeping those categories separate makes subsequent updates easier to evaluate. A new wallet tally would update the amount attributed to the outflow. A statement about withdrawals would address service availability. A reconciliation of customer assets would answer a different question again. One update should not silently stand in for all three.

Decrypt places the first Ethereum transaction at 04:24 SGT on October 30 (20:24 UTC on October 29) and Circle's USDC freeze at 05:04 SGT (21:04 UTC). These are the transaction and freeze times reported by the outlet; they give readers a sequence for comparing a later update with the initial coverage. Decrypt's reported timeline.

The frozen amount is part of the wallet story

Decrypt gives the frozen components as 975.1 million USDT and 823 million USDC. Adding the reported amounts gives 1,798.1 million, or about $1.8 billion at the dollar amounts used in the report. The arithmetic explains the rounded headline figure; it does not establish how much money will eventually be returned to anyone.

A freeze and a completed recovery should therefore be tracked separately. In evaluating the next announcement, look for the issuer or exchange to say precisely what happened: an address blocked, assets moved into a controlled wallet, or funds returned. The reports reviewed here support the frozen amount. They do not provide a final distribution of recovered assets to customers.

The same care applies to subtraction. Taking a frozen total away from a reported outflow can produce a number on a calculator, but calling that result the final loss would add an unsupported conclusion. Asset attribution, valuation and the outcome of the investigation would still need to be established. There is no final loss figure in the evidence used for this article.

Someone holding USDC elsewhere should also avoid reading the $823 million figure as an instruction about their own address. The dispatch concerns stablecoins associated with this incident. It is not an account-by-account notice to all USDC holders. If you need to assess a specific transfer, start with its transaction record and the address involved, not with the global headline amount.

How to check a pending Binance transfer

SponsoredBinance

Partner rebate share25%Up to

Check regional eligibility and account terms

✓Code applied automatically by the sign-up link: 11350287

Sign up on Binance →Code11350287Copied

Open the Binance app or browser session you ordinarily use and inspect the specific deposit or withdrawal record. Record the asset, network, amount, displayed status and any transaction identifier. Keep the time shown by the account alongside your own notes. This gives you an exact case to compare with a later account message or to describe to support.

If the account provides a transaction identifier, compare it with the receiving account's record for that same transfer. Keep the asset and network paired throughout the check. Do not substitute a different transaction merely because its amount looks similar. If no identifier is shown, preserve the account's current status rather than inventing an on-chain explanation for the delay.

For a transfer that has not yet been submitted, review the account's current deposit or withdrawal instructions before confirming. Check the current account notice for the asset and network before confirming. Read any instruction that applies to that specific transfer.

If a support request is necessary, describe one transfer per case: what you requested, when you requested it, what the account currently displays, and the transaction identifier if one exists. Ask what that status means for that transfer. A precise question is easier to resolve than asking support to confirm an entire breaking-news narrative.

The NexuAlpha Binance profile can help you find the site's venue coverage. For this incident, use your account's own transfer record to judge your transaction. The profile is background reading, and the article's reported wallet figures should not be treated as a receipt for your account.

Keep trading decisions tied to the position you hold

A customer with a pending withdrawal has a different immediate problem from someone holding an open trading position. If you have a position, inspect its size, collateral and displayed liquidation information in the account. Record any orders you have already placed before deciding whether to change them. These are checks to perform, rather than a claim that a particular order type or service is currently functioning.

If you choose to change a position, read the confirmation screen and the account's response to the instruction. Distinguish an order request from an executed trade in your own records. A submitted instruction, a pending order and a completed fill answer different questions about your exposure. Do not assume the result of an instruction from the fact that you clicked the button.

For a spot holder, first establish which asset and balance you are checking. For someone waiting for an incoming payment, identify the sender's transfer record. For someone who has not sent funds, review the destination and network before submitting anything. The same news event can produce different next steps because the reader's starting point differs.

Keep the account check concrete: the balance, the transfer, or the order that you actually need to understand. Evaluate a decision against that record and the instructions currently displayed in the account.

What would change the account assessment

The most useful next update would resolve an unanswered operational question. Watch for a Binance statement that identifies the scope of affected wallets, explains whether customer balances are affected, or states the status of withdrawals. Read the scope and timestamp of that statement before applying it to a transfer on another network.

For the stablecoin part, look for a statement from Circle or Tether that identifies the assets or addresses covered and describes any subsequent recovery. A larger blocked amount would be a new fact about that component. It would still need to be described using the issuer's own wording rather than automatically relabelled as cash returned to customers.

For the overall tally, look for an address-level reconciliation rather than simply a larger headline. The question is which movements belong to the incident and which assets they represent. Until that is established, keep the existing $5.57 billion amount attributed to Decrypt's report. It should not become an independently audited final loss through repetition.

The Binance coverage page is an internal starting point for related venue information. Return to the dated incident sources when comparing new claims with this report. A later story should tell you what changed: a revised amount, a confirmed service decision, or an investigation finding, with the source for that change.

Questions customers are asking

Has Binance confirmed a $5.57 billion customer loss?

The opened Decrypt report describes a suspected breach and an on-chain tally. It reports that Binance was investigating and had not confirmed an impact on user funds. That evidence does not establish a final $5.57 billion customer loss. A customer-loss statement would need its own confirmation and scope.

Do the reports agree about Circle's USDC freeze?

Yes. Decrypt reports 823 million USDC frozen, and Odaily's dispatch reports a value of $823 million. The agreement supports that specific reported amount. It should not be expanded into independent confirmation of every transaction or every asset included in the broader suspected outflow.

Does roughly $1.8 billion frozen mean that amount has been returned?

The reports describe a freeze. They do not give a completed customer repayment amount. Track any announcement about funds returning separately, including who controlled them, where they went and what the issuer or exchange actually confirmed.

What should I save if my transfer is pending?

Save the asset, network, amount, request time, displayed status and transaction identifier if available. Compare the same transaction on the sending and receiving sides. If you contact support, ask about that specific record and preserve the response with its timestamp.

Which facts remain unresolved here?

The evidence used here does not settle the final loss, root cause, customer-by-customer impact or the present status of every Binance deposit and withdrawal network. Those are the details needed to turn an early incident report into an account-level assessment. Keep the transaction record open when reading the next official update.