Independent record. Not associated with, endorsed by or operated by Binance. We will never ask you to connect a wallet, log in or pay to recover funds.
An independent record of the October 2026 Binance hack
Statements from Binance-published sources, and from people whose recorded role mentions Binance, in date order, oldest first. These are official statements: the party said it, which is not the same as it being true.
109 approved statements.
Binance says it will cover all losses from its SAFU reserve and company funds, and that user funds are safe.
Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day. Hacken relays a Binance statement.
The world's biggest cryptocurrency exchange reported Thursday that approximately $6.3 billion was impacted in an apparent hack.
Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day.
Zhao posted Thursday on X that "User funds are safe!" but added that the theft "does look like a hack on Binance."
Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day.
At around 2026-10-29 20:05 (UTC), our hot wallets were compromised, resulting in a loss of approximately $6.3B USD worth of token assets.
Reviewer note: Binance states the time as 'around 2026-10-29 20:05 (UTC)'.
A Binance spokesperson told Cointelegraph on Thursday that the exchange was investigating reports of a potential security issue but had not confirmed any impact on user funds.
Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (9:15 pm UTC), not a time stated by the speaker.
the activity appeared to be a hack, adding that Tether and Circle had frozen approximately $971 million and $823 million, respectively.
23:35 | Binance states that the verified frozen total is $2.54B.
Reviewer note: Hacken relays a Binance statement and cites TRM for it.
Binance said the verified total of assets frozen in connection with the hack had reached $2.54 billion, clarifying differing figures circulating publicly, including references to $1.8 billion.
Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (11:35 pm UTC), not a time stated by the speaker.
the verified total of assets frozen in connection with the hack had reached $2.54 billion, clarifying differing figures circulating publicly, including references to $1.8 billion.
co-CEO Richard Teng said the attacker "did not simply use one engineer's permissions, and this was not a single 'one-click' action."
Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day.
It said Friday that it was beginning to recover assets for users.
Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day.
In a video update on October 30, Binance co-CEO Richard Teng said he was hopeful that withdrawals would resume before Sunday, October 31.
Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day.
Binance, the world's biggest cryptocurrency exchange, worked on Friday to shore up public confidence after a record $6.3 billion hack of its platform, promising it would cover all losses from company funds and allow clients to trade again within days.
Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day.
Binance said customer funds were safe and it is working with industry partners to freeze some of the affected assets, with about $3 billion located so far.
Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day.
Binance co-CEO Yi He said in a post on X that $3 billion represented only about 2% of the company's total user assets and public reserves.
Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day.
The exchange also said on Friday afternoon US eastern time that its technical team was targeting a resumption of withdrawal services within approximately 34 hours.
Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day.
Binance said it has set aside around $6.34 billion of company funds internally to cover the losses.
Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day.
Binance's other co-CEO, Richard Teng, said in a post on X that the breach was a "complex attack" that was not carried out by one person and included a compromised laptop as well as malicious software designed to delete evidence of its activity as it went along, "making it more difficult for us to trace and investigate."
Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day.
The hackers were able to manipulate a system used to approve transactions to move money out of a Binance-controlled, internet-connected so-called "hot" wallet in a way that did not pass through normal approval controls, Teng said.
Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day.
Binance said it has temporarily suspended deposits as it conducts security checks, freezes funds and coordinates with law enforcement.
Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (12:07 am UTC), not a time stated by the speaker.
deposits as it conducts security checks, freezes funds and coordinates with law enforcement. It previously confirmed it had suspended withdrawals.
Binance said the current verified amount of assets frozen from the hack is now $3 billion.
Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (12:52 am UTC), not a time stated by the speaker.
Binance's update of 02:23 UTC, Oct 30 , says its initial investigation "suggests that the security incident may involve a compromised DevOps engineer's laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions," and that it has "found no evidence of any wallet private key leak."
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions.
We have found no evidence of any wallet private key leak.
Tracked Binance pages are captured again on a schedule. When the text of a page changes between two captures, the change is logged here and shown line by line on Changes.
No edits to tracked Binance pages have been detected yet.
Copies of Binance pages kept by the Internet Archive's Wayback Machine, captured before 29 October 2026, of selected pages: proof of reserves, about, security-related help articles and terms of use. They show what a page said when the Wayback Machine's crawler saw it, which can be later than when the words were written, and they say nothing about what is true. A quote appears below only after a person has checked it against the archived copy and approved it.
No quote from an archived page has been approved yet.
No archived copy of a Binance page has been collected yet.