Skip to content

News · Security

Binance puts the hot-wallet loss near $6.3 billion. Covering it is a company promise.

Updated 16 Nov: Binance says coverage is complete. A 12 Nov snapshot covers 198 tokens. That is not the stolen coins back.

Guide: What is Bitcoin?, How does Ethereum work?, What is BNB?, What is Tether (USDT)?, What is USDC?

ECGBy EasyCryptoGuides · Editor · Published · Updated · 21 min read

Padlock resting on a laptop keyboard, suggesting device security
Photo by FLY:D on Unsplash
In this article

On 30 October 2026 Binance published a security update after halting withdrawals late the night before. The firm’s own estimate of the impact is about $6.3 billion. It says about $3 billion of that has been frozen on-chain with help from other companies. The first version of the note said an early look “may involve” a compromised laptop belonging to a DevOps engineer, which let an attacker reach a service container and submit withdrawal transactions the exchange did not mean to send. Binance says it has found no evidence that a wallet private key leaked. The company said a fuller technical account would follow. This page will not invent one.

Updated later the same day, from posts and a video by co-CEO Richard Teng on X. He said the laptop was not the whole breach. “This was not carried out by one person.” The later investigation, he said, found additional points of breach. It was “a more complex attack process”, not a single one-click action, and the investigation “has not attributed responsibility to any individual.” He also said the attackers used a self-destruct mechanism that destroyed tools and traces as they went, which is why the tracing is slower. In the video he said the attacker used an Ethereum feature, EIP-7702, to obtain execution approval over a hot wallet, and that this delegation did not pass through Binance’s normal approval controls. That is why withdrawals were switched off. The support note put the first unauthorised movements at about 20:05 UTC on 29 October, from hot wallets, and said the authorisations involved had been revoked. It also said the full sequence was still being established, and that a technical account would be published only after it had been checked and only if publishing it would not harm the investigation. On 3 November that account arrived as initial findings. This page will not describe how that approval is granted, and it will not repeat the file changes or the delegation steps the report includes.

The sentence customers are being shown is “user funds are safe”, plus a promise to cover the loss from the Secure Asset Fund for Users and from the company’s own money. Later on 30 October Binance put a figure on the company side of that promise: more than $6.34 billion set aside, of which about $5 billion was already held in the same tokens that were taken. The shortfall, co-CEO Yi He said, is being bought through private deals and on exchanges. That $6.34 billion is not the $3 billion already frozen. The frozen pile is other people’s stop-buttons. The set-aside is Binance’s own money, and it does not include the frozen tokens. Read both as a balance-sheet plan. The number on a Binance screen was never the coin. What is a crypto exchange balance? When the hot wallets that make withdrawals fast are swept, the screen can still show yesterday’s balance. What changed is whether the coins behind that screen are still in the company’s spendable wallets.

Updated on 1 November, from Teng and from the company’s Saturday notice. Teng said Binance had replenished approximately 95% of the impacted assets. That is about $6 billion of the $6.3 billion estimate, up from about 90% on Saturday and about 80% in the notice before that. The set-aside figure did not move. It is still more than $6.34 billion of company funds. Replenished means the company says it has bought or allocated replacement assets. It does not mean the stolen coins were recovered. Saturday’s notice said the money was coming from three places: a partial draw on SAFU, a portion of the futures insurance fund, and the corporate treasury. Yi He said about half of SAFU would be used, and the company said it would put that fund back to about $1 billion. On the futures fund, Binance said it moved only the balance above the size its own risk rules require, and that what remains still meets those rules. That fund exists to absorb bankrupt futures positions. It is not the spot ledger, and it is not deposit insurance.

The ten assets Binance listed as fully backed were bitcoin, ether, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD, and ZEC. The rest of the gap, it said, is less liquid tokens outside that list, which can take longer to buy. A line that says 100% on a reserve page is a claim that the company holds enough of that asset for the balances it shows. It is still a claim on Binance.

What happened

Hot wallets are the float an exchange keeps online so a withdrawal does not wait on a cold-storage ceremony. Teng said that is the piece that was hit. User assets, he said, sit under the company’s custody design, and the vast majority stay in cold wallets until someone actually withdraws. “We never use any customer funds so they are not impacted” is his answer to people asking how a personal balance can be untouched. He means the company does not spend the customer pile to run itself. It does not mean the hot-wallet coins are still there. He did not publish a list of affected accounts.

Binance says it revoked the address authorisation involved and called in law enforcement and tracing firms. The written update, edited later on 30 October, says deposits continue as normal. The first draft of that page had suspended deposits as well as withdrawals. The edit is the company’s correction. Withdrawals were the service that stayed off while the firm rebuilt and tested. Teng’s Friday video put that restart on track within about 40 hours, before Sunday, and said it would not be switched on until it passed testing. On Sunday 1 November the pause ended in phases. Bitcoin was the first network back, shortly after 06:00 UTC, inside a window the company had set from 06:00 to 09:00 UTC. Ether, BNB, and some USDT and USDC followed. The first phase was described as 15 assets, including XRP and dogecoin, with other networks waiting on further checks. A network that is not open on the withdrawal page is still paused. Binance also said it had added newly generated addresses to its proof-of-reserves list and that withdrawals would be sent from those addresses. That is the company paying out from a new wallet. It is not an instruction to send coins to an address a message just gave you. The status inside the app is the one that can move money.

The proof of reserves moved past the Monday promise, and then past the Tuesday one. Teng had said a full report would come by Monday, 2 November, with an earlier snapshot if the firm could produce one. A snapshot taken at 00:00 UTC on 31 October went up first. Recovery Update 5, posted at 12:49 UTC on 2 November, said the full zero-knowledge proof for that snapshot was complete, inside an estimate that had pointed at Tuesday. It covers the same ten assets already listed as fully backed: bitcoin, ether, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD, and ZEC. Binance says a user checks an account by logging in and running a verifier it describes as open source, published on GitHub, and independently audited. The construction it describes is a Merkle tree, so a user can see that their own balance was included, and a zk-SNARK, so the total reserves can be shown as at least one-to-one without printing everyone else’s balance. This page has not run the verifier. The proof is one moment, 00:00 UTC on 31 October. It is not a statement about the hour you are reading this, and it is not insurance. A wider snapshot, covering more tokens, was planned for 4 November. Yi He said generating that next proof was expected to take about 40 to 50 hours after the snapshot. Recovery Update 7, below, is what happened to that plan.

Updated on 3 November, Recovery Update 6, posted at 02:30 UTC. A second wave of withdrawals was set to begin at 04:00 UTC, one network-and-asset pair at a time, after each pair passed the checks. The list covers nine networks. BNB Smart Chain is the longest, and Binance said withdrawals of its tokenized stocks, the bSTOCKS line, would open there too. Ethereum and Solana are the next longest. Shorter lists name pairs on the XRP Ledger, Sui, Arbitrum, Optimism, Tron, and Base. Later the same morning the company said a run of the Ethereum and Solana pairs had been restored. A pair that is not open on the withdrawal page is still paused. Deposits remained open. The 95 percent figure did not move in either update.

Updated on 4 November, from Binance’s initial findings, posted on 3 November. The company calls it an initial report. The investigation is still open, an independent review is still to come, and Binance says some technical details will stay confidential so they cannot be reused. The report’s own description of the campaign is this: it was not one breach and it was not a simple phishing click. In June a Wallet DevOps engineer downloaded a tampered Homebrew installer while looking for a popular AI coding tool. Binance says its security team caught that, replaced the device, and rotated the related credentials, and that the engineer’s role and the wallet team around him were already exposed. In September a software engineer was contacted on a legitimate job platform by someone posing as a project director. The engineer’s profile mentioned Binance. A first interview was a live video with someone presented as HR, who shared a social-media account of personal photos and videos. A second interview, in a chat app, was with someone presented as the chief executive of a company that does not exist. Near the end, the engineer was told to download an assignment onto the work computer. Binance says that file was malware, that it ran during setup, and that the endpoint tools did not detect it. The report describes how the malware changed a developer tool. This page will not.

On 20 October, Binance says, the attacker used that computer and an internal AI tool to gain control of the first engineer and a third wallet engineer, and found a token on the first engineer’s computer that could deploy software. The report does not name the AI tool and does not say what it was allowed to do. On 29 October, between 17:15 and 19:56 UTC, Binance says the attacker used that credential from the third engineer’s computer to reach the internal wallet signing service. Transactions could then be started outside the normal withdrawal process. The report says a container was deployed and a script was run. This page will not describe either. Binance also says that during 2026 its security team detected and stopped 57 suspected North Korea-linked attempts, including fake recruitment and tampered developer tools. A count of attempts stopped is not this theft, and it is not a method.

The findings then give the outflow the company is willing to itemise. Between 20:05 and 20:09 UTC, five hot wallets sent 233.46 million XRP. Hot wallets on Solana and Optimism sent about 970,500 SOL and about 44.2 million OP. A hot wallet sent 18,270 BTC. Binance says an internal alert on large transfers fired and the investigation started. The attacker then used the signing service to install the EIP-7702 delegation already named above, giving a contract the attacker controlled partial execution rights over a hot wallet. The delegation sat on the chain, so pausing withdrawals and shutting the hot-wallet service did not cancel it. The hot wallet uses multiparty computation, which splits signing so that no single private key can move the coins alone. Binance says that same design meant no single key could revoke the delegation quickly, and that the team had to build a procedure to clear it. The last unauthorised transfer in the report, 2,961.9 ETH, finalised at 23:56 UTC. Binance says it cleared the delegation at 00:10 UTC on 30 October. No private key is described as having leaked. The service that is allowed to ask for a signature was reached. This page will not describe how the delegation was installed or how it was cleared.

The same post changes three figures, and it does not add them to the earlier ones. The impacted amount is given as about $6.34 billion. That is the company’s later total for the same incident the first note put near $6.3 billion. Frozen or intercepted assets are given as about $2.85 billion, subject to reconciliation and to price moves. That is the later aggregate, not a sum to place on top of the earlier “about $3 billion”, and not a sum to place on top of the issuer freezes. Coverage is now stated as more than 100% of the funds required, set aside so that users do not bear the loss. As of 31 October, the post says, 98% of the impacted token assets had been replenished and could be checked on the proof-of-reserves page, with the less liquid remainder still being bought. Recovery updates through 3 November had put the replenished share at about 95% of the impacted amount, and Update 6 did not move that 95%. Both sentences are the company’s. They are not the same sentence. Replenished still means bought or allocated. It does not mean the stolen coins came back.

What Binance says it has already done, as of 3 November: rebuilt the affected wallet system in a new environment, rebuilt the internal AI tool and its access controls, replaced the affected devices, and decommissioned the credentials and tokens tied to the engineers involved. It says it scanned employee devices, widened automated checks for unusual behaviour, and tightened risk controls on the wallet service. It also says it is reviewing how the incident was handled, which signatures the policy covered, and the hot-wallet controls. What it says comes next is an independent cybersecurity review to test these findings, more spending on detection, endpoint protection, and the security of developer machines, and work toward a security research fund with AI companies, other firms, and security companies, aimed at AI security in blockchain settings. Some of the new controls, it says, will stay private. A rebuilt system is a company statement about a system. It is not a promise that a hot wallet cannot be signed for again.

Updated on 5 November, from Recovery Update 7, posted at 15:23 UTC on 4 November. Binance said it has now replenished approximately 98% of the impacted amount, and that it is still buying the remaining 2% through markets and private deals. It said those purchases will be slower because the tokens are less liquid. That 98% is the recovery-update figure moving to the same percentage the 3 November findings used for impacted token assets as of 31 October. The findings had dated their 98% to 31 October, while Updates 4 through 6 were still saying about 95%. Update 7 does not explain the gap. It does say 98% of the impacted amount, now. Replenished still means bought or allocated. It does not mean the stolen coins came back. The set-aside is still described as more than 100% of the funds required, from the company’s own resources.

The same update says a new proof-of-reserves snapshot was taken at 00:00 UTC on 4 November. It covers 44 tokens, up from the ten in the 31 October snapshot. Binance says the snapshot is on its proof-of-reserves site. It does not, in the update, name the 44. Generating the full zero-knowledge proof is expected to take about 50 to 60 hours, longer than the 40 to 50 hours Yi He had given for this wider snapshot. Once that proof exists, holders of a covered token are supposed to be able to check that their own balance was backed at least one-to-one at 00:00 UTC on 4 November. This page has not run that check. A snapshot of 44 tokens is not a snapshot of every token, and it is not insurance.

Updated on 7 November. Recovery Update 8, timestamped 03:04 UTC on 5 November, says withdrawals for another 69 network-and-asset pairs would start reopening at 04:00 UTC that day, on Ethereum, BNB Smart Chain, Base, Tron, Polygon, and Sui. Not all of them at once. Each pair opens after its own checks. Deposits stay open. Recovery Update 9, as republished for 03:06 UTC on 6 November, is a further batch, counted in those accounts as 58 pairs across nine networks. This page did not open that announcement. Those accounts do not move the 98 percent. At 09:08 UTC on 6 November Binance posted that the zero-knowledge proof for the latest snapshot is ready, and that users can verify covered balances are backed at a minimum of one-to-one. The same post says there is a time gap between the proof being finished and the moment a user can run the check, and that the length of the gap depends on the size of the asset list and is outside Binance’s control. This page has not run the check. Later the same day Binance said it was working to reopen withdrawals for HYPE, INJ, APT, PLASMA, NEAR, and LTC by the end of the following week, and for all tokens on networks it described as already restored. That is an aim. It is not a withdrawal page that is already open.

Updated on 10 November. This page did not open the posts. Coindaro quotes a Binance post at 08:52 UTC on 8 November that reopened withdrawals of HYPE and APT, ahead of that end-of-week aim. Exchange.news, Etherworld, and Atlas Pulse quote a post at 04:56 UTC on 9 November that reopened Binance Alpha withdrawals on BNB Smart Chain, Ethereum, Base, and Arbitrum, and that lists HYPE and APT as already enabled. INJ, PLASMA, NEAR, and LTC are not in that post. The only timetable for those four is still the 6 November aim for the end of this week. The 98 percent figure did not move. Counts from outside firms of bitcoin, ether, and stablecoins leaving wallets they label as Binance mix the theft with later customer withdrawals. They are not Binance’s figure, and this page will not use them as one.

Updated on 13 November. That end of the week has arrived. This page has not found a company post that reopens INJ, PLASMA, NEAR, or LTC. Sites that scrape the withdrawal page disagree with one another, and a scrape is not a Binance post. The 98 percent figure did not move. Binance Pool stopped is a product that was switched off. It is not this list.

Updated on 16 November. A recovery notice dated 14 November, quoted by several outlets and not opened on this page, says withdrawals were reopened this week on 87 networks. LTC, NEAR, and PLASMA are in the list those outlets print. HYPE and APT were already back, and they are named again. The notice aims to reopen whatever is left by the end of next week. INJ is not in that printed list. A status page that shows INJ as open is not the notice.

Updated later the same day. The about 98 percent was the figure on 4 November, while the less liquid tokens were still being bought. An announcement posted at 16:54 UTC on 12 November, as outlets quote it and this page did not open, says coverage of the affected assets is complete. The money committed is more than $6.34 billion. That is the same company commitment as the set-aside. It is not a second $6.34 billion, and it is not the stolen coins returned. Binance says the tokens were bought in the market and in private deals, from the same three places: part of SAFU, the slice of the futures insurance fund above the size the company’s own rules require, and the corporate treasury. The announcement still says SAFU will be refilled toward about $1 billion. That sentence is not a receipt that the fund is already there. A proof-of-reserves snapshot at 00:00 UTC on 12 November covers 198 tokens. The 4 November snapshot covered 44. The 31 October snapshot covered 10. Binance said the zero-knowledge proof for the new snapshot would take about 40 to 50 hours. A post at 10:55 UTC on 14 November, quoted and not opened here, says that proof has been generated and that a user can check at least 1:1 backing for the assets in the snapshot. This page has not run that check. The snapshot is one moment. It is not the whole balance sheet, and a green check is not a withdrawal. Tokens the company no longer lists are to go through its delisting process, and it says those holders will be covered.

On 12 November the US Justice Department said a court had authorised it to seize or restrain more than $1.2 billion of the crypto stolen from Binance. It said government and private-sector efforts together have frozen more than $2.7 billion of that theft. The $1.2 billion sits inside the $2.7 billion. It is not added to Binance’s about $2.85 billion frozen or intercepted, and it is not added to the $6.34 billion. A court authorisation is not a coin back in a customer account. The same release describes FaceStealer, a separate scheme it says took more than $400 million over about 18 months. That figure is not this theft.

A separate proposal on the Polygon forum, discussed on that network’s 5 November governance call, asks for a one-time hard fork so that native POL already stopped by block producers could be credited to recovery addresses. The proposal’s own count is about 70.49 million POL, of which about 46.63 million is tied to this incident and about 23.86 million to the Polymarket incident. Polymarket’s page is the other one. No vote result and no activation block had been published when this page was updated. A proposal is not those tokens returned, and it is not part of the $6.34 billion. The proposal’s own price print, near $6.5 million, is not a new loss figure. What is Polygon?. This page will not publish the addresses, and it will not describe the balance change.

Freezes are a different pile from the $6.3 billion. Tether’s chief executive said the company had frozen more than 1.567 billion USDT tied to the incident. Circle’s chief executive said more than $800 million of USDC had been frozen. Ripple said it was freezing RLUSD connected to the event, and Yi He later put that help near $200 million. Those are issuer switches on tokens the issuers can stop. Bitcoin and ether do not have that switch. Binance’s “about $3 billion frozen” is the company’s aggregate at the time of the note. Adding the issuer posts on top of it will double-count. A freeze is also not a return. A frozen token is stuck. It is not back in the hot wallet.

Binance.US said it is a separate company, that it does not share custody with Binance.com, and that its own service was not part of this incident. A similar name is not the same ledger. What is BNB? is the exchange token and the chain fee. BNB moving, or not moving, is not the customer-balance question.

Three earlier exchange thefts on this site are the same kind of event, and they are not this one. In May 2019 Binance lost about 7,000 bitcoin from a single hot wallet and said SAFU, a fund it sets aside from trading fees, would cover customers. That piece is Binance’s 7,000 BTC theft is why SAFU existed. In February 2025 Bybit lost on the order of $1.5 billion from a company wallet. That piece is The Bybit theft was a company wallet. The chain did what signatures do. In September 2026 Bitget lost about $387.5 million from hot wallets. That piece is Bitget lost about $387.5 million from hot wallets. That is an exchange ledger. Each time, the coins that moved belonged to the exchange’s online wallets, and the company promised to honour the balances on its own screen. Bitcoin and Ethereum did not stop, and they did not mint the missing coins back.

Why it matters

If your coins are on Binance, you are a creditor of Binance for that number, for as long as they stay there. “We will cover it” now has Recovery Update 7 beside it: about 98% of the impacted amount replenished. The 3 November findings had already said 98% of impacted token assets as of 31 October, while the recovery updates through 3 November were still at about 95%. Update 7 does not say why those clocks disagreed. The set-aside is more than 100% of what the company says is required to cover the loss, with SAFU and a slice of the futures insurance fund used along the way. SAFU is a pot the company funds. It is not a government deposit scheme, and it is not a smart contract that pays you when a wallet moves. A ticker marked 100% can still sit on a network whose withdrawals have not reopened. If your coins are in a wallet whose keys you hold, this incident did not spend them. Deposits stayed open. A deposit onto a network that cannot yet withdraw is a balance you cannot yet leave.

Some tracing firms had said the pattern resembles thefts previously linked to North Korea. On Saturday the FBI said North Korea was responsible, and named the group it calls TraderTraitor. Binance’s 3 November findings cite the FBI’s indication that North Korea is responsible. That is the company pointing at the FBI. It is not Binance naming a person, and a named suspect is not a returned coin. North Korea has denied involvement in attacks of this kind. The US Secret Service said it is working to identify, freeze, trace, and recover funds, with the US Attorney’s Office for the District of Columbia. Those are the agencies speaking for themselves. They are not a finished recovery. The findings are Binance’s first account of the path. They are not the last one.

A message that needs a recovery phrase is still not Binance, including one that claims to explain the findings. Binance’s own note says to use official channels. Nobody who can restore a withdrawal needs your recovery phrase, a code from a text, or a file that “updates your Binance wallet”. The findings do not ask anyone to download an assignment or to paste a seed. See How do you keep crypto safe?. See How crypto wallets actually work if the difference between a login and a key is still soft. A candle in the bitcoin price that morning is weather. It does not put the coins back and it does not tell you whether the promise will be kept.

What happens next

Whether a user can actually run the 12 November proof, which a quoted post says was generated on 14 November and which this page has not run. Whatever the 14 November notice left out of the 87 networks, which it aims to reopen by the end of next week, and which did not include INJ in the list the outlets printed. The SAFU refill, which is still a promise toward about $1 billion. What the Justice Department’s authorisation actually seizes, which is not a customer withdrawal. The Polygon proposal, which is not an approved fork. The independent review Binance said it would commission. Watch Binance’s own channel and the in-app withdrawal status. We will not treat completed coverage as the stolen coins returned, and we will not treat 87 networks as every network.

Not a recommendation to deposit, withdraw, or close a Binance account. Not a finding that any other exchange is safer. The FBI’s statement is the FBI’s. It is not this page identifying an attacker, and it is not a statement that the missing coins are back. The findings of 3 November name the path in at the level of a tampered installer, a fake recruitment, an internal AI tool, and a signing service. They do not publish a method this page will repeat.

Topics

This article is for information only and is not financial advice. Cryptoassets are volatile and you can lose money. See our disclaimer.

Comments

Keep it civil. First comments wait for an editor. This is not financial advice, and we remove spam or “DM me for signals” posts.

No comments yet. Be the first — keep it civil, and skip the tips.

Sign in to comment. Reading never requires an account.

Back to top

Continue reading

Stay a little clearer on crypto

Guides, reviews, and the news that actually matters. Unsubscribe anytime.

By subscribing you agree to our privacy policy.

More news

View all