Binance says a security incident with an estimated total impact of about $6.3 billion led it to pause withdrawals, according to the latest update from its verified Binance News account. The company first pointed to a compromised DevOps engineer’s laptop. On 30 October at 08:47 UTC it said its investigation had found additional points of breach. It says deposits are operating normally and that it will cover all losses through its SAFU fund and company resources.
Last checked against sources: October 31, 2026. Our own on-chain balances were queried on 30 October between 06:37 and 06:59 UTC. Figures and service status are changing as the investigation continues.
Update 31 October: In a recovery update on X at 19:58 UTC on 30 October, Binance said its hot wallets were compromised around 20:05 UTC on 29 October. It said withdrawals should start resuming in phases within about 34 hours, subject to security checks. It expects to share further technical findings within about 48 hours. On 31 October, its support account said crypto withdrawals remained paused, while P2P and fiat options stayed available where supported.
Update 1 November: In its Recovery Update 4, Binance said it had covered approximately 95% of the impacted amount, up from 90% in its prior update. It listed ten fully backed assets:
- BTC
- ETH
- USDT
- BNB
- SOL
- USDC
- XRP
- USD1
- RLUSD
- ZEC
It said the outstanding 5% are tokens outside that list, which have lower liquidity and take longer to source at the required scale.
The FBI’s 31 October advisory said the group is expected to further launder the stolen assets, already converted mainly into Ethereum, through decentralized finance platforms and instant swap services. It also asked those platforms, along with THORNode and RPC node operators and blockchain analytics firms, to block transactions tied to the group’s addresses.
What Did Binance Say?
Binance first posted on X on 29 October that it was investigating reports of a potential security issue, according to IBTimes UK. Early reports described a pause of both deposits and withdrawals. The latest Binance News update says deposits are unaffected and only withdrawals are paused.
According to that update, initial investigation suggested the attacker used a compromised DevOps engineer’s laptop. That access may have allowed entry to a service container and the submission of unauthorized withdrawal transactions. Binance says it found no evidence that wallet private keys were leaked. IBTimes UK reports that Binance revoked the affected address authorization.
On 30 October at 08:47 UTC, Binance said on X that its later investigation uncovered additional points of breach. It called the incident a complex attack and said it is working with law enforcement. It did not say what the other points of breach were.
Binance describes the cause as involving multiple factors. These are the company’s preliminary findings, not a final root-cause analysis.
How Did the Theft Work On-Chain?
Brandefense analysts traced the Ethereum side of the theft using public blockchain data. The attacker’s operator wallet was funded with three small withdrawals from the Tornado Cash 0.1 ETH pool. These arrived on 28 October at 07:39 and 08:53 UTC, and on 29 October at 08:23 UTC.
At 20:20:59 UTC on 29 October, that wallet sent one transaction carrying 50 EIP-7702 authorizations for a Binance hot wallet. Each was valid only for one specific transaction count. Only one of the 50 matched, which suggests the attacker could obtain signatures but could not predict the wallet’s live state.
Security firm Blockaid described this pattern on 29 October. Its analysis says Binance’s own signing infrastructure, under the attacker’s control, signed the authorization. That fits Binance’s statement that it found no evidence of a wallet private key leak.
Four minutes later, at 20:24:23 UTC, a single sweep moved about 167,464 ETH and 1.62 billion USDT out of the hot wallet. Dozens of other tokens went with it. Earlier, at 20:20:06 UTC, 18,270.2 BTC moved from a wallet labelled as Binance’s into one address, and most of it was split in the same block into 1,000 BTC outputs.
Binance co-CEO Richard Teng described the same mechanism in a video statement on 30 October at 14:32 UTC and a transcript he posted. He said the attacker used EIP-7702 to obtain on-chain execution approval over a hot wallet, and that this delegation did not pass through Binance’s normal approval controls. He also said the attack was not carried out by one person, and that the attacker used a self-destruct mechanism that destroyed tooling and traces.
Where Did the Money Go?
The attacker raced to turn freezable stablecoins into ETH. Within about 40 minutes, roughly 435 million USDT was swapped into about 160,446 ETH through UniswapX and Uniswap. That is an average near $2,711 per ETH, well above the market price of about $2,245 at our query time.
Paying that premium shows speed mattered more than price. A further 60 million USDT was deposited on Aave as collateral to borrow 19,763 WETH. Binance co-founder Yi He said this Aave position is not counted in the frozen total. Altcoins such as ENA, PEPE, UNI and LINK were sold into ETH over the next hours, with activity peaking around 02:00 UTC on 30 October.
The bitcoin is harder to stop. CoinDesk traced the 18,270 BTC to 19 wallets, 17 of them holding exactly 1,000 BTC. Elliptic’s 31 October update says none of it had yet been sent to a service. Elliptic reports that nothing stolen on Bitcoin, the XRP Ledger, Solana or NEAR has been frozen, because those assets have no issuer that can block them.
The attacker also made at least one costly mistake. Lookonchain reported that about $3.32 million in altcoins was sent to a token contract address, where it cannot be recovered.
Laundering has started on Tron. Elliptic says the attacker’s 638 million TRX was split across five new addresses on 30 October. Between $38 million and $67 million of TRX has since left them, mostly into ETH through swap services and cross-chain bridges. Elliptic also says Optimism’s governance appears to have moved 44 million OP, around $5 million, out of the attacker’s address.
The table below lists the operator wallet and the wallets holding the main remaining Ethereum funds. Together, attacker wallets held about 465,020 ETH plus 29,934 WBETH, worth roughly $1.12 billion at query time. We saw no deposits from these wallets to exchanges or Tornado Cash.
| Role | Address | Balance on 30 Oct, 06:37–06:59 UTC |
|---|---|---|
| Operator wallet, funded via Tornado Cash | 0x7C8601d4645b93cea45F71e118A729332e6B5CA0 |
About 1.2 ETH |
| Main collector, stablecoins frozen | 0x5227f603C1eE34CE3C06eFe6477003BDfCCB2f8c |
1.18B USDT and 823M USDC frozen |
| ETH holder | 0x8532FA14ACAf483729C449b8458aedDb900543D4 |
197,460 ETH |
| ETH holder | 0xc887aF690E0301CD4edBbCe8F8d31b4EC65B286A |
137,602 ETH |
| ETH holder | 0x897C80d1a9729E94460e2Bd93178bD5215158DF3 |
78,415 ETH |
| ETH consolidation wallet | 0x79e70d139fC05AA75F75611fDF2680E9952B544A |
34,280 ETH |
| ETH holder | 0x03b0eE5d82990cFF1bDa48651AC3e436d1a020ea |
17,260 ETH |
| WBETH holder | 0x7f9DC988B46336aD536828fAD50fa8fA1E5415E3 |
29,934 WBETH |
Addresses are listed for defenders and compliance teams to screen. The main collector is also being targeted by address poisoning, with look-alike addresses and fake tokens. Always compare the full address, not the first and last characters.
How Much Has Been Frozen?
We checked the stablecoin blacklists directly on Ethereum. Tether has blacklisted three attacker wallets holding 1.38 billion USDT. Circle has blacklisted 823 million USDC. That is about $2.2 billion frozen on Ethereum alone.
TRM Labs reports further freezes on Tron, Avalanche, Polygon and Arbitrum, plus RLUSD and USD1 stablecoins. TRM puts the total near $2.7 billion. Elliptic had verified $2.85 billion frozen or seized by about 04:30 UTC on 31 October, while Chainalysis says about $2.8 billion and Binance about $3 billion. These totals use different scopes and times.
Tether froze the main collector at about 21:01 UTC, around 40 minutes after the theft. Two later sweeps from the same hot wallet, worth about $204 million in USDT, landed in that already-frozen wallet. A freeze restricts movement; it does not prove recovery.
Some early figures do not match the chain. Glassnode data cited by Investing.com put the BTC outflow at 17,985 BTC and USDC at $767 million. On-chain records show 18,270.2 BTC and 823 million USDC. Analytics firms’ theft totals also differ from Binance’s $6.3 billion: TRM says $6.36 billion, Chainalysis $6.4 billion and Elliptic $6.43 billion.
Who Is Suspected?
Binance has not named an attacker. CoinDesk reports that blockchain investigators point to North Korea. ZachXBT said the attacker was “likely Lazarus.” TRM Labs assessed with “high confidence” that TraderTraitor, a Lazarus Group subgroup, was likely responsible.
Chainalysis CEO Jonathan Levin said the theft was likely carried out by TraderTraitor, citing links to a previous hack. ZachXBT later said funds from this theft and a $388 million Bitget exploit were mixed at one address after crossing THORChain. Our trace could not yet confirm the Binance side of that link.
Elliptic has since confirmed that some of the Tron funds were laundered alongside proceeds of the September 2026 Bitget exploit. It says laundering networks can serve multiple clients, so the link does not prove one hacker carried out both thefts. The FBI said in a 31 October alert that North Korea was responsible for the theft, naming the activity TraderTraitor. It said FBI, Secret Service and IRS Criminal Investigation agents observed the group converting stolen assets mainly into Ethereum.
Blockaid’s CEO said the tactics are consistent with DPRK operations. CoinDesk’s report, published before the FBI’s 31 October statement, quoted a source saying the attack had not yet been definitively attributed. The FBI statement is now the first official government attribution of this incident.
Our TraderTraitor profile covers the group’s known tactics. The FBI attributed the February 2025 Bybit theft to the same group. TRM notes shared traits with that case, such as small Tornado Cash funding and pre-staged signatures. It also notes a shift from bridges toward swaps and lending.
Could AI Have Played a Role?
No investigator has said the attacker used artificial intelligence. Binance has not explained how the engineer’s laptop was compromised or what the additional points of breach were. The Register notes that phishing or a supply chain attack cannot be ruled out. Everything in this section is a Brandefense analyst assessment, not an established fact.
Our hypothesis is that AI-assisted reconnaissance may have helped the attackers find their way in. That could include automated scanning of public profiles, code repositories and job sites to identify the right DevOps engineer. It could also include generating convincing recruiter or test-task lures for that person.
The reasoning rests on documented behavior. CISA has described TraderTraitor spearphishing crypto employees with fake high-paying job offers. Google reported in November 2025 that UNC4899, a cluster linked to TraderTraitor, used Gemini to develop code, research exploits and improve its tooling.
There is no forensic evidence of AI use here. The 50-authorization attempt points to careful human planning, not automated scanning. Microsoft says it has not yet observed large-scale use of agentic AI by threat actors. We will revise this assessment when Binance publishes its post-mortem.
What Do Dark Web and Social Channels Show?
Brandefense Blackhole monitoring recorded 1,695 Telegram, forum and Discord messages mentioning Binance between 28 and 30 October. In a sample of 1,000, about half were about the hack. Hack-related volume peaked at 21:00 UTC on 29 October, mostly in Cyrillic-script, largely Russian-language, Telegram channels. Our analysis of how the Binance hack spread on Telegram and X follows the first 12 hours channel by channel.
Scammers moved fast. About an hour after the theft, sellers on an English-language Telegram channel offered “stolen funds” from the hack at a sixth to a tenth of face value. This matches a common advance-fee scam and is not verified.
On 30 October, a Chinese-language crypto news channel warned readers that unsolicited “Binance compensation” messages are fraud. A cybercrime forum post the same morning advertised a wallet “recovery” tool, a familiar malware lure. These claims are not verified.
On X, opportunists launched hack-themed memecoins. One Solana token named after TraderTraitor appeared on 30 October, about two hours after TRM Labs published its attribution. Its only social link was a post that pointed to our own TraderTraitor profile. Brandefense has no connection to any token.
What Does the Pause Mean for Users?
Binance says it is rebuilding the security of its withdrawal service and related addresses. On 30 October at 14:32 UTC, Teng said Binance hopes users can withdraw before its Sunday deadline, which he put within 40 hours. Binance’s later 19:58 UTC update set a phased restart within about 34 hours, subject to security checks. These are company estimates, so check the official app or type the exchange’s address directly before acting.
Binance says it will publish a full post-mortem once remediation is complete. Teng said a full Proof of Reserves report will follow by Monday, and the later update said initial snapshot results would be ready by 2 November. He also described a company-wide security review of endpoints, cloud, key management and signing. Binance asks users to rely only on official Binance channels for updates.
On 30 October at 10:55 UTC, Binance said on X that it had reserved over $6.34 billion of company funds to cover the incident. It said $5 billion of that is already held in the exact tokens that were taken. On 31 October, Teng said on X that the exchange had replenished 90% of the stolen assets and was committed to covering the rest.
It is buying the rest through market and OTC channels. Co-founder Yi He said the exchange is buying the stolen altcoins in fully matching amounts and will update users when the purchases are complete.
CoinDesk found that the drained “Binance 14” hot wallet appears in Binance’s 1 October Proof of Reserves. It puts the ETH taken at roughly 204,500, about 5.6% of the ETH reserves in that report, which would leave ETH backing near 94% until the assets are replaced.
That figure is higher than the 167,464 ETH we saw leave Binance 14 in the main sweep; Elliptic counts another 28,006 ETH from a second hot wallet. Binance says user funds are safe and expects results of a new reserve snapshot by 2 November.
The US Federal Trade Commission warns against unsolicited crypto recovery offers that request fees or account details. Its crypto scam guidance also warns against unexpected links. Do not buy “stolen funds”, download recovery tools or follow refund links.
Do not share passwords, recovery phrases or one-time codes. Our guide to phishing explains how deceptive messages seek access to accounts.
What Should Security Teams Take From This?
The first reported entry point was an engineer’s endpoint, not a wallet key, and Binance now says the attack had more points of breach. That pattern matters beyond crypto. Access held by DevOps and platform staff can reach systems that move money or data.
Teams should review how build and operations laptops are protected and how service containers authorize high-value actions. Limits, extra approval and anomaly alerts on outbound transfers can reduce the damage when one account is compromised.
Exchanges and payment firms should screen the addresses above and watch for look-alike addresses. Our overview of blockchain investigations explains why tracing needs context. A separate 2022 BNB Chain bridge incident involved a different system.
Organizations that rely on exchange access should use their incident response and third-party risk processes to map this dependency. Keep the provider’s statements separate from independently verified findings until the post-mortem is published. For a separate, unverified Telegram listing that claims to sell Binance user data, see our Binance data sale claim explainer.
Frequently Asked Questions
When will Binance withdrawals resume?
In its 30 October update at 19:58 UTC, Binance said it targeted a phased restart of withdrawals within about 34 hours, subject to security checks. On 31 October its support account said crypto withdrawals remained paused, with P2P and fiat options available where supported. On 31 October, Teng said on X that the exchange remained on track to reopen withdrawals on Sunday, 1 November. Check the current status through an official Binance channel.
Are Binance deposits affected?
The latest Binance News update says deposits are unaffected and operating normally. Earlier reports described a pause of both deposits and withdrawals.
How much was lost in the Binance incident?
Binance estimates the total impact at about $6.3 billion and says about $3 billion has been frozen. On 30 October it said it had reserved over $6.34 billion of company funds to cover the incident. It has not published a final loss figure.
Who is behind the Binance hack?
The FBI said on 31 October that North Korea's TraderTraitor group was responsible for the theft; TRM Labs and Chainalysis had already reached the same assessment. Binance has not named an attacker publicly.
Where are the stolen funds now?
At our 30 October query, attacker wallets on Ethereum held about 465,020 ETH plus WBETH, while about $2.2 billion in USDT and USDC was frozen. The BTC had been split across 19 addresses; Elliptic said on 31 October that none had yet been sent to a service.
Was AI used in the Binance hack?
No investigator has reported AI use. Brandefense considers AI-assisted reconnaissance a possibility based on documented North Korean tactics, but there is no evidence for it in this case.
Sources
- Binance News security investigation update
- TRM Labs: North Korea steals $6.36 billion from Binance
- EIP-7702 authorization transaction (Blockscout)
- Elliptic: Binance hack analysis and updates
- Chainalysis: The $6.4 Billion Binance Hack: Tracing the North Korea Link
- FBI alert: North Korea Responsible for $6 Billion+ Binance Attack
