OfficialresponseStatement 282
Binance told users in its first 30 October update to rely only on official Binance channels for updates.
Please rely only on official Binance channels for updates.
What Binance has said
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.
Official statements that quote a page exactly can publish automatically. Items are reviewed by an AI editor (Claude) under the owner's direction, using exact-quote checks. No lawyer or journalist has reviewed them.
Statements
102 approved statements.
OfficialattributionStatement 283
Binance said in its first 30 October update that it was working with law enforcement partners to confirm the identity of the criminals.
We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.
OfficialamountStatement 162
Binance said in its Security Incident Update dated 2026-10-30 that the estimated total impact sits at around $6.3B.
The estimated total impact sits at around $6.3B.
OfficialfreezeStatement 163
Binance said in its Security Incident Update dated 2026-10-30 that it had worked with blockchain partners to freeze affected assets, with about $3 billion frozen on-chain so far.
We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
OfficialrecoveryStatement 164
Binance said in its Security Incident Update dated 2026-10-30 that it will cover all losses from the SAFU fund and the company's funds, and that user funds are safe.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe.
OfficialwithdrawalsStatement 165
Binance said in its Security Incident Update dated 2026-10-30 that as an immediate precaution it had temporarily suspended withdrawals, revoked the affected address authorisation, and engaged law enforcement and blockchain intelligence partners.
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.
OfficialresponseStatement 166
Binance added a note to its Security Incident Update dated 2026-10-30 saying the announcement was updated on 2026-10-30 to clarify that deposits remain unaffected.
Note: This announcement was updated on 2026-10-30 to clarify deposits remain unaffected and continue to operate as normal.
OfficialreservesStatement 916
Binance said in its Security Incident Update dated 2026-10-30 that it will also publish an updated Proof of Reserves once the remediation is complete.
We will also publish an updated Proof of Reserves once the remediation is complete.
ReportedwithdrawalsStatement 126
Cointelegraph reported that Binance said withdrawals remained paused while it completes a security revamp, with service expected to resume within 48 hours.
Binance said withdrawals remain paused while it completes a security revamp of its withdrawal service and related addresses, with service expected to resume within 48 hours.
ReportedresponseStatement 241
TRM Labs wrote that Binance said it was investigating a potential security issue, then said it had temporarily suspended withdrawals on multiple networks as a precaution, and that Binance has said user funds are safe.
Binance said it was investigating a potential security issue, then said it had temporarily suspended withdrawals on multiple networks as a precaution. Binance has said user funds are safe.
ReportedfreezeStatement 243
Binance co-CEO Yi He said Ripple helped stop about USD 200 million from moving; TRM reports a 40.5M RLUSD freeze; the sources do not say whether the figures measure the same thing.
Binance co-CEO Yi He said Ripple helped stop about USD 200 million from moving; TRM has confirmed the 40.5 million RLUSD freeze onchain.
ReportedattributionStatement 346
Cointelegraph reported that the speaker wrote that Binance's investigation has not attributed responsibility to any individual.
“Our investigation has not attributed responsibility to any individual,” he wrote.
ReportedfreezeStatement 223
The Guardian reported that Binance has said the attack began with a compromised employee laptop and involved multiple breach points, that it found no evidence of private-key leakage, and that it said roughly $3bn of affected assets had been frozen.
Binance has said the attack began with a compromised employee laptop and involved multiple breach points. It found no evidence of private-key leakage and said roughly $3bn of affected assets had been frozen.
ReportedrecoveryStatement 231
Binance pledged to meet customer losses through its SAFU reserve and company resources, announcing more than $6.34bn of company funds separate from roughly $3bn of frozen assets.
Binance has pledged to meet customer losses through its SAFU reserve and company resources, announcing more than $6.34bn of company funds separate from roughly $3bn of frozen assets.
Reportedroot causeStatement 129
Cointelegraph reported that Binance said its investigation had uncovered additional points of breach after initially pointing to a possibly compromised laptop, and that it remained on track to resume withdrawals in 45 hours.
Binance’s investigation into its $6.3 billion hack has uncovered “additional points of breach,” the exchange said , 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.
ReportedrecoveryStatement 131
Cointelegraph reported that Binance said it had set aside more than $6.34 billion in company funds to cover losses, of which $5 billion was already held in the same tokens affected by the attack.
Binance has set aside 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.
ReportedreservesStatement 132
Cointelegraph reported that co-CEO Yi He said Binance was buying altcoins in quantities matching those stolen as it prepares updated proof of reserves.
Binance is buying altcoins in quantities matching those stolen in the hack as it prepares updated proof of reserves,
ReportedresponseStatement 455
Binance stated that it is still gathering the facts and will share more directly as it has them.
“We are still gathering the facts, and will share more directly as we have them,” it wrote.
ReportedreservesStatement 133
Cointelegraph reported that a Binance spokesperson said the $5 billion in matching tokens is held in the exchange's custody and declined to disclose wallet addresses.
A Binance spokesperson told Cointelegraph that the $5 billion in matching tokens is held in the exchange’s custody. The spokesperson declined to disclose wallet addresses, citing security reasons.
ReportedregulatorStatement 342
Cointelegraph reported that Binance said it submits weekly reports on company funds to Abu Dhabi's Financial Services Regulatory Authority under a requirement that predated the hack.
The exchange also said it submits weekly reports on company funds to Abu Dhabi’s Financial Services Regulatory Authority under a requirement that predated the hack.
ReportedreservesStatement 474
Cointelegraph reported that a Binance spokesperson declined to disclose wallet addresses, citing security reasons, and that Binance did not disclose when it acquired the assets.
The spokesperson declined to disclose wallet addresses, citing security reasons. Binance did not disclose when it acquired the assets.
ReportedreservesStatement 361
Cointelegraph reported that the speaker said the exchange's revenue for the year was sufficient to cover the hack losses and that the company did not need to sell its stake in SpaceX.
that the exchange’s revenue for the year was sufficient to cover the hack losses and that the company did not need to sell its stake in SpaceX.
ReportedreservesStatement 362
Cointelegraph reported that the speaker said Gulf, Binance's partner in Thailand, had offered financial support.
he said Gulf, Binance’s partner in Thailand, had offered financial support.
ReportedreservesStatement 363
Cointelegraph quoted a Binance spokesperson as saying the $5 billion is held in the exact token assets required and is in Binance custody.
“The $5 billion is held in the exact token assets that are required. These assets are in Binance custody,” a Binance spokesperson told Cointelegraph.
ReportedrecoveryStatement 203
The Block reported that Binance said it had reserved over $6.34 billion in company funds to offset its losses.
Binance said it has reserved over $6.34 billion in company funds to offset losses it suffered in a recent breach.
Detected edits to Binance pages
Tracked Binance pages are captured again on a schedule. This list shows a page only when its text differs between two captures in a way a reader would notice (link fragments, cookie banners and layout are ignored). Binance's numbered update notes, such as Security Incident Update #2 or Recovery Update #3, are separate pages: each appears under Statements above, and appears here only if the text of one of them was edited. Edits are shown line by line on Changes.
No edit to a tracked Binance page has been detected in the captures stored so far.
What Binance said before the hack
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 the AI editor (Claude) has checked it against the Wayback Machine copy and approved it.
Archived quotes
No quote from an archived page has been approved yet.
Archived pages collected
No Wayback Machine copy of a Binance page has been collected yet.