We analyzed this claim: is it true that

Binance sent 200 million USDT into its compromised wallet after alarms sounded, letting attackers drain the funds 72 seconds later?

Why Binance Sent $200M to a Hijacked WalletAI generatedConfirmed

Public transaction records show the transfer happened, but the stolen funds landed at an address already frozen by Tether, leaving the tokens immobilized.

Crypto
  • ClaraAuthorComing December 1
  • RafaVisual artistComing December 1
  • JolinaMarketingComing December 1

Why Binance Sent $200M to a Hijacked Wallet

Routine funding kept flowing into a compromised account during the theft.

Published
Quantum Otter — crypto markets and AI trading bots

In a nutshell

During a 6.34 billion dollar cyberattack on Binance, the exchange sent 200 million dollars into one of its own hijacked accounts more than an hour after alarms sounded. Attackers drained the money 72 seconds later, but an earlier freeze by stablecoin issuer Tether locked the funds in place. While customer reserves have been verified, Binance has not explained whether the flawed transfer was caused by automated treasury software or human error.

Highlights

  • Attackers stole about 6.34 billion dollars from Binance across ten blockchains on October 29, 2026.
  • Binance sent 200 million USDT into its compromised wallet more than an hour after the initial intrusion.
  • The attacker drained approximately 200.4 million USDT from the account just 72 seconds after it arrived.
  • Tether had blacklisted the attacker's receiving wallet 41 minutes prior, freezing the stolen USDT on arrival.
  • Binance cleared the attackers' unauthorized control over the wallet at 00:10 UTC on October 30.

Incident Recovery Breakdown

CategoryValue in Billions
Total Affected Assets6.34
Frozen or Intercepted Assets2.85
  • Comparison of the total assets affected in the breach against the amount frozen or intercepted.
  • It shows that emergency freezes locked down a substantial share of the stolen funds.

From the Editor’s Diary

Halting customer withdrawals does not secure an exchange if automated internal treasury systems continue feeding funds into compromised accounts.

Who's involved

  • Binance

    Global cryptocurrency exchange whose transaction-signing systems were breached

    goal → Stop unauthorized outflows, protect user deposits, and prove its internal controls are sound

  • TraderTraitor attackers

    North Korea-linked cyber syndicate named by the FBI for the theft

    goal → Seize exchange assets, move them before halts occur, and launder usable balances

  • Tether

    Company that issues USDT, a digital coin pegged to the US dollar

    goal → Freeze stolen USDT tokens to prevent illicit circulation across the market

  • Circle

    Company that issues the USDC dollar-pegged coin

    goal → Freeze illicit USDC balances linked to the exploit to halt their movement

  • Independent blockchain investigators

    Private research firms that mapped the public transaction records

    goal → Trace stolen fund flows and uncover gaps left open by exchange incident reports

  • Federal Bureau of Investigation

    US federal law enforcement agency investigating the breach

    goal → Identify the perpetrators, disrupt money laundering, and help firms block hacker addresses

In short

This case matters because it reveals how automated financial systems can keep feeding money into a broken account even after alarms go off. When attackers took over an internal account at Binance, another company wallet sent 200 million dollars straight into it. The intruders took the money over a minute later, showing that emergency halts failed to stop internal transfers.

Regulatory investigators will likely demand strict circuit breakers that automatically sever internal cash flows the moment an intrusion is detected.

That outcome is likely, because financial watchdogs and independent security auditors already treat internal containment failures as severe operational flaws.

How it unfolded

01

Attackers Reach Binance's Wallet Engineering Systems

2026-10-20 – 2026-10-20

The intrusion began well before the public saw any missing funds. Binance later disclosed that intruders used an infected employee computer and an internal AI tool on October 20 to compromise more staff accounts and steal a software deployment credential. The public only learned of the breach on October 29 when independent blockchain monitors noticed unusual outflows.

1 source
02

A Normal Funding Pattern Meets a Compromised Signing Path

2026-10-20 – 2026-10-28

Before the theft, the account called Binance 14 regularly received round-number payments from another company address. It received 200 million USDT on October 25 and two matching amounts on October 26. These regular payments looked like ordinary treasury management, revealing how signing systems can be exposed while everyday funding routines continue unbothered.

3 sources
03

One Signature Gives the Attacker a Standing Claim

2026-10-29 – 2026-10-29

On the afternoon of October 29, the attackers struck. Using stolen access codes, they reached Binance's signing system and set up a rule on Ethereum that handed control of Binance 14 over to malicious computer instructions. They did not need to steal the account's master private key.

At 20:24 UTC, the intruders used that rule to empty 167,464 Ether and 1.615 billion USDT from the account. An internal alarm alerted Binance to unusually large transfers, but company staff had not yet removed the intruders' standing permission.

5 sources
04

Public Warnings, a Partial Shutdown and a $200 Million Refill

2026-10-29 – 2026-10-29

By 20:32 UTC, outside analysts noticed the theft. Normal customer withdrawals paused, yet the unauthorized rule on Binance 14 remained active. Tether froze the attacker's main collection address at 21:01 UTC, but Binance 14 itself was not blacklisted.

Then came the unexpected payment. At 21:42 UTC, another Binance wallet sent 200 million USDT into Binance 14. Just 72 seconds later, the intruders swept the fresh money. Because Tether had already blocked the destination address, the newly stolen dollar tokens were frozen on arrival.

6 sources
05

Freezing the Loot Was Faster Than Revoking Its Authority

2026-10-29 – 2026-10-31

Freezing the attacker's account proved faster than fixing the compromised exchange wallet. Tether blacklisted Binance 14 at 22:06 UTC. Binance needed nearly four hours to craft a special transaction that finally erased the intruders' control over the account shortly after midnight.

Binance committed to covering user losses, and the FBI named North Korea's state-sponsored TraderTraitor group as the culprit, as investigators targeted the stolen loot. Yet the mystery remained why Binance's own systems sent funds into an account while alarms were active.

6 sources
06

The Money Is Replaced, but the Decision Trail Is Missing

2026-11-01 – 2026-11-04

Binance reopened customer withdrawals on November 1 and released cryptographic proof that user balances remained fully backed by exchange reserves. Its detailed report confirmed an internal alarm had fired during the breach, but omitted any mention of the late 200 million dollar payment.

Outside cybersecurity specialists noted that exchanges need hard physical boundaries between staff equipment and money-moving tools. While Binance replaced customer funds, questions linger over whether automated routines or human operators approved the payment.

5 sources

Where things stand

Public blockchain records confirm that Binance transferred 200 million USDT into a compromised account that attackers emptied 72 seconds later. Because Tether had already blacklisted the thieves' address, the stablecoins could not be spent. Whether the transfer was triggered automatically by routine replenishment software or approved by staff remains unconfirmed.

The remaining question is institutional: Binance has not yet published the internal logs, timestamps, and authorization records that explain why funding continued into an active security incident.

Sources

  • Blockaidattack-detection-and-signing-controls · 2026-10-29
  • drkearly-technical-reconstruction · 2026-10-30
  • Site Qwalityexact-wallet-timeline-and-monitoring · 2026-10-30
  • Halbornblacklist-timing-and-custody-controls · 2026-10-30
  • Rangeattack-chronology-and-original-public-warning · 2026-10-30
  • Binanceofficial-incident-chronology-and-control-review · 2026-11-03
  • Metrikaindependent-operational-risk-analysis · 2026-11-03
  • TRM Labssubsequent-laundering-update · 2026-11-03