Binance Edited Hack Statement Twice in 13 Mins as $6.3B Breach Unfolded
Binance published its first statement on X at 21:16 UTC on October 29 (02:46 IST on October 30), around 52 minutes after the main Ethereum wallet sweep linked to the incident.
The exchange edited the statement at 21:24 UTC and again at 21:29 UTC. The original version said Binance had “not confirmed any impact to user funds.” The first edit removed that sentence. The second added: “User funds are completely safe.”
None of the three versions used the word “hack.” Binance continued to describe the incident as a “potential security issue” while its investigation was underway.
Binance issued three X statements, shifting from uncertain impact to asserting user funds are safe.
Co‑founder Changpeng Zhao labeled the event a hack on X before Binance’s official assurance.
Binance’s security team later attributed the breach to a compromised DevOps engineer’s laptop, promising full loss coverage.
The wording changes are notable because they gave readers different versions of the exchange’s initial response. FinanceFeeds noted that some media outlets cited the original wording, while others referred to the updated assurance.
The Crypto Times has independently verified X’s full edit history. The timestamps and wording below are based on the review.
Three versions of one Binance statement
| Version | Time (UTC / IST) | Wording on user funds | What changed |
|---|---|---|---|
| Original | 21:16 / 02:46 | “At this stage, we have not confirmed any impact to user funds.” | Binance said it was investigating reports of a potential security issue. |
| Edit 1 | 21:24 / 02:54 | No specific statement on user funds | The sentence saying Binance had not confirmed an impact was removed. |
| Edit 2 | 21:29 / 02:59 | “User funds are completely safe.” | Binance added a direct assurance about customer funds. |
The rest of the statement remained largely unchanged. Binance said its security teams were reviewing relevant information and that it would share updates through official channels once details were verified. It also warned users against unofficial links, messages and requests for account information.
CZ called it a hack before Binance did
The timing of the edits is notable because Binance co-founder Changpeng Zhao had already described the incident as a hack.
At 21:15 UTC, one minute before Binance’s first statement, Zhao posted on his X account: “User funds are safe! It does look like a hack on Binance.” Zhao added that he no longer manages Binance.com but, as a shareholder, expected all user funds to be fully covered. He also thanked Tether and Circle for freezing assets linked to the incident.
Binance’s final wording aligned with Zhao’s assurance that user funds were safe, but the exchange continued to use the phrase “potential security issue” rather than confirming a hack in that initial post.
Zhao’s comments were made in his capacity as a shareholder, not as the exchange’s operational chief. He stepped down as Binance CEO in November 2023.
From “potential security issue” to a $6.3B impact estimate
Binance’s public language evolved as the investigation progressed. The exchange initially described the incident as a potential security issue, later suspended deposits and withdrawals, and eventually published a more detailed account of the suspected breach.
The sequence below separates Binance’s own statements from comments made by its executives.
| Time (UTC) | Statement or development | What Binance or its executives said |
|---|---|---|
| 21:15, Oct. 29 | CZ comments on X | Zhao says the activity “does look like a hack on Binance.” |
| 21:16, Oct. 29 | Binance’s first X statement | The exchange says it has not confirmed any impact on user funds. |
| 21:24, Oct. 29 | First edit | The sentence about unconfirmed impact to user funds is removed. |
| 21:29, Oct. 29 | Second edit | Binance adds: “User funds are completely safe.” |
| 22:15, Oct. 29 | Withdrawal update | Binance says withdrawals will resume once the security issue is resolved and repeats that user funds remain safe. |
| Oct. 30, 02:23 UTC | Detailed security update | Binance estimates the incident’s impact at approximately $6.3 billion and says around $3 billion in affected assets has been frozen on-chain. |
In its October 30 security update, Binance said its initial investigation suggested that a compromised DevOps engineer’s laptop may have allowed an attacker to access a service container and submit unauthorized withdrawal transactions.
The exchange said it had found no evidence of a wallet private-key leak. It also said it would cover all losses through its Secure Asset Fund for Users (SAFU) and company funds, and publish an updated proof-of-reserves report after remediation.
Binance’s $6.3 billion figure is its estimate of the incident’s total impact. It should not be interpreted as the amount still unrecovered: the exchange said approximately $3 billion in affected assets had been frozen on-chain by the time of its update.
Why the edits matter
An exchange’s first public statement during a security incident can shape how customers, trading counterparties and other platforms assess the risk. In this case, the wording changed from an acknowledgment that Binance had not confirmed an impact on customer funds to a categorical assurance that those funds were safe.
The distinction is important. The exchange was still investigating the incident when it made the assurance, and unauthorized transfers were continuing during the wider attack.
Binance later said it would cover all losses using SAFU and company funds. That commitment provides a clearer explanation of how the exchange intends to protect customers, but it does not explain why the original statement was edited or how the attacker was able to submit unauthorized withdrawals.
The exchange has said it will publish a detailed technical post-mortem after its investigation is complete. It has not publicly explained the reasoning behind the two edits to its initial X statement.
The incident has also prompted scrutiny of Binance’s hot-wallet controls and reserve disclosures. As The Crypto Times reported, Binance plans to publish an updated proof-of-reserves snapshot after completing remediation.
For now, the edit history provides a record of how Binance’s initial public wording changed. The full technical explanation, including how the unauthorized withdrawals were approved, remains pending.
Also Read: Binance Hack LIVE Updates: The $6.3 Billion Security Breach
Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.


