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.
63 approved statements.
Binance [says](https://x.com/binance/status/2115993361517891592) 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.
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](https://x.com/binance/status/2115947325617299903) 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.
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 said it has temporarily [suspended](https://x.com/binance/status/2115960292115124558) 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.
Binance [said](https://x.com/binance/status/2115970069696217576?a=UY3TfEEm4R462RHRUPo&s=20) 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](https://x.com/binance/status/2115993361517891592) , 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.
The estimated total impact sits at around $6.3B.
We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe.
As an immediate precaution, Binance has: - temporarily suspended withdrawals while security checks are completed; - revoked the affected address authorisation; - engaged law enforcement and blockchain intelligence partners to trace and recover funds.
Note: This announcement was updated on 2026-10-30 to clarify deposits remain unaffected and continue to operate as normal.
Binance said withdrawals [remain](https://x.com/binance/status/2116026356740034858?a=9FDgHcAuOzrDhGef-Q0&s=20) paused while it completes a security revamp of its withdrawal service and related addresses, with service expected to resume within 48 hours.
Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (4:17 am UTC), not a time stated by the speaker.
Binance’s investigation into its $6.3 billion hack has uncovered “additional points of breach,” the exchange [said](https://x.com/binance/status/2116089661408108712) , after initially pointing to a potentially compromised laptop. The exchange said it was still gathering facts in coordination with law enforcement. Binance said it remained on track to resume withdrawals in 45 hours, while deposits remained unaffected.
Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (8:37 am UTC), not a time stated by the speaker.
Binance has set [aside](https://x.com/binance/status/2116121748555153621) more than $6.34 billion in company funds to cover losses from the hack, the exchange said. The company said $5 billion of those funds were already held in the same tokens affected by the attack.
Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (10:55 am UTC), not a time stated by the speaker.
Binance is buying altcoins in quantities matching those stolen in the hack as it prepares updated proof of reserves,
Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (11:07 am UTC), not a time stated by the speaker.
A Binance spokesperson told Cointelegraph that the [$5 billion in matching tokens](https://cointelegraph.com/news/binance-5-billion-replacement-crypto-in-custody) is held in the exchange’s custody. The spokesperson declined to disclose wallet addresses, citing security reasons.
Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (12:41 pm UTC), not a time stated by the speaker.
Binance said it has reserved over $6.34 billion in company funds to offset losses it suffered in a recent breach.
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.