Reporting: sourced factual coverage reviewed by the editorial desk.
Binance’s November 3 initial report says unauthorized access to an internal wallet signing service enabled the October 29 theft, which it estimates affected $6.34 billion in digital assets. The report is a new account of an earlier attack, not evidence of a new theft today.
The exchange says approximately $2.85 billion had been frozen or intercepted, subject to reconciliation and market-price changes. Those assets should not be treated as money already returned. Binance says it will absorb the financial impact and that 98% of impacted token assets had been replenished as of October 31; RailsRecord has not independently audited those balances.
According to Binance, compromised employee computers, stolen deployment credentials and an internal AI tool formed part of the attack path. It says onchain authorizations allowed movements outside its ordinary withdrawal infrastructure, so suspending customer withdrawals alone did not fully contain the incident. The company describes subsequent revocation work and rebuilt systems.
For readers, the distinction is between the exchange’s withdrawal interface and permissions already granted on a blockchain. Stopping one route does not necessarily terminate the other. That is the operational issue highlighted by the company’s account, rather than evidence that every wallet using the same technology is compromised.
Binance calls its findings preliminary and says independent security review is being arranged. Its assurances about replenishment and remediation remain statements from the affected company, not completed independent review. This report does not establish that every asset or withdrawal network is available now; readers need the exchange’s asset-specific service notices for that question.
The accompanying conceptual vault-and-conduit composition illustrates signing access and containment. It does not depict an actual Binance facility, employee or attack scene.


Join the conversation
Share your perspective and reply to other readers in Community.
Discuss this article →