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.