Cases › security breach › LR-2026-0842
Binance US$6.3bn hot-wallet theft following recruitment-lure intrusion and misuse of an internal AI tool
Also listed as: AI cyberattacks
Confirmed Why: 9 independent outlets · 9 independent reports
Evidence level history
- 2026-11-05: Preliminary (1 report: Insurance Business · subject to change)
- 2026-11-05: Confirmed (2 independent outlets)
Developing: a major or severe case captured in the last 72 hours. Later changes are logged on the corrections page.
Status: no action reported
No source states: developer and model, could do, deployer.
Severity severe: under the dollar band: the stated loss estimate of about US$6.3bn is over 10M USD. The figure is Binance’s own estimate.
A Binance software engineer was approached about a new job in September, and code he downloaded for a recruiter’s take-home test contained malicious code. A tampered AI coding assistant installer had earlier disclosed who worked on wallet systems. On 20 October, attackers used his laptop and an internal Binance AI tool to take over the computers of two wallet-team engineers. On 29 October they used stolen credentials to launch a container and run a script that moved funds out of hot wallets. Binance estimates the loss at US$6.3bn, and the FBI attributed the attack to TraderTraitor, which Pyongyang denies. About US$2.85bn has been frozen or intercepted. Withdrawals were suspended for almost two days and reopened on 1 November. Binance says it has replaced about 95% of affected funds.
What happened
No source tells the story step by step yet.
What was done
No source states an action or fix.
Risks
Primary98 incidents
Rising: 25 vs 4.0 a week
Sorted by rule from the case's fields; not yet read from the sources.
Controls
Not yet read for controls. Controls that mitigate the primary risk:
ModelSafety training and refusal · Cyber and weapons safeguards · Abuse monitoring and account enforcement · Staged or restricted release · Dangerous-capability testing before release · Outside red-teaming · Content safety classifiers · Safeguards kept on in testing · Reasoning monitoring
Infrastructure / targetKnown flaws patched · Multi-factor sign-in and password policy · Network segmentation · Intrusion and endpoint detection · Backups and recovery · Phishing and fraud filters
Similar incidents
Evidence
- Direct loss $6,300,000,000
- Cause hostile input carried instructions
No source states: a step-by-step account, when it was found, how many records were exposed, a count of the other parties affected, any court case, what set it off, what was done.
Show every field, with its source and grade
What happened
Impact
Context
Notes on gaps
The document is a press account of a company incident report. The first break-in has only a month (June). The year for the 3 November report is likewise taken from metadata. Loss is Binance's own estimate. Insurance status is reported second-hand via Bloomberg Law: no cyber cover, D&O cover held, and Binance has not commented, so coverage posture is unknown and not recorded. Statements about specie, crime and war exclusions are generic market commentary, not Binance's policy wording. The 95% replacement figure is a company claim. Extractor proposed values without quotes; dropped: .
LR-2026-0842 · version 20 · published 2026-11-05 after automatic checks; not yet checked field by field by a person · changes to this case · JSON