The Binance hack affected $6.3 billion worth of digital assets, drawing attention as the largest security incident involving a cryptocurrency exchange in history. The exchange initially did not disclose that a compromised engineer laptop was the starting point of the incident, but its acknowledgment that additional entry points had been identified made it difficult to explain the full sequence of the attack through the initial account alone.
$6.3B in Losses: Tracking Must Continue After Asset Freezes
Binance said it had frozen roughly half of the affected assets. Nevertheless, the attacker still holds a significant amount of stolen assets, and the company said it would compensate all losses. The freezes do not necessarily mean that the attack has been contained or that the underlying infrastructure for withdrawals has been blocked. Instead, it shows that the process of tracing where the funds moved remains unfinished.
Tether and Circle said they had frozen a combined total of approximately $2.4 billion in assets in response to the incident. World Liberty Financial said it was working with partners to freeze the stolen assets. Coinbase said it had not been affected by the incident and was monitoring the situation.
A Multi-Stage Attack From Laptop to Withdrawal Environment
Binance co-CEO Richard Teng said the initial investigation found that the attack began on a compromised engineer laptop. He explained that the attacker used the laptop to access service containers and submit unauthorized withdrawal transactions.
The attack was not a simple, one-time click carried out using a single engineer’s credentials. Teng emphasized that it involved a complex, multi-stage attack and said no evidence of a wallet private-key compromise had been found as of the latest update. Jayant Dave of Check Point pointed to similarities with the recent Bitget hack, analyzing that attackers may target the systems and people authorized to use vault keys rather than the keys themselves.
This structure reveals why the operational environment cannot be considered secure based solely on the safety of private keys. If the process for creating, approving, and executing withdrawal requests is concentrated in a single account or piece of credential information, an attacker who gains control of those privileges could cause widespread losses. To limit the potential scope of an internal breach, organizations must verify that laptop endpoints, administrative privileges, service containers, and the withdrawal approval system are not connected through a single attack path.
Analysis and Official Positions Diverge Over a TraderTraitor Link
Check Point and TRM Labs analyzed the attack as connected to the activities of TraderTraitor, a hacking group linked to North Korea. Check Point described the group as also being known in the industry as the Lazarus Group, the organization widely blamed for the 2025 Bybit hack. TRM Labs likewise reported that the incident shared several similarities with previous North Korea-linked cases, including the Bybit hack.
Chainalysis also assessed with high confidence that a North Korea-linked organization was involved in this hack. Ari Redbord, global head of policy at CipherTrace, characterized the Binance hack as a turning point the industry had not previously seen. Binance, however, has not officially identified the perpetrators and said it is working with law enforcement to determine who was responsible and bring them to justice.
Withdrawal Suspension and the Remaining Post-Incident Challenges
Binance suspended withdrawals until it could verify the security environment. Co-CEO Yi He explained that the decision to suspend withdrawals was made because safety had to come first. The suspension is currently an available defense against further damage, but it must lead to verification that the entry points are genuine and proof that the incident cannot recur.
Binance said it plans to release a detailed post-incident review once the investigation is complete. In the meantime, the company has said it is continuing to gather facts and will share more specific information immediately as it is discovered. The core of strengthening exchange security lies in distributing withdrawal privileges, continuously detecting anomalous activity across operational environments, and rechecking the intrusion path after an attack. The $6.3 billion hack will remain a stark example of how a combined path linking operational privileges with the execution environment can cause damage on a much broader scale than private-key exposure alone.
Source Note
This article was written with reference to the following source: BBC Tech — Crypto giant Binance hit by $6.3bn hack suspected to be largest in history









