Q-Cyber Magazine · Incident report

Fintech · 23 November 2026 · 7 min read · Updated

Binance heist: about $6.3 billion taken through an internal wallet signing service

On 29 October 2026, an attacker used unauthorised access to an internal Binance wallet signing service to move about $6.3 billion in digital assets. The FBI attributed the theft to North Korea.

A set of keys left in the lock of an open door

23 November 2026. Binance, the world's largest cryptocurrency exchange, lost about $6.3 billion in digital assets on 29 October 2026 after an attacker gained unauthorised access to an internal wallet signing service and used it to send funds from the exchange's hot wallets outside the normal withdrawal process. The FBI has attributed the theft to North Korea.

What happened

According to Binance's initial report, the attacker exploited unauthorised access to an internal wallet signing service to initiate transactions outside the normal withdrawal process. From 20:05 UTC on 29 October, Binance hot wallets on the XRP Ledger, Solana, Optimism and Bitcoin networks sent funds to attacker-controlled addresses. Binance says it received an internal alert about large-volume transfers and began investigating.

The attacker then used the signing service to abuse an Ethereum authorisation mechanism (EIP-7702), giving an attacker-controlled smart contract partial execution rights over a Binance hot wallet. Binance says suspending withdrawals could not stop those authorisations, because they existed on-chain and operated independently of its withdrawal systems. The hot wallet used multi-party computation (MPC), so there was no single private key that could revoke the authorisations at once; the exchange had to develop and run a dedicated procedure, which took additional time. Binance reports that the final unauthorised transfer was finalised at 23:56 UTC, and that it cleared the delegation at 00:10 UTC on 30 October.

How the attacker got in

Binance describes the incident as a sophisticated, multi-stage campaign rather than a single breach or a simple phishing incident. Its report sets out the following sequence:

  • June 2026. An engineer on the wallet infrastructure team downloaded a tampered installation package for a popular AI coding tool after finding it through a search engine. Binance's security team detected the anomaly, replaced the device and rotated related credentials, but says the engineer's role and colleagues were exposed to the attacker.
  • September 2026. A second engineer was contacted on a legitimate job-hunting platform by someone posing as a project director. After a video interview with a purported HR representative, a second interview on a chat app ended with an instruction to download an "assignment" onto his work computer. The code repository contained malware that, according to Binance, was not detected by its endpoint protection at the time. Binance called the approach "more advanced and deceptive than previously seen social engineering approaches".
  • 20 October 2026. Using the compromised computer, the attacker used an internal AI tool to gain control over the first engineer and a third engineer, and found a container deployment permission token on the first engineer's computer.
  • 29 October 2026. The attacker logged on to the third engineer's computer, used the stolen credentials to deploy a container and triggered a script that launched the attack.

Binance says some technical details will remain confidential so that they cannot be used to plan further attacks. Binance's chief executive, Richard Teng, said the attacker used a self-destruct mechanism that destroyed tooling and traces, The Record reported.

Who is affected

Binance says it will absorb the financial impact of the stolen funds, not its users, and that it set aside more than 100% of the funds required. The exchange suspended transactions after the incident and reopened for deposits and withdrawals on Sunday 1 November. Binance said on X that between 06:00 and 15:30 GMT that day it processed $4.649 billion in withdrawals and $1.01 billion in deposits, a net outflow of about $3.64 billion, the BBC reported.

What is confirmed, and what is not

Attribution. According to FBI statements reported by The Record and CoinDesk, the FBI attributed the theft to North Korea's TraderTraitor activity, working with the US Secret Service and IRS Criminal Investigation. The FBI said the actors were converting stolen assets primarily into Ether and expected further laundering through decentralised finance (DeFi) and instant swap services. It published a list of addresses and asked exchanges, DeFi services, node operators, blockchain analytics firms and other virtual asset service providers to block transactions with or derived from them. Binance's report cites the FBI's finding.

Figures that differ. The amount taken is given as about USD 6.34 billion by Binance, more than $6.3 billion by The Record and more than $6 billion in the FBI's statements as reported. Figures for recovery vary by source and date:

  • Frozen or intercepted: about USD 2.85 billion according to Binance's report of 3 November, "subject to reconciliation and market price volatility"; more than $2.4 billion frozen by stablecoin issuers, according to CoinDesk on 31 October; about $3 billion according to blockchain security experts cited by The Record on 2 November. The Secret Service said it worked within minutes of the attack to "identify and freeze a significant portion" of the stolen cryptocurrency.
  • Replenished by Binance: 90% according to CoinDesk on 31 October; around 95% according to the BBC on 2 November; 98% of impacted token assets as of 31 October according to Binance's report of 3 November, which says the remaining, more illiquid assets are being purchased.

Not yet published: the findings of the independent review Binance has commissioned, and the technical details Binance has chosen to keep confidential.

The official response

The FBI, the Secret Service and IRS Criminal Investigation asked the crypto industry to block transactions linked to the published addresses. Binance says it has closed the entry points identified in the attack, rebuilt the affected wallet system in a new environment, rebuilt the affected internal AI tool and its access controls, replaced affected devices, decommissioned the credentials and tokens of affected engineers, and tightened device controls and wallet-service risk controls. It is engaging independent security firms to review the incident and says it is reviewing its incident response process, signing policy coverage and hot-wallet controls.

What it means

  1. The signing service is the vault door. The attacker did not need to break any cryptography. Access to the service that signs transactions was enough to move funds outside the normal withdrawal process. Signing policy, such as limits, destinations and approvals, should be enforced at the signer itself and not only in the systems in front of it. Knowlcom's data security practice keeps key custody and use under the institution's control; see also key management and custody controls for crypto-asset service providers.
  2. Plan how to revoke before you need to. Pausing withdrawals did not cancel authorisations that already existed on-chain, and the MPC set-up meant there was no single key to revoke them quickly. Incident playbooks should cover how every delegated permission is revoked, by whom and how fast, and should be rehearsed.
  3. Recruitment is an attack channel. The decisive foothold came from a fake job interview that ended with code run on a work computer. Staff in sensitive roles need clear rules against running outside code on work devices, and devices with signing or deployment access should be isolated from everyday work. The enterprise identity and least privilege article and Knowlcom's zero-trust architecture work cover the controls.
  4. Developer tools and internal AI tools are part of the attack surface. The campaign began with a tampered installer found through a search engine, moved laterally through an internal AI tool and reached production with a deployment token kept on a laptop. Verified software sources, short-lived deployment credentials and the same access controls for internal AI tools as for any other privileged system all apply; see secure software supply chain and AI security.

Binance's investigation and the independent review are continuing. This article will be updated if Binance or the authorities publish further findings.

Sources

  1. Binance, 29 October 2026 Binance Security Incident: Initial Findings and Response Update (3 November 2026)
  2. The Record (Jonathan Greig), FBI blames N. Korea's TraderTraitor for Binance theft, urges crypto industry to block transactions (2 November 2026)
  3. CoinDesk, FBI confirms North Korea's role in $6 billion Binance hack, asks DeFi community to block BTC, ETH, SOL addresses (31 October 2026)
  4. BBC News (Osmond Chia), Binance users withdraw $3.6bn after largest-ever crypto hack (2 November 2026)