Update, 3 November 2026: Binance has published its initial report on the attack. It says the entry points used have been closed and the affected systems rebuilt, and traces the campaign back to a tampered installer in June and a fake job interview in September. Details below.
Update, 2 November 2026: Binance says fiat withdrawals are now available in five more currencies, including the US dollar, bringing the currencies on its list to 28. The Defiant reports that withdrawals for several tokens remain suspended. Details below.
Update, 1 November 2026 (evening): Binance says withdrawals had resumed on all 15 networks in the first phase by 12:36 UTC, and that it processed $4.649 billion in withdrawals and $1.01 billion in deposits between 06:00 and 15:30 UTC, a net outflow of about $3.64 billion. Other networks are still being tested. Details below.
Update, 1 November 2026: The FBI says North Korea was responsible for the theft of more than $6 billion from Binance, and has asked crypto services to block addresses linked to it. Binance has begun reopening withdrawals in phases, starting with the bitcoin network, and says it has now covered about 95% of the impacted amount. Details below.
Update, 31 October 2026, 14:30 UTC: Binance says it has now covered up to 90% of the stolen assets, drawing on its SAFU fund, part of its Futures insurance fund and its own treasury, and has published a new Proof of Reserves snapshot. Withdrawals have not yet resumed; Binance says it is on track to reopen them on Sunday 1 November. Details below.
Update, 31 October 2026: Blockchain analytics firm Elliptic says $2.85 billion of the stolen funds, 44% of the theft, has been frozen or seized, and puts the total taken at $6.43 billion. Elliptic thinks North Korea’s TraderTraitor group is likely responsible; no government has confirmed that. Details below.
Update, 30 October 2026: Binance says it has reserved over $6.34 billion of company funds to cover the incident and has begun recovering affected assets. Earlier, it said it had found additional points of breach beyond the laptop it first suspected, and that withdrawals remain on track to resume in 45 hours. Details below.
Binance says it will cover every loss from a security incident that it estimates at around $6.3 billion, and that about $3 billion of the affected assets has already been frozen on-chain. In a security incident update published at 02:23 UTC on 30 October, the exchange said it “will cover all losses from the SAFU fund and the company’s funds”, adding: “User funds are safe.”
SAFU is Binance’s emergency insurance fund for users. The exchange said it would also publish an updated Proof of Reserves, its public accounting of customer assets, once remediation is complete.
Freezes, revoked access and a withdrawal pause
The first line of defence was the stablecoin freezes. Binance said it had worked with blockchain partners to freeze affected assets, and its verified frozen total rose through the night: $2.54 billion in a post on X at 23:22 UTC on 29 October, then “around $3 billion” by 00:52 UTC. Tether chief executive Paolo Ardoino said on X that Tether had frozen more than 1.567 billion USDT, and Circle’s Jeremy Allaire said Circle had frozen more than 800 million USDC.
Binance said it had also revoked the affected address authorisation and brought in law enforcement and blockchain intelligence partners to trace and recover funds. “We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice,” it said.
A later update, a service notice on X at 04:36 UTC, changes one detail of the overnight announcement. Deposits, initially suspended, “remain unaffected and continue to operate as normal”. Withdrawals stayed paused “while our team completes a security revamp of the withdrawal service and its related addresses”. Binance said: “We expect to resume within 48 hours.” At 08:47 UTC it said it was still on track, with withdrawals expected to resume in 45 hours.
Binance co-chief executive Richard Teng had earlier written on X: “I want to be direct: user funds remain SAFE.”
Update, 3 November: Binance says it has closed the entry points used in a months-long attack
Binance says it has shut the routes the attackers used and rebuilt the systems they touched. In its initial report on the incident, an article posted on X at 14:33 UTC on 3 November, it said: “The entry points identified as having been used in the attack have been closed.” It has rebuilt the affected wallet system in a new environment, rebuilt the internal AI tool that was misused along with its access controls, replaced affected devices and decommissioned the credentials and tokens of the engineers involved.
The exchange also says it has completed enhanced security scans of all employee devices, tightened device controls and wallet-service risk controls, and expanded AI-based behavioural anomaly detection. It is bringing in independent third-party cybersecurity experts to review the incident and validate its findings, and says some technical details will stay confidential so that attackers cannot use them.
The report opens with an apology. “This should not have happened, and we apologise for the concern, disruption and uncertainty it caused our users, partners and the wider industry,” Binance wrote. It puts the digital assets affected at about $6.34 billion, and says about $2.85 billion has been frozen or intercepted, “subject to reconciliation and market price volatility”. Binance says it will absorb the loss, and that as of 31 October 98% of the impacted token assets had been replenished; it is buying the remaining, less liquid assets. It does not explain how that figure relates to the 95% it gave on 1 November.
Binance calls the attack “a sophisticated, multi-stage campaign. It was not a single isolated breach or a simple phishing incident.” It began in June, when a Wallet DevOps engineer searched online for a popular AI coding tool and downloaded a tampered Homebrew installation. Homebrew is a widely used package manager for Mac computers. Binance’s security team spotted the anomaly, replaced the device and rotated the related credentials, but the report says the engineer’s role and his colleagues on the wallet infrastructure team had been exposed to the hacker. The report links to a SANS Internet Storm Center diary from May describing a malicious search advert for a fake Homebrew page that delivered MacSync Stealer to Mac users; Binance does not say that was the same campaign.
In September a second engineer was approached on a legitimate job-hunting platform by someone posing as a project director. After a live video interview with a supposed HR representative, a second interview took place in a chat app, where he was told to download an “assignment” to his work computer. Malicious code in the repository ran during setup and replaced part of a legitimate development tool with a malicious version; the steps Binance published show pyenv, a Python version manager, being swapped. Binance says the “0-day malware was not detected by the endpoint security protection tools at the time”.
On 20 October the attacker used that computer and an internal AI tool to take control of the first engineer’s machine and a third engineer’s, then found a container deployment permission token on the first engineer’s computer. On 29 October, between 17:15 and 19:56, the attacker logged on to the third engineer’s computer, used the stolen credentials to deploy a container and triggered a malicious script.
The theft began at 20:05 UTC. Binance says the attacker abused an internal wallet signing service to send transactions outside the normal withdrawal process: 233.46 million XRP from five hot wallets by 20:09 UTC, about 970,500 SOL and 44.2 million OP, then 18,270 BTC. The attacker then used the signing service to exploit EIP-7702, an Ethereum feature that lets an account delegate some execution rights to a smart contract, submitting 50 signing transactions to set up malicious delegations over a Binance hot wallet.
Those delegations are why pausing withdrawals was not enough. They existed on-chain and worked independently of Binance’s withdrawal systems, and because the hot wallet used multi-party computation (MPC), there was no single private key that could revoke them at once. Binance says it had to develop a special procedure. The final unauthorised transfer, 2,961.9 ETH, finalised on-chain at 23:56 UTC, and at 00:10 UTC on 30 October Binance cleared the delegation with a new authorisation from its Binance14 hot wallet to the zero address.
Binance cites the FBI’s finding that North Korea was responsible, and says its security team detected and prevented 57 suspected North Korea-linked cyber threat cases during 2026, using lures such as fraudulent job interviews and malicious software disguised as developer tools. North Korea rejects the FBI’s attribution. Kim Yo Jong, sister of leader Kim Jong Un, called it “a grave political provocation” in a statement carried by the state news agency KCNA, Yonhap reported on 3 November.
The fixes target people and permissions, not wallet keys
Every fix Binance lists covers devices, credentials, an internal AI tool or signing permissions; none concerns its wallet cryptography. That fits its earlier statement that it found no wallet private key leak. On Binance’s account, the attackers did not break the keys but got a signing service to use them. For other exchanges, the lessons sit in the controls around signers: which machines can deploy containers near them, which tokens live on engineers’ laptops, and whether an internal AI assistant can be turned into a route to other staff devices.
The report also shows how hiring scams have become a front door for crypto theft, the pattern Microsoft described when it said North Korean hackers use AI to scale familiar attacks, and that US authorities targeted when they sanctioned people over North Korean IT worker schemes. A fake interview, a coding assignment and a tool installed from a search result each look routine on their own. Joined up between June and October, they reached the wallets.
From a compliance and operational-resilience view, the EIP-7702 detail matters as much. A pause switch inside an exchange’s own systems cannot undo permissions already written to a blockchain, so incident plans need a tested way to revoke them quickly, a point TRM made when it advised treasury teams to watch for unexpected delegations. Hacken’s third-quarter report had already found that most of that quarter’s losses came via suppliers. Binance calls this an initial report; the independent review it has promised, and how much of it is published, will decide what other firms can verify.
Update, 2 November: dollar and four other fiat withdrawals open, while some tokens stay shut
Binance has added the US dollar to the currencies its users can withdraw to a bank. In a “Fiat Withdrawal Update” posted on X at 08:00 UTC on 2 November, it said fiat withdrawals “are now available” for five currencies marked as new: the US dollar (USD), the UAE dirham (AED), the Vietnamese dong (VND), the Philippine peso (PHP) and the Indonesian rupiah (IDR). It listed 23 more as current, among them the euro, the Japanese yen, the Brazilian real and the Mexican peso, which makes 28 in all by TSN’s count. “We will continue to share further updates through official Binance channels,” it said.
The post does not say when the 23 current currencies became available, or whether fiat withdrawals were paused during the incident. TechFlow reported the same five additions, citing a Binance announcement.
On the crypto side, The Defiant reports that all 15 initial network groups have reopened but that withdrawals for several other tokens remain suspended. Binance’s own latest word is its 1 November post, which said withdrawals had resumed for all 15 networks and assets in the first phase and that its team “continues testing rigorously the remaining networks and assets”. Its fiat post gives no date or list for that next phase.
So the way out is now wider for cash than for some coins. A customer can move a dollar balance to a bank, but anyone holding a token outside the first phase still cannot take it off the exchange. Binance has said the last 5% of the losses it has yet to cover are less liquid tokens outside its top ten. The next checks are the Proof of Reserves report Binance said it expected on 2 November and a date for the remaining tokens.
Update, 1 November (evening): phase one complete, with a net outflow of about $3.64bn
Binance says the first phase of its withdrawal reopening is complete. In a post on X at 16:12 UTC on 1 November, it said it “began restoring withdrawals in phases at 06:00 UTC” and that “by 12:36 UTC, withdrawals had resumed for all 15 networks and assets in the initial phase”. The remaining networks and assets are not yet open: Binance said its team “continues testing rigorously the remaining networks and assets” and will “share details of the next phase as soon as we can”.
It also gave its first figures for money leaving the exchange. “Between 06:00 and 15:30 UTC on November 1, we processed $4.649 billion in withdrawals and $1.01 billion in deposits, resulting in a net outflow of approximately $3.64 billion,” it said. Binance put that at 2.1% of its $171 billion in total assets under management, “based on the latest available Proof of Reserves (PoR) data as of October 28, 2026”, so the percentage is measured against assets before this week’s withdrawals reopened. It said that “after an initial spike, withdrawal volumes have declined and are stabilising as expected, while deposit volumes have remained substantial”.
The next check is the reserves report. Binance said a new Proof of Reserves snapshot was taken at 00:00 UTC on 31 October and that the zero-knowledge proof computation, which lets users verify their own balances, had begun. “The updated report is expected to be available on our PoR website tomorrow,” it said, meaning 2 November; on 31 October it had estimated 3 November. These are Binance’s own figures; TSN has not checked them independently.
Update, 1 November: FBI names North Korea as Binance reopens withdrawals in phases
The FBI says North Korea was behind the theft. In a cyber alert dated 31 October, it said North Korea “was responsible for the theft of more than $6 billion USD in virtual assets from cryptocurrency exchange Binance, on or about October 29, 2026”. The FBI calls this activity “TraderTraitor”. It is the first government attribution of the attack; until now, North Korea’s role had been the assessment of the analytics firms TRM Labs and Elliptic.
The alert is, above all, a request to block the stolen funds. The FBI says that it and its partners at the US Secret Service (USSS) and IRS Criminal Investigation (IRS-CI) have seen TraderTraitor actors “converting stolen assets primarily into Ethereum (ETH)”, and that it expects the assets to be laundered further “using DeFi and instant swap services”. The three agencies are “urging private sector entities including THORNode operators, RPC node operators, instant exchanges, DeFi services, blockchain analytics firms, and other virtual asset service providers to block transactions with or derived from addresses TraderTraitor actors are using to launder these stolen assets”.
The alert lists addresses that, it says, “are holding or have held assets from the theft”. By TSN’s count, the list has 608 Ethereum addresses, 19 bitcoin addresses and one Solana address. The FBI asks anyone with information to contact a local FBI field office or its Internet Crime Complaint Center at ic3.gov.
A fixed list will not be enough on its own. Chainalysis chief executive Jonathan Levin said in a statement that the attackers had already used “thousands of addresses”, CoinDesk reported. “We anticipate this will become tens of thousands over the coming weeks as money is transferred through a broader money laundering network,” he said, adding that the money would flow to “a wider network of services, like bridges, instant exchanges, and swappers”. That is why the FBI’s request is aimed at swap services and node operators as well as exchanges: screening has to follow each new hop, not only the addresses on the first list.
Binance, meanwhile, has started to reopen withdrawals. In Recovery Update #4, published on 1 November and posted on X at 04:11 UTC, it said it was “preparing to resume phase one of withdrawals on 2026-11-01 between 06:00 and 09:00 (UTC)”. Phase one covers 15 listed networks, among them BTC, ETH, BSC, TRX and SOL, which Binance says will become available “progressively”; other networks and assets “will be added once they are ready”. In a post on X last edited at 06:20 UTC, Binance said the first network opened in phase one was the bitcoin network. Deposit services “remain open and are not affected by the incident”, it said.
For users, that means a withdrawal on a network that has not yet reopened will not go through. Binance asks users to check the withdrawal page for their asset and network, or its network status page, and warns of “temporary delays or longer processing times due to traffic volume”. If a withdrawal on a listed network does not go through, it says, “you can try again after a short while”. Binance’s own site, app and official accounts are the places to check status.
On the money, Binance says it “has now covered approximately 95% of the impacted amount, up from 90% in our prior update”. It says: “The outstanding 5% are tokens outside the top ten listed above, and are less liquid in the market and take longer time to source at the required scale.” It repeated: “Binance will absorb the financial impact of the stolen funds, not our users.” Once its investigation is complete, it says, it will publish “a post-incident report with further details on the incident”.
Co-chief executive Richard Teng wrote on X at 05:11 UTC: “Today, we’re beginning the phased resumption of withdrawals, taking a careful approach to ensure services return safely and securely.” Binance co-founder Yi He said on X at 04:48 UTC that wallets for other currencies “are still undergoing repeated security audits and perimeter checks”.
The coverage figures are still Binance’s own, and Binance’s update does not say who was behind the attack or how the attackers got in. The post-incident report will need to answer the second question. For earlier thefts and how they were traced, see TSN’s crypto hacks and exploits hub.
Update, 31 October: Binance says users are now up to 90% covered
Binance says it has now covered up to 90% of the assets taken in the theft. In a recovery update published on 31 October and posted on X at 14:30 UTC, it said that at the time of its previous update it had “already covered approximately 80% of the impacted amount”, and that “that covered amount is now up to 90%”. It added: “All BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD, and ZEC are fully backed 100%.”
The outstanding 10%, Binance says, “consists of tokens outside the top ten listed above”. These are “less liquid”, so they may take longer to source, and it is still buying them “through market and OTC channels” with help from industry partners. “Binance will absorb the financial impact of these stolen funds, not our users,” the update says.
The money has come from three places, according to Binance: a partial deployment of SAFU, which is “expected to happen over the next 24 hours”; “a portion of our Futures insurance fund”, the rest of which it says is a regulatory requirement; and “Binance’s own corporate treasury”. It says it is committing to replenish SAFU “to return the fund size to approximately US$1 billion”.
The exchange has also taken a new Proof of Reserves snapshot, dated 00:00 UTC on 31 October, and published it on its Proof of Reserves website. The full zero-knowledge proof, which will let holders of the ten tokens check for themselves that their assets are backed at least 1:1, takes “approximately 40 to 50 hours” to generate, and Binance estimates it will be ready by Tuesday 3 November (UTC).
Withdrawals have not yet resumed. “We remain on track to reopen withdrawals within our previously stated timeframe (on Sunday, 2026-11-01) and will provide a further update as soon as details are confirmed,” Binance said. Co-chief executive Richard Teng wrote on X at 14:33 UTC: “We’ve now replenished 90% of the stolen assets, and we’re committed to covering the remaining 10%. Our users will not bear the financial impact of this incident.”
The coverage figures are Binance’s own. Users will only be able to check their balances against the new snapshot once the full proof is out, and the reopening of withdrawals remains a target, not an event.
Update, 31 October: Elliptic says $2.85bn of the stolen funds is frozen or seized
Freezes and seizures now cover close to half of the Binance theft, according to blockchain analytics firm Elliptic. In an analysis by Dr Tom Robinson, last updated at 05:00 UTC on 31 October, Elliptic says it “has verified $2.85 billion of frozen or seized funds, 44% of the theft, almost all of it USDT and USDC”. That is close to Binance’s own estimate of around $3 billion frozen.
Elliptic sets out how quickly the issuers moved. Tether froze the attacker’s main Ethereum wallet 37 minutes after the stolen USDT arrived, locking 1.18 billion USDT, and then froze four more attacker addresses within 17 minutes. Circle froze the 823 million USDC in the same wallet three minutes later. Ripple, World Liberty Financial, Paxos and First Digital froze further stablecoins, and the Arbitrum Security Council took emergency action to move assets out of the attacker’s reach. On 31 October, Elliptic says, Optimism’s governance appears to have done the same with 44 million OP, around $5 million. Elliptic has published the addresses it links to the theft so that exchanges and other firms can screen against them.
Elliptic puts the total at $6.43 billion, slightly above Binance’s estimate of around $6.3 billion and TRM’s $6.36 billion, and calls it “more than four times the $1.46 billion stolen from Bybit in 2025”. It says hot wallets on 11 blockchains were drained from about 20:05 UTC on 29 October. The largest losses were on Ethereum, “where $3.80 billion was taken across 186 different tokens, including 1.9 billion USDT and 823 million USDC”. The attacker also took “18,270 BTC, worth $1.48 billion, and 612.7 million USDT on Tron”, Elliptic says.
The rest is harder to stop. Elliptic says the attacker is swapping it “into ETH and other assets that cannot be frozen, and moving funds between blockchains, using automated scripts that run around the clock”. It estimates that about $3.21 billion now sits in assets no issuer can freeze, and says some funds on Tron have been laundered alongside proceeds of the September 2026 exploit of Bitget. That puts the burden on exchanges and brokers to catch the funds when they try to cash out.
On attribution, Elliptic says that “based on the evidence, Elliptic believes it is likely that North Korea’s TraderTraitor hacking group perpetrated the theft”. It adds: “No government has yet confirmed attribution.” That is Elliptic’s assessment, in line with TRM’s earlier one. Binance has still not said who was behind the attack or what the additional points of breach were, and it has not yet confirmed that withdrawals have resumed.
Update, 30 October, 10:55 UTC: Binance has set aside over $6.34bn and begun recovery
Binance has put a number on its coverage pledge. In a post at 10:55 UTC on 30 October, via @binance on X, it said: “Binance has already reserved over $6.34B of company funds to cover this incident. $5B of these funds are already held in the exact token assets that were impacted.” It is buying the rest “through market channels and OTC channels” to match the tokens that were taken, and warned that this “can take longer because some tokens may have low liquidity and OTC settlement also takes time”.
The exchange said it “has begun recovering affected assets for users”. It said the reserved figures “do not include frozen or protected assets”, and that “currently, $3bn has been frozen”, the same total as before. It repeated that user funds will be verified publicly through its Proof of Reserves.
One recovery is already on-chain. Synthetix, which describes itself as a perpetual futures exchange on Ethereum and is behind the SNX token, said on X at 10:42 UTC that “the SNX stolen from Binance has been recovered by the Synthetix protocolDAO”, and that the tokens “will be sent back to Binance on request”. The transaction it linked shows 8.41 million SNX moving from an address Etherscan labels as a Binance hot wallet exploiter to Synthetix’s protocolDAO at 23:03 UTC on 29 October. Recoveries by a token’s own project cannot reach the ether and bitcoin that TRM says the attacker still holds, since neither has an issuer that can step in.
None of this changes Binance’s estimate of the impact, about $6.3 billion, its account of the cause, or its timetable for resuming withdrawals.
Update, 30 October: Binance says it found additional points of breach
Binance has widened its account of how the attack happened. In an investigation update on X at 08:47 UTC on 30 October, it said: “Our initial investigation suggested that the security incident may have involved a compromised laptop, however our subsequent investigation has uncovered additional points of breach.” It called the incident “a complex attack” and said it was “doing all we can in coordination with law enforcement to resolve it”, adding that it is still gathering the facts.
The exchange said it is “still on track towards the expected timeline to resume the withdrawal service in 45 hours”, and that deposits remain unaffected. Outflows stopped when withdrawals were paused, it said, and it has “frozen around $3 billion thus far” while it works with partners to freeze more. It repeated that it will cover all losses from SAFU and company funds.
About an hour earlier, co-chief executive Richard Teng wrote on X that “the attacker did not simply use one engineer’s permissions, and this was not a single ‘one-click’ action. It involved a more complex attack process. Our investigation has not attributed responsibility to any individual.” He put the estimated total impact at “~$6.3B, with ~$3B frozen on-chain so far” and said Binance has still found no evidence of a wallet private key leak.
Several points of entry turn the question from one employee’s device to the controls around Binance’s withdrawal systems, which the technical post-mortem Teng has promised will need to address. Binance still has not said who was behind the attack; the North Korea attribution below was then TRM’s assessment alone. The FBI confirmed it on 31 October.
What Binance and TRM say happened
Binance first said it was “aware of reports of a potential security issue” at 21:15 UTC on 29 October. Its announcement gives an initial finding: the incident “may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions”. It said it had “found no evidence of any wallet private key leak”. In the 04:36 UTC update it said the incident “stems from multiple factors”, and promised a full root-cause report. By 08:47 UTC it said its investigation had “uncovered additional points of breach” beyond the laptop.
Blockchain analytics firm TRM Labs has published its own analysis of the theft. It puts the amount moved out of Binance wallets at about $6.36 billion across ten blockchains, most of it in about 20 minutes from 20:05 UTC. TRM says that makes it the largest crypto theft on record, about four times the $1.5 billion Bybit theft of February 2025.
TRM attributes the attack “with high confidence” to TraderTraitor, a group linked to North Korea that the FBI named over Bybit. That was TRM’s assessment; on 31 October the FBI said North Korea was responsible and named the activity TraderTraitor. Binance has not itself attributed the incident to anyone.
On the cause, TRM’s reading differs in emphasis from Binance’s. Because wallets on many chains, with different key types, produced valid transfers within about half an hour, TRM says the most likely explanation is that the attacker could make Binance’s hot wallet signing system “sign transactions of its choosing across chains”. That is consistent with Binance finding no leaked private keys, but Binance has not confirmed it. TRM counts about $2.7 billion frozen as of 00:30 UTC, a little below Binance’s later figure.
Why the freezes worked and where they stop
The freezes show how much of a large theft now sits in assets that a central issuer can stop. Tether and Circle acted within about an hour of the main transfers, according to TRM, and Binance’s verified frozen figure climbed from $2.54 billion to about $3 billion in about 90 minutes. By TSN’s arithmetic, without them the gap Binance has pledged to fill would be roughly twice as large.
The limit is everything else. TRM estimates that the attacker still controls about $2.4 billion in ether and bitcoin, which no issuer can freeze, and expects those funds to move through bridges, swap services and over-the-counter brokers. Recovery from here depends on exchanges and trading desks screening deposits, which is why TRM is urging them to check counterparties against the addresses it has labelled.
The cause matters for the wider industry. Binance now says the laptop was not the only point of breach, but it still reports no evidence of a wallet private key leak, so on its account this was a break-in rather than a broken wallet, and Hacken’s third-quarter report found that most of that quarter’s $1.18 billion in losses came via suppliers, another sign that the weak points are often the systems around wallets. TRM recommends that treasury teams watch Ethereum wallets for EIP-7702 delegations, a feature that lets a wallet hand control to a smart contract, and reject unexpected ones. It also advises separating signing systems by chain and wallet tier, so that one compromise cannot reach wallets on ten chains.
The coverage pledge is the other test. Binance has said it will pay from SAFU and its own funds, and by 10:55 UTC on 30 October said it had reserved over $6.34 billion of company funds, $5 billion of it already in the affected tokens, and the Proof of Reserves it has promised will be the first public check of whether customer balances remain fully backed. Binance took a new snapshot on 31 October and said on 1 November that the report, with the zero-knowledge proof that lets users check their own balances against it, was expected on its Proof of Reserves website the next day, 2 November. The full accounting can take time: CoinDCX admitted “operational losses” from wallets compromised in 2025 well after the event.
The FBI has now answered the North Korea question; tracing and blocking the rest of the funds will take longer. Microsoft said this week that North Korean groups are using AI to scale familiar attacks on crypto firms, and the US Treasury has sanctioned people over North Korean IT worker schemes. The FBI now says this incident fits that pattern; Binance has not said so itself.
Sources
Primary:
– Binance on X: 29 October Binance Security Incident: Initial Findings and Response Update (X article), 3 November 2026, 14:33 UTC
– Binance on X: Fiat Withdrawal Update (USD, AED, VND, PHP and IDR added), 2 November 2026, 08:00 UTC
– Binance on X: phase one of withdrawals complete; withdrawals, deposits and net outflow, 1 November 2026, 16:12 UTC
– FBI: North Korea Responsible for $6 Billion+ Binance Attack (FBI cyber alert, 31 October 2026)
– Security Incident | Recovery Update #4: Withdrawals Resume in Phases (Binance announcement, 1 November 2026)
– Binance on X: Recovery Update #4, 1 November 2026, 04:11 UTC
– Binance on X: bitcoin network first opened in phase one of withdrawals, 1 November 2026, 06:20 UTC
– Richard Teng on X: phased resumption of withdrawals, 1 November 2026, 05:11 UTC
– Yi He on X: phase one of withdrawals, 1 November 2026, 04:48 UTC
– Security Incident | Recovery Update #3: 90% of Stolen Assets Replenished; Proof of Reserves Snapshot Provided (Binance announcement, 31 October 2026)
– Binance on X: Recovery Update #3, 31 October 2026, 14:30 UTC
– Richard Teng on X: 90% of stolen assets replenished, 31 October 2026, 14:33 UTC
– Security Incident Update (Binance announcement, 30 October 2026)
– Binance on X: over $6.34B of company funds reserved, recovery begun, 30 October 2026, 10:55 UTC
– Synthetix on X: stolen SNX recovered by the protocolDAO, 30 October 2026, 10:42 UTC
– Etherscan: transfer of 8.41M SNX to Synthetix protocolDAO, 29 October 2026, 23:03 UTC
– Binance on X: Investigation update, 30 October 2026
– Richard Teng on X: not a single one-click action, 30 October 2026
– Binance on X: Service Update, 30 October 2026
– Binance on X: verified frozen total around $3 billion, 30 October 2026
– Binance on X: verified frozen total $2.54 billion, 29 October 2026
– Binance on X: first acknowledgement, 29 October 2026
– Richard Teng on X, 30 October 2026
– Paolo Ardoino (Tether) on X, 29 October 2026
– Jeremy Allaire (Circle) on X, 29 October 2026
Analysis (attributed, not a primary for Binance’s statements):
– SANS Internet Storm Center: Malicious Ad for Homebrew Leads to MacSync Stealer (Brad Duncan, 1 May 2026; linked in Binance’s report)
– TRM Labs: North Korea steals USD 6.36 billion from Binance in the largest hack in history, 29 October 2026
– Elliptic: The largest theft in history: North Korea likely behind the $6.4 billion Binance hack (Dr Tom Robinson, 30 October 2026, updated 31 October 2026, 05:00 UTC)
Press:
– Yonhap: N. Korean leader’s sister blasts FBI’s crypto theft probe as ‘political provocation’, 3 November 2026
– The Defiant: Binance Restores USD Withdrawals as Post-Hack Reopening Expands, 2 November 2026
– TechFlow: Binance Adds Support for 5 Fiat Currency Withdrawals Including USD, 2 November 2026
– CoinDesk: FBI confirms North Korea’s role in $6 billion Binance hack, asks DeFi community to block BTC, ETH, SOL addresses, 31 October 2026
Related stories
- Chainalysis Restores Reactor and KYT After Breach Hit
- Keplr Pauses Google and Apple Login After Wallet Reports
- Binance Will Shut Down Binance Pool and Related Mining Services on 10 November 2026
- CoinDCX Admits ‘Operational Losses’ From Wallets Compromised in 2025
- Drift Exploiter Moves About $61m of Ether Into Tornado Cash, Cointelegraph Says
- Hacken: Crypto Hacks Cost $1.18bn in Q3 2026, Mostly via Suppliers
- CryptoBilis Changed Hands in March, Its Former Founders Say; CZ Alleges Hackers Bought the Reseller
- Israeli Man Extradited to US to Face Nomad Bridge Hack Charges
- Threshold Pauses tBTC Minting as Aave Halts New tBTC Deposits
- Microsoft Says North Korean Hackers Use AI to Scale Familiar Attacks
- BTCPay Server Says Hot Wallets Swept on 2.4.1 and Older
- Mercado Bitcoin Halts Deposits and Withdrawals After Attack
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X





