Binance Says It Has Fully Covered $6.34B Hack Losses, Publishes 198-Token Proof of Reserves
Binance says it has finished replacing the assets stolen in the October 29 hack with more than $6.34 billion in company funds and published a new 198-token proof-of-reserves snapshot, though the zero-knowledge proof users need to verify it is still being generated and withdrawals are reopening in phases.

Table of Contents
Binance says it has finished covering the customer assets hit by the October 29 hack, the largest crypto theft on record. In an announcement posted on its support site on Thursday, November 12, 2026, and repeated in a post from its official @binance account on X the same day, the exchange said it "has completed coverage of assets impacted in the security incident" and has published a new proof-of-reserves (PoR) snapshot covering 198 tokens.
Two things are still open. Users cannot yet check the new snapshot themselves, because Binance says the zero-knowledge proof behind it will take about 40 to 50 hours to generate. And withdrawals are still coming back in phases, not all at once.
What Binance announced
The announcement, titled "Binance Completes Coverage of Assets Impacted in Security Incident; New Proof of Reserves Published", makes four main points:
Coverage is complete. Binance says it committed more than $6.34 billion in company funds to cover the losses and bought the affected tokens through market and over-the-counter (OTC) channels.
A new PoR snapshot is out. The snapshot was taken at 00:00 UTC on November 12, 2026, covers 198 tokens and is posted on Binance's proof-of-reserves website. Binance says it "provides an updated view of assets that are fully accounted for."
Withdrawals are still reopening in phases. Binance says it "will provide further updates as soon as they are confirmed." The announcement gives no date for a full return to normal.
Delisted tokens will be covered too. Binance says "a very small number" of tokens it no longer supports were also affected. They will be handled under its delisting process, and users who hold them will be covered.
Binance's co-CEO Yi He shared the same message on X with the caption "100%", according to BeInCrypto.
Coverage is not recovery
The key word in the announcement is coverage. Binance is saying that it has used its own money to replace the tokens that disappeared from its hot wallets, so customer balances are backed again. It is not saying that it has taken the stolen coins back from the attackers.
Binance names three sources for the money:
A partial deployment of SAFU. The Secure Asset Fund for Users is Binance's emergency reserve. CoinDesk has described it as a facility that has typically held around $1 billion in bitcoin. Binance says it will refill SAFU to "approximately US$1 billion" so that it "remains fully resourced as an emergency user-protection reserve." The announcement does not say when that will happen.
Part of the futures insurance fund. Binance says it used only the portion "above the level required under Binance's risk-management framework." Crypto.news reports that Binance has described these reserves as company funds that are separate from customer assets.
Binance's corporate treasury.
The announcement does not say how much came from each source. It also does not list the purchases token by token or say what share of the stolen crypto has been recovered. Crypto.news points out that the November 12 update gives no final split between the three sources.
Recovery is a separate process. On October 30, a Binance spokesperson told CoinDesk that about $3 billion had been frozen with the help of industry partners and that those figures were not counted in the coverage. The spokesperson said Binance was working with partners and law enforcement to recover the frozen assets. BeInCrypto, citing Chainalysis, reported about $2.8 billion frozen as of November 3. Frozen funds are not the same as recovered funds, and the November 12 announcement does not say how much, if any, has been returned or how recovered assets would be treated.
How coverage built up over two weeks
The November 12 statement is the last step in a process Binance has reported in stages:
October 30: CoinDesk reported that Binance had set aside more than $6.34 billion, and that $5 billion of it was already held in the same tokens that were stolen. The rest was being bought on public markets and OTC.
October 31: Binance took a PoR snapshot covering 10 tokens. Crypto.news reports that its recovery update that day put replacement coverage at 90%.
November 1: Withdrawals began reopening, starting with bitcoin and then expanding to other networks, according to Bitcoin Magazine.
November 2: The Block reported that Binance had finished the zero-knowledge proof for the October 31 snapshot. That let holders of BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC check their balances. Binance put coverage at about 95% at that point, with the last 5% in less liquid tokens.
November 4: Crypto.news reports that a new snapshot expanded coverage to 44 tokens and that replacement coverage reached about 98%. The remaining tokens took longer to buy because their markets were thin.
November 12: Binance announced that coverage was complete, with a 198-token snapshot.
The new proof of reserves and how to check it
A proof of reserves compares what an exchange owes customers in each asset with what it holds. Crypto.news, describing Binance's reserves page, says Binance uses a Merkle tree so each customer can confirm that their balance was included in the reported totals. A zero-knowledge system then checks the balance calculations without publicly revealing any individual user's holdings.
Based on that guidance, checking works roughly like this:
Wait until Binance says the zero-knowledge proof for the November 12 snapshot is finished. Until then, the 1:1 backing is Binance's own claim.
Log in and open the proof-of-reserves verification section of your account. Find your record ID and Merkle leaf for the snapshot.
Choose the November 12, 2026 verification date. This shows the assets covered and your balances as recorded at the snapshot.
Check that your holdings in the affected tokens appear and that the reserve ratio for each asset is at least 100%.
Reviewing the PoR portal for its own report, Spanish-language outlet DiarioBitcoin found the Merkle root hash field still marked "In Progress". That shows that publishing a snapshot and finishing the proof are two separate milestones. For the earlier rounds, crypto.news reports that Binance estimated 50 to 60 hours for the proof of the 44-token snapshot. The Block quoted Yi He as estimating about 40 to 50 hours after a snapshot is completed.
A PoR also has limits. As crypto.news notes, a March 2023 advisory from the US PCAOB's Office of the Investor Advocate says such reports describe assets at one point in time. It says they may not establish liabilities or borrowing arrangements, give no assurance about internal controls, and cannot show whether assets were still there after the snapshot. A PoR is a transparency tool, not an audit.
Background: the October 29 hack
According to CoinDesk, attackers drained an estimated $6.3 billion from Binance's hot wallets across several blockchains late on October 29. Most of the funds left in a burst of about 20 minutes and included BTC, ETH, USDT, USDC and smaller tokens. Binance first pointed to a compromised DevOps engineer's laptop that let attackers submit unauthorized withdrawal requests through internal systems. It later said it had found more exploit points, while saying it had seen no evidence that wallet private keys were stolen. Bitcoin Magazine reports that Binance's November 3 incident report traced the theft to a fake job interview and a poisoned developer tool.
Several sources point to North Korea, though not Binance itself. CoinDesk reported that Chainalysis and TRM Labs linked the attack to North Korean hackers with high confidence. Yonhap reported that the FBI attributed the theft to the North Korean group known as TraderTraitor. Kim Yo-jong, the sister of North Korean leader Kim Jong-un, rejected the FBI's findings as a "grave political provocation." Bitcoin Magazine notes that Binance's November 12 announcement does not name an attacker.
Laundering is still going on. As MyTraderBot reported, Elliptic found North Korean launderers minting throwaway meme coins to move stolen Binance funds through DEX pools on NEAR and other chains.
What it means for users and the market
For most Binance customers, the announcement means their balances in the affected tokens should be fully backed again by Binance's own funds. Binance had said users would not carry the loss, and it is now saying it has done that. Practically, three things matter:
Verification beats announcements. The best time to rely on the 1:1 claim is after the zero-knowledge proof is published and you have checked your own record.
Withdrawal access is still uneven. Some networks or assets may still have limited withdrawals. Check Binance's official announcements, not social media screenshots, for the status of a specific coin.
Expect phishing. Big incidents bring fake "compensation" and "verification" links. Treat any outside link asking you to "claim" compensation or "verify" a wallet with suspicion, and use only Binance's official app or website. MyTraderBot recently covered a claimed sale of Binance user data that the exchange called a likely scam.
The industry is also responding. Regulators are reacting to the wave of exchange hacks. South Korea's FSC, for example, now lets exchanges freeze deposits and withdrawals when a hack is suspected. CoinDesk reported that OKX founder Star Xu called for shared security standards, such as extra checks on large withdrawals to unknown addresses, enforced at the signing layer.
What to watch next
Completion of the zero-knowledge proof for the 198-token snapshot of November 12, and whether every asset shows at least 1:1 backing.
The withdrawal timeline: which networks and assets are still restricted, and when Binance confirms a full restart.
SAFU replenishment: when Binance confirms the fund is back near $1 billion.
Recovery of frozen funds: whether any of the roughly $3 billion that partners reported frozen is actually returned.
The investigation: any further official attribution, sanctions or law-enforcement action tied to TraderTraitor.
FAQ
Did Binance get the stolen crypto back?
Binance has not said that. It says it covered the losses with company funds and bought replacement tokens. Separately, a Binance spokesperson told CoinDesk that about $3 billion had been frozen with partners' help, but frozen does not mean recovered.
Where did the more than $6.34 billion come from?
Binance says it came from a partial use of SAFU, the part of its futures insurance fund above required levels, and its corporate treasury. It did not give the split.
Can I verify my balance now?
Not fully. Binance says users holding affected tokens will be able to check 1:1 backing once the zero-knowledge proof is generated. It puts that at about 40 to 50 hours of computation.
Are all withdrawals open?
No. Binance says withdrawals continue to reopen in phases and that it will share updates once they are confirmed.
What if I hold a token Binance has delisted?
Binance says the few affected delisted tokens will be handled under its delisting process and that holders will be covered.
This article reports statements by Binance and third-party outlets. It is not an independent audit of Binance's assets or liabilities, and it is not investment advice.
Sources & further reading
- Binance announcement: Binance Completes Coverage of Assets Impacted in Security Incident; New Proof of Reserves Published (2026-11-12)
- @binance on X: coverage completed, new PoR snapshot (2026-11-12)
- Binance Proof of Reserves page (2026-11-12 snapshot)
- Yonhap: Binance says all asset losses from N. Korea-linked cyberattack covered (2026-11-12)
- Bitcoin Magazine: Binance says it has fully covered the $6.34B hack with company funds (2026-11-12)
- crypto.news: Binance says $6.3B hack assets covered, reserve proof pending (2026-11-12)
- BeInCrypto: Binance customers hit by $6.3B hack are fully repaid, exchange says (2026-11-12)
- DiarioBitcoin: Binance dice que completó la cobertura de pérdidas (2026-11-12)
- The Block: Binance completes latest proof of reserves after record hack (2026-11-02)
- CoinDesk: Binance arranges $6.34 billion to cover losses from record crypto hack (2026-10-30)
See the signals and their results
Browse publicly logged signals and how they performed, or create a free account to follow them.





