Crypto
The Next Attack: Binance’s $6.3B Theft Demands International Cooperation

An Abu Dhabi court order supports recovery efforts. Binance’s account of the breach raises a harder question: why could compromised employee systems reach so much money?
[For more news, click here]
Binance said on November 18 that it had obtained an Abu Dhabi Global Market court order to support recovery after the October 29 attack. The step brings UAE courts into an international effort to trace, freeze and reclaim stolen assets.
The exchange says it has absorbed the financial impact. Recovering the stolen funds requires further legal and operational work. Explaining why the order matters, Binance said:
“In some cases, issuers, exchanges or other partners request a formal court order before frozen assets will be released, transferred or returned.”
That cooperation is necessary. The harder question is whether cooperation before the breach, combined with stronger internal separation, could have prevented or contained the loss.
How did the loss reach $6.3 billion?
Binance’s November 3 preliminary report put affected assets at approximately $6.34 billion. Around $2.85 billion had been frozen or intercepted. Those are different measures: a freeze can obstruct an attacker without returning money to its owner. Our October 30 report covered earlier freeze estimates. Neither those estimates nor Binance’s replacement of customer assets establish how much stolen money has actually returned.
The total spans several wallets and blockchains. Binance describes unauthorized transfers of XRP, Bitcoin, Solana, Optimism and Ethereum-related assets. The final unauthorized transfer was confirmed nearly four hours after the first XRP movements.
According to the report, attackers moved through engineers’ computers and an internal AI tool. Stolen deployment credentials then helped them reach a wallet-signing service, which authorizes transactions. Several blockchains were affected, but the report traces the attack through Binance’s systems. Cross-network losses do not establish a breach of each blockchain.
The FBI attributes the theft to North Korean activity called TraderTraitor. Our November 4 coverage explained how fake interviews and malicious developer software helped establish that access.
Suspending withdrawals did not stop everything. Attackers had also created permissions on Ethereum that operated independently of Binance’s normal withdrawal systems. Revoking those permissions required additional work.
This explains how losses could accumulate across networks. It leaves unanswered why the available permissions and transaction controls allowed exposure on that scale. The public report does not provide a complete asset-by-asset dollar reconciliation.
The warning was already there in May
Tech Revolt identified the underlying threat in May, five months before the Binance breach. Drawing on CrowdStrike research, we described organized North Korean operations using recruitment lures, synthetic identities and compromised software to target financial businesses.
That reporting recognized the danger early: apparently routine professional interactions could become entry points into financial infrastructure. Binance’s account now describes a fake recruitment process that persuaded an engineer to download a malicious coding assignment.
The methods were documented before this loss occurred. Binance also says it prevented 57 suspected North Korea-linked threats during 2026, evidence of a persistent campaign rather than an isolated attempt.
Cooperation before the emergency
In its July 2026 assessment, the Financial Action Task Force warned that criminals exploit uneven regulation and enforcement across borders. Its findings strengthen the case for cooperation before funds disappear.
For prevention, that means turning shared threat intelligence into working controls. Recruiters, exchanges and security teams could share verified malicious identities and software indicators earlier. Joint exercises could test whether partners can recognize suspicious transfers and coordinate restrictions quickly.
Binance’s account also makes internal separation central. It describes several compromised employees and systems, without establishing that one person held unrestricted access. The concern is how their combined permissions reached transaction authority.
The FBI’s earlier sector guidance recommended approvals from separate, unconnected networks before moving company assets. Applied effectively, independent approvals and narrowly limited credentials could reduce what one compromised environment can authorize. The preliminary findings cannot establish exactly which controls would have stopped this attack.
Transaction limits could also cap exposure while suspicious activity is investigated. Emergency exercises need to test whether stopping withdrawals also stops existing blockchain permissions. Otherwise, an internal shutdown can leave an attacker’s authority intact.
Sovereignty includes the ability to contain a breach
For the UAE, whose regulatory relationship with Binance predates the theft, recovery is one test of financial infrastructure. Containment is another.
Sovereign cybersecurity needs control over credentials, signing systems and emergency decisions. Domestic hosting alone cannot provide that control. Sensitive functions can be isolated while carefully governed connections preserve essential services and international threat sharing.
An approval system separated from everyday employee devices could help keep a recruitment scam from reaching custody operations. Its effectiveness would depend on controlling the access routes between them.
Our Mercado Bitcoin coverage raised related custody concerns after another exchange incident. The continuing threat warrants preparation for further attempts. Resilience means containing a compromised system, keeping essential operations available and cooperating internationally before recovery becomes necessary.





