Yellow Binance wordmark on a black background.

Binance’s $6.3 billion hack and the security of wallet signing

Binance reported $6.34 billion in affected assets. Its preliminary findings show how compromised access reached an internal wallet signing service and why approval must be enforced at execution.

What does the $6.3 billion figure mean?

Binance’s November 3 preliminary report puts the virtual assets affected by the October 29 incident at approximately $6.34 billion. Binance said it was absorbing the impact, had replenished 98% of the affected token assets as of that update, and that roughly $2.85 billion had been frozen or intercepted, subject to reconciliation and price volatility. Those figures describe different things. A freeze is a restriction on movement, and replenishment describes assets the exchange says it put back. Binance’s preliminary findings

How did access reach the wallet signing service?

Binance’s preliminary account describes social engineering involving fake recruiting activity, compromised employee devices, misuse of an internal AI tool as a foothold, and stolen credentials used to reach wallet operations. The exchange said unauthorized access to its signing service let transactions bypass its normal withdrawal flow. That is the exchange’s current account of the sequence, and the full findings may change as the investigation develops. Binance’s October 30 response

Yellow Binance wordmark on a black background.

Where should a sensitive action be stopped?

A useful review starts at the system that can actually move money. Trace whether a single developer identity can change a service, deploy code, and request a signature. Separate those permissions, verify the destination and amount at signing, and require approval tied to the exact transaction. Make high-risk authorizations short-lived and log the request, policy decision, approver and execution together.

Test the emergency path before relying on it. Teams should be able to suspend signing, revoke affected credentials, and reconcile queued or in-flight transactions. An insurance review can then focus on evidence of which controls were operating and who can exercise them.

What is ImadDhin exploring with Xion?

For blockchain teams, the next step is a security-first delivery workflow: define custody and permissions, build in isolation, verify contract and infrastructure behavior, and independently approve production changes. Explore blockchain engineering and guided AI workflows.

Xion is a security product concept in development. Its policy simulation explores when an AI-assisted request should be allowed, blocked, or held for independent approval. The aim is to make the identity, requested action, destination and approval visible in one decision record. The interactive demo uses synthetic scenarios. Explore the Xion simulation

Optional Bybit referral

Affiliate disclosure: ImadDhin may receive a commission or referral benefit if you use this Bybit referral link. This is separate from our engineering services, is not a security endorsement or investment advice, and does not imply an exchange is risk-free. Crypto assets and exchange custody carry risk. Check availability and eligibility in your location and Bybit’s terms.

Take the next step

Try a simulated policy decision for a sensitive AI workflow.

Explore Xion

Bring one workflow and the systems it needs to access.

Let's Talk

Keep reading