8thGuard / insights

The Binance Breach: What a Signing Service Can Make Possible

Binance’s initial findings describe compromised staff devices, an internal AI tool and unauthorised access to a wallet signing service. The incident exposes a question for every organisation: what can a compromised permission actually do?

Bitcoin coin photographed in front of a Binance sign
Bastian Riccardi / Pexels

A permission can be small on an access list and enormous in practice. The question is what it allows someone to do once they have it.

On 29 October 2026, Binance suffered an attack that the FBI says resulted in the theft of more than $6 billion in virtual assets. The FBI attributed the theft to North Korean actors it calls TraderTraitor. That attribution is the agency’s assessment; the investigation continues.

In its initial findings published on 3 November, Binance described a chain of events involving compromised employee devices, social engineering and an internal AI tool. The company said the attacker used unauthorised access to a wallet signing service to initiate transactions outside the normal withdrawal process. Those findings are Binance’s account of an evolving investigation, not an independent audit.

Why stopping withdrawals was not enough

A wallet signing service authorises transactions. If an attacker can make that service approve an action, the network may see a valid authorisation even when the organisation never intended it. The security question is therefore not only who possesses a private key. It is also who can reach the systems and permissions that produce valid signatures.

Binance says the attacker used Ethereum’s EIP-7702 authorisation mechanism to give an attacker-controlled contract partial execution rights over a hot wallet. The company says it suspended withdrawals, worked with partners to freeze affected tokens and took steps to revoke unauthorised permissions. It reported $2.85 billion in assets frozen through those efforts. A freeze is not the same as a completed recovery.

The company said existing on-chain authorisations continued to operate independently of its normal withdrawal infrastructure. Suspending a customer-facing service did not automatically cancel those authorisations. Binance said additional transactions were needed to clear them.

What customers and businesses can take from this

For a business holding assets with a provider, an incident raises ordinary but difficult questions: can I access my funds, what information has the provider published, and which claims can be verified? Check the provider’s official updates through a familiar address you enter yourself. Treat urgent messages offering recovery or requesting wallet credentials as suspicious. Never give anyone a recovery phrase to release funds.

For an institution, the questions extend to the systems behind the service. How are signing privileges separated? Can an administrator or automated tool reach sensitive operations? How quickly can the firm identify and revoke a compromised authorisation? What evidence supports its statements about reserves and recovery?

A proof-of-reserves snapshot can provide useful evidence about assets at a particular time. It is not a complete substitute for information about liabilities, controls or the next incident. Likewise, an on-chain observation can show a transaction or permission without explaining every off-chain decision that produced it.

Binance says it has rebuilt affected systems, replaced devices and decommissioned relevant credentials. It also says independent cybersecurity experts will review the incident. Those actions and the final findings deserve scrutiny as more evidence becomes public.

Sources: Binance, 29 October 2026 Binance Security Incident: Initial Findings and Response Update, published 3 November 2026; FBI Cyber, North Korea Responsible for $6 Billion+ Binance Attack, published 31 October 2026; Binance, Security Incident Recovery Update 5, published 2 November 2026.

Source links

Binance incident report: https://www.binance.com/en/blog/community/3229153443759566763

FBI attribution: https://www.fbi.gov/investigate/cyber/alerts/2026/north-korea-responsible-for-6-billion-binance-attack

Binance recovery update: https://www.binance.bh/en-GB/support/announcement/security-incident-recovery-update-5-october-31st-por-snapshot-now-fully-verifiable-by-users-as-zk-proof-generated-2026-11-02-185bd9a4717f44088b3be70287b8237f