Officialroot causeClaim 281
Binance said in its first 30 October update that it had found no evidence of any wallet private key leak.
We have found no evidence of any wallet private key leak.
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.
Statements
110 approved statements.
OfficialresponseClaim 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.
OfficialattributionClaim 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.
Officialroot causeClaim 161
Binance said in its Security Incident Update dated 2026-10-30 that its initial investigation suggested the incident may involve a compromised DevOps engineer's laptop, which allowed an attacker to access a service container and submit unauthorized withdrawal transactions, and that it had 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.
OfficialamountClaim 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.
OfficialfreezeClaim 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.
OfficialrecoveryClaim 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.
OfficialwithdrawalsClaim 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.
OfficialresponseClaim 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.
ReportedwithdrawalsClaim 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.
Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (4:17 am UTC), not a time stated by the speaker.
ReportedresponseClaim 241
Binance confirmed a security incident and suspended withdrawals on several networks, stating that 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.
ReportedfreezeClaim 243
Binance co-CEO Yi He stated that Ripple helped stop about USD 200 million from moving.
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.
Reviewer note: Yi He's figure is Binance's side of a disagreement: TRM confirmed 40.5 million RLUSD frozen on-chain.
ReportedattributionClaim 346
Cointelegraph reported that Richard Teng wrote that Binance's investigation has not attributed responsibility to any individual.
“Our investigation has not attributed responsibility to any individual,” he wrote.
ReportedfreezeClaim 223
Binance stated that the attack began with a compromised employee laptop, involved multiple breach points, and that it found no evidence of private-key leakage while freezing roughly $3bn of affected assets.
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.
ReportedrecoveryClaim 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 causeClaim 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.
Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (8:37 am UTC), not a time stated by the speaker.
ReportedrecoveryClaim 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.
Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (10:55 am UTC), not a time stated by the speaker.
ReportedreservesClaim 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,
Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (11:07 am UTC), not a time stated by the speaker.
ReportedresponseClaim 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.
Reviewer note: Binance post on X as relayed by Cointelegraph. Event time not stated.
ReportedreservesClaim 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.
Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (12:41 pm UTC), not a time stated by the speaker.
ReportedregulatorClaim 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.
ReportedreservesClaim 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.
ReportedrecoveryClaim 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.
ReportedfreezeClaim 204
The Block reported that Binance co-CEO Yi He said Ripple promptly froze roughly $200 million in associated funds.
Ripple "promptly" froze roughly $200 million in associated funds, co-CEO Yi He [said]
Reviewer note: TRM, by contrast, confirmed a 40.5 million RLUSD freeze on-chain.
Reportedroot causeClaim 134
Cointelegraph reported that co-CEO Richard Teng said the attacker used an EIP-7702 delegation to gain execution authority over a hot wallet, and that the delegation did not pass through Binance's normal approval controls.
The attacker used an EIP-7702 delegation to gain execution authority over a hot wallet, Teng said. That delegation “did not pass through our normal approval controls.”
Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (2:34 pm UTC), not a time stated by the speaker.
Detected edits to Binance pages
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.
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 a person has checked it against the archived copy and approved it.
Archived quotes
No quote from an archived page has been approved yet.
Archived pages collected
No archived copy of a Binance page has been collected yet.