Binance said it had set aside more than $6.34 billion in company funds and reserves to cover the financial impact of its hack; about $5 billion, the company said, was already held in the affected tokens. That is a commitment to cover losses—not confirmation that stolen assets have been recovered or that the reserve has been independently verified.
On October 30, 2026, Binance said it had set aside more than $6.34 billion to cover the incident’s financial impact, which it preliminarily estimated at about $6.3 billion.
In its official update, Binance said the company would absorb the financial losses rather than pass them on to users. This is the exchange’s statement about funds set aside for coverage, not a final, independently verified loss assessment.
Binance said about $5 billion of the amount was already held in the same tokens affected by the incident. The Block reported that the exchange was buying the remainder. The distinction matters: the total amount committed and the assets reportedly already available in matching tokens are not the same figure.
No. Setting aside funds, recovering stolen assets, and freezing transfers are separate actions.
A commitment to cover losses means Binance says it intends to make up the financial shortfall. By itself, the announcement does not show how much stolen crypto has been recovered or when users will receive compensation.
Frozen assets should not automatically be counted as recovered assets either. Restricting token transfers and restoring assets for affected users are separate steps. The Associated Press separately reported Binance’s statement that it had begun recovering assets for users.
For exchange operators, the incident illustrates why response planning needs to cover both cybersecurity and the financial capacity to absorb losses.
In practical terms, an exchange needs to establish who can authorize compensation, which resources can fund it, and how quickly the required assets can be made available. If restoring customer balances requires matching tokens, a dollar-denominated reserve alone may not be enough; the asset mix and availability also matter.
These are risk-management takeaways, not independent verification of Binance’s stated reserve. The available sources describe its amount and composition based on company statements.
No. Binance said it had set aside more than $6.34 billion overall and that about $5 billion was already held in affected tokens. That is the company’s statement; the sources reviewed do not independently verify the full reserve.
No. A loss-coverage reserve is not the same as recovering stolen assets. Freezing, recovery, and compensation are distinct processes.
The exchange said its reserve exceeded its preliminary estimate of the incident’s impact. The available sources do not independently reconcile the two amounts or establish the final loss.
As of October 30, 2026, Binance said its investigation had identified additional intrusion points, while withdrawals remained suspended. The exchange set Sunday, November 1, as a target for resuming withdrawals, not a confirmed schedule, as it continued rebuilding and testing related systems. The roughly $6.3 billion impact figure and the investigation’s findings remain preliminary.
Binance said investigators found additional intrusion points beyond the initially suspected compromised laptop; the full sequence of the attack has not yet been published.
Binance’s October 30 preliminary update said the incident may have involved a compromised DevOps engineer’s laptop and access to a service container. CoinDesk later reported that co-CEO Richard Teng said investigators had found additional intrusion points. That broadens the initial picture but does not yet establish the complete attack chain.
Binance estimated the incident’s overall impact at about $6.3 billion and said roughly $3 billion in affected assets had been frozen. These are preliminary company figures, not a final audited loss calculation.
Binance named Sunday, November 1, 2026, as its target, but withdrawals were still suspended in reports published October 30 and no confirmed restart time had been announced.
CoinDesk reported that Binance hoped to resume withdrawals by Sunday while rebuilding and testing the relevant infrastructure. Other reports described approximate time windows. These should not be treated as guarantees: the target could change if security checks are not complete.
For users and integration teams, the practical approach is to check Binance’s official channels for current status rather than rely on a stale estimate or retry against an assumed schedule. At the time of the cited reports, Binance said withdrawals remained suspended.
CoinDesk reported that Binance was reviewing cloud systems, employee devices, private-key management and transaction-signing procedures.
This indicates that recovering trading infrastructure involves more than switching the withdrawal function back on. The exchange said it was reviewing several connected components before testing operations.
This is a list of review areas described in reporting, not a complete technical plan published by Binance. A final post-mortem was not yet available.
The incident highlights the need to examine the full path from employee devices and internal services to permissions and transaction approval—not just wallet security.
This is an operational inference from the reported facts, not a conclusion from a completed root-cause analysis. When an investigation identifies additional intrusion points, platform operators can review trust boundaries between employee devices, service containers, cloud systems and critical asset operations.
Specific controls depend on a platform’s architecture. The available reports do not disclose Binance’s complete internal controls, so this is a general operational checklist, not a description of its configuration.
As of the October 30 reports, the final attack sequence, all contributing causes and the actual withdrawal restart time were not known.
Binance said it would publish a technical post-mortem after completing its investigation and verifying the facts. The final attack mechanism, the full set of affected systems and whether the restart target would be met therefore remained unresolved.
It is also important to distinguish company statements from independent verification. Binance said its preliminary investigation found no evidence of a wallet private-key leak and said it would cover losses, but those statements do not replace a final technical report and subsequent verification.
Reports published on October 30 said withdrawals were still suspended. Sunday, November 1, 2026, was described as a target, not a confirmed restart time.
It is Binance’s preliminary estimate of the incident’s overall impact. It should not automatically be read as the final amount of assets permanently lost.
No. In its preliminary update, Binance said it had found no evidence of a wallet private-key leak. A full technical review had not yet been published.
Use official Binance updates for current status, account for the withdrawal pause in transaction processing and avoid treating the target date as a guaranteed schedule.
As of the October 30 reports, no full post-mortem had been published. Binance said it would share one after the investigation and fact verification were complete.
As of October 30, 2026, Binance estimated the incident’s impact at about $6.3 billion and said approximately $3 billion had been frozen. The exchange said a compromised DevOps engineer’s laptop may have provided a route to a service container, but the investigation is ongoing and no full technical post-mortem has been published. In Binance’s latest update found for this report, deposits were operating while withdrawals remained paused.
Binance is investigating unauthorized withdrawal transactions with a preliminary estimated impact of about $6.3 billion.
In its preliminary account, Binance said a compromised laptop belonging to a DevOps engineer may have given an attacker access to a service container, from which unauthorized withdrawal transactions could be submitted. The exchange said it had found no evidence that wallet private keys were compromised. This remains Binance’s preliminary explanation, not a completed technical report.
Binance also said it intends to cover losses using SAFU and company funds, and to publish a technical post-mortem after the investigation and remediation are complete.
Binance put the estimated total impact at about $6.3 billion and said roughly $3 billion had been frozen; both figures are preliminary and may change.
In its latest update found for this report, Binance said it was working with blockchain partners to trace and freeze assets. The exchange’s reported frozen amount was approximately $3 billion. That figure should not be read as a final recovery total: tracing and investigation are still underway.
It is important to distinguish Binance’s estimate from a completed independent audit. Until the exchange publishes its full post-mortem, the precise attack path and final impact remain unsettled.
In Binance’s latest update found for this report, deposits were operating while withdrawals remained temporarily paused.
Binance said it was carrying out security checks and revamping the withdrawal service and related addresses. This status reflects the exchange’s update on October 30, 2026, and may change; readers should check official Binance communications for current service information.
The company’s statement that user funds are safe should be attributed to Binance. A full technical post-mortem had not yet been published at the time of this report.
Operators should review how access is separated across employee devices, internal services, and withdrawal permissions—and how quickly suspicious transactions can be contained.
Binance’s preliminary account makes the access path for withdrawal operations an important area for platform operators to audit. This is a general engineering takeaway, not a confirmed description of a specific flaw in Binance’s systems.
These controls can reduce operational risk, but they cannot guarantee that an attack will be prevented.
No. Binance said it had found no evidence of a wallet private key compromise. That is the company’s preliminary statement; the investigation is ongoing.
It is Binance’s preliminary estimate of the incident’s total impact. The exchange also reported that about $3 billion had been frozen. A final audit and post-mortem were not available at the time of this report.
Binance said it temporarily paused withdrawals while it conducted security checks and revamped the withdrawal service and related addresses.
Not yet. Binance identified a compromised DevOps engineer’s laptop and access to a service container as a possible route, but it has not published a full technical post-mortem.
On October 29, 2026, Bitcoin traded below $77,000 and BNB was down 7.1% over 24 hours amid reports of a Binance security incident. The Block also reported substantial liquidations. These figures describe a specific market snapshot; they do not prove the incident was the sole cause of the broader decline.
In The Block's October 29 snapshot, Bitcoin was at $76,664 after a 4.5% 24-hour decline, while BNB was down 7.1%.
The Block reported that Bitcoin had slipped below $77,000 as several major crypto assets also declined. In the same snapshot, Ether was down 5.2% and XRP was down 7%. These are time-specific figures from the report, not current prices.
The move coincided with reports of a Binance security incident. That timing is relevant to understanding the market response, but it does not by itself establish what caused every part of the sell-off.
At the time of the reports, Binance said it was investigating a potential security issue; The Block reported that the exchange's co-CEO pledged to cover user losses.
The Associated Press described Binance as investigating a potential security issue and reported that the company’s founder said the event looked like a hack. The Block described an exploit and reported that co-CEO Yi He said Binance would cover user losses related to it.
Reports, preliminary estimates and confirmed technical findings are not the same thing. The sources reviewed here do not establish a definitive technical root cause, so a specific attack scenario should not be presented as proven.
The Block reported $1.55 billion in liquidations over 24 hours, including $1.34 billion in long positions.
Forced position closures can accompany sharp market moves and add pressure to prices. The liquidation total is a time-specific figure reported by The Block, citing CoinGlass, rather than a final tally for the entire period following the news.
For trading platforms, a practical takeaway is to review how margin monitoring, risk limits and alerts behave when liquidity or prices shift quickly. This is a general risk-management recommendation, not a claim about the precise mechanisms behind liquidations in this episode.
The episode underscores the value of security and market-risk readiness, but does not reveal a confirmed technical failure mode.
When a major security incident is reported, platform operators can use it as a prompt to review practical readiness in several areas:
This is a general review checklist, not a description of confirmed shortcomings at Binance. The sources do not specify which infrastructure changes the company will make after the incident.
The Block reported the move late on October 29, 2026. Its snapshot at about 10:00 p.m. ET put Bitcoin at $76,664.
The Block reported a 7.1% 24-hour decline in BNB in its October 29, 2026 market snapshot.
In the reports reviewed, Binance said it was investigating a potential security issue. Those reports do not establish a definitive technical root cause.
That is not established. The market decline coincided with reports of the incident, but the available data does not prove it was the sole cause of declines across crypto assets.
On October 29, 2026, Binance reported a security incident and put its preliminary overall impact at about $6.3 billion. The more-than-$5.7-billion figure in reports referred to the value of assets held in wallets linked to the suspected attacker, not a final tally of irrecoverable losses. Binance also said roughly $3 billion in assets had been frozen; the cause was still under investigation.
Binance reported a potential security incident affecting a large volume of crypto assets and began investigating.
Reports published on October 29 cited more than one estimate. Binance later put the incident’s preliminary overall impact at about $6.3 billion. That company estimate does not mean the entire amount was a final, unrecoverable loss.
It is important to distinguish the reported incident, preliminary estimates, and the findings of a completed investigation. Early reports had not established the full attack mechanism or final financial impact.
The figures describe different measures: Binance’s preliminary estimate of about $6.3 billion in overall impact and CoinDesk’s report of more than $5.7 billion in assets held in wallets linked to the suspected attacker.
CoinDesk reported that wallets linked to the suspected attacker held assets worth more than $5.7 billion at one point. The same report discussed other estimates of the assets stolen. The headline claim that Binance “lost $5.7 billion” therefore compresses several different measures: assets tracked in wallets, the exchange’s estimate of overall impact, and any eventual confirmed losses.
When comparing incident figures, check what each number measures: asset movements, the exchange’s own estimate, balances in specific wallets, or confirmed losses.
Binance’s preliminary account pointed to a potentially compromised DevOps engineer’s laptop, but that account is not a final investigative finding.
In its preliminary account, Binance said a compromised device may have enabled access to a service container and the submission of unauthorized withdrawal transactions. The exchange also said it had found no evidence that wallet private keys were leaked.
These are early findings reported by the company, not independent confirmation of the complete technical sequence. While the investigation continues, neither a specific vulnerability nor an attacker’s identity should be presented as conclusively established.
Binance said roughly $3 billion in assets had been frozen and said it would cover incident-related losses using SAFU and company funds.
Binance reported that roughly $3 billion had been frozen on-chain. The exchange also said deposits were no longer affected and that it would cover losses related to the incident using SAFU and company funds. These are the exchange’s statements, not an independent assessment of a completed recovery.
For crypto trading-platform operators and developers, the incident is a reminder to review layered controls. Practical areas include employee access boundaries, endpoint security, approval and monitoring of critical withdrawals, anomaly detection, and incident-response plans. These are general risk-management considerations; they do not establish that any particular missing control caused this incident.
No. CoinDesk used that figure for the value of assets in linked wallets. Binance separately put the preliminary overall impact at about $6.3 billion; neither figure should be treated as a final tally of irrecoverable losses.
Binance reported that about $3 billion in assets had been frozen on-chain. The figure reflects the update available at the time and could change.
Binance said it had found no evidence of a wallet private-key leak. That was a report of preliminary findings, not independent confirmation of every investigative detail.
The sources available for this article do not establish a definitive attribution. Early suggestions about a specific group should not be treated as confirmed.
Binance’s October 1 Proof of Reserves snapshot let CoinDesk match an affected wallet to assets backing customer balances. CoinDesk estimated ETH backing could be around 94% if the withdrawn assets had not been replaced. That is an estimate based on an earlier snapshot, not a confirmed current ratio. Binance said it would cover losses and publish updated reserves after remediation.
On October 30, Binance said its preliminary investigation pointed to a possible compromise of a DevOps engineer’s laptop and access through a service container.
The exchange estimated the total impact at about $6.3 billion and said blockchain partners had frozen about $3 billion in assets at that point. Binance said it had found no evidence that wallet private keys were leaked, temporarily suspended deposits and withdrawals, and would cover losses through its SAFU fund and company funds.
This was Binance’s preliminary account, not a final technical post-mortem. The possible access path should therefore be described as an early investigative finding, not an established final cause.
CoinDesk linked Binance 14 to the October 1 Proof of Reserves snapshot and estimated that ETH backing could be about 94% after the incident if the assets had not been replaced.
CoinDesk’s analysis found Binance 14 in the October 1 reserve snapshot and connected it to wallets later associated with the outflows. The publication reported that customer ETH liabilities were fully covered on the snapshot date and estimated that the withdrawal of roughly 204,500 ETH could reduce ETH backing to around 94% if the exchange had not replenished the asset.
This is a third-party estimate based on a specific snapshot, not Binance’s published post-incident balance. It should not be treated as a confirmed overall reserve ratio or proof that customers cannot access their funds. Binance said it would cover losses and publish updated Proof of Reserves after remediation.
Proof of Reserves helps verify asset and customer-balance data at the time of a snapshot, but it does not provide a continuous, real-time view of reserves.
Binance describes a process that uses a snapshot of customer balances and cryptographic proofs, allowing users to check whether their balances were included in a report. The exchange also notes that a report reflects a particular point in time and may not match current asset holdings.
That makes the October 1 snapshot useful for understanding which wallets and assets were counted then, but it cannot by itself show how much remained after the October 29–30 incident. Updated post-remediation data is needed to assess the later position.
The incident illustrates that reserve verification and wallet-access security address different risks, so platform operators need both kinds of control.
Proof of Reserves can help check reported assets and customer liabilities at a chosen date. Separate access controls and incident response are needed to address unauthorized transactions. Based on the confirmed information in this case, practical considerations include:
These points do not establish which internal security controls Binance did or did not use: the reviewed sources do not include a completed technical report with such findings.
No. It is CoinDesk’s calculation using the October 1 snapshot and estimated ETH outflows, assuming the assets had not been replaced. It is not a final post-incident audit or an overall ratio for all assets.
No. In its October 30 update, Binance said it had found no evidence of a wallet private-key leak. It presented a possible DevOps laptop compromise as a preliminary investigative finding.
Binance said it would publish updated Proof of Reserves after remediation. Its reviewed statement did not give a later specific publication date.
It is a way to report assets held by an exchange and verify that customer balances are included in a report at a particular time. Binance says its report is a snapshot, not a real-time display of assets.
On October 25, 2026, CoinDCX said it lost 15.99 million USDT after an automated process for moving deposits from deprecated wallets failed, and said the company absorbed the loss. The exchange says its active wallets and trading operations were unaffected; that claim is not independently verified by the statement itself.
CoinDCX says deposits continued to reach old wallet addresses while the automated service meant to move those funds was failing for a period.
In an update dated October 25, 2026, CoinDCX linked the unusual activity to earlier wallet infrastructure that it says had been deprecated after a July 2025 security incident. The exchange said a failure in its deposit-sweeping process resulted in a 15.99 million USDT loss, which the company absorbed.
CoinDCX also said some users continued sending funds to old addresses despite guidance to use current addresses shown in its app. This is the exchange’s account of the incident, not independent confirmation of every detail.
CoinDCX says its active wallets, customer balances, and trading operations continued to function, but that claim should not be presented as an independent audit.
The company said its active trading and wallet infrastructure was not paused and that customer assets remain in segregated cold wallets. These are CoinDCX’s statements; the published update does not independently verify the status of every balance.
Blockchain data can help trace token movements, but it does not by itself identify who controlled the addresses or how access was obtained. The transfers alone therefore do not resolve every question about the incident’s mechanism.
CoinDCX’s update did not specify how long the process failed, exactly how the legacy infrastructure was compromised, or provide a complete account of the funds’ movements.
Based on the available statements, it is not possible to establish precisely how the vulnerability arose, how long the sweeping service was unavailable, or how many deposits were affected. Blockchain analysis records transactions and notes limits in attributing addresses; it is not a complete technical report on the cause of the incident.
A practical precaution for users is to check the deposit address and network in the exchange’s official app or website each time they transfer funds. Addresses saved from earlier transactions may no longer be current. This is a general safety step, not a guarantee against loss.
In its October 25, 2026 update, CoinDCX reported a loss of 15.99 million USDT and said the company absorbed it.
The exchange attributed the incident to deprecated infrastructure and a failed deposit-sweeping process. It said active wallets were unaffected; the update itself does not independently verify that claim.
It refers to a process intended to move funds from deposit addresses into an exchange’s primary wallet.
Check the current address and network in the exchange’s official app or website before each deposit instead of relying on a previously saved address.