Skip to content

Binance hot wallets drained on Oct 29, 2026: where the funds went

  • Binance
  • Cause not confirmed
  • 10 chains · Solana traced
  • Active

Started · Last checked · Updates

Binance puts its Oct 29, 2026 incident at around $6.3B; about $3B is frozen and 90% replenished. What left each of ten chains and where it is now. (Binance, Oct 30, 2026, Binance, Oct 30, 2026, and 30 more in Sources)

Where it stands

Withdrawals
Paused; Binance expects them back on Nov 1
(Binance, Oct 30, 2026, Binance, Oct 31, 2026)
Binance says
90% of the losses replenished
(Binance, Oct 31, 2026)
Frozen so far
About $3B, by Binance’s count
(Binance, Oct 30, 2026)

Quick answers

Who hacked Binance?

Binance confirmed a security incident and puts the impact at around $6.3B. On Oct 31 the FBI said North Korea was responsible for the theft of more than $6 billion from Binance; it calls this activity “TraderTraitor”. (Binance, Oct 30, 2026, FBI, Oct 31, 2026)

Are my funds on Binance safe?

Binance says its users won’t bear the losses. By Oct 31 it had replenished 90% of what was taken, with BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC fully backed, and it published a Proof of Reserves snapshot from 00:00 UTC that day; the full proof is due by Nov 3. traceme can’t check an exchange’s books: these are Binance’s statements. (Binance, Oct 30, 2026, Binance, Oct 31, 2026)

Can I withdraw from Binance?

Not yet. Binance paused withdrawals for its security checks, while deposits keep working. Its update of Oct 31 expects withdrawals to reopen on Sunday, Nov 1, in phases. (Binance, Oct 30, 2026, Binance, Oct 31, 2026)

5 more questions
How much was taken?

Binance estimates the impact at around $6.3B. Counted from each chain, what left includes 2,488,194,179.07 USDT on Ethereum and Tron, 823,000,000 USDC, 18,270.2 BTC, 233,461,943.1 XRP, 205,965.6 ETH on Ethereum and Arbitrum, and 970,521.9 SOL, beside other tokens. (Binance, Oct 30, 2026, Transaction 0x53bd…e2f3 on Etherscan, and 35 more in Sources)

How much is frozen?

Binance counts about $3B frozen on chain with blockchain partners so far. Read on chain, Tether has frozen 1,767,593,981.61 USDT on Ethereum, Tron and Avalanche, Circle 824,563,812.78 USDC on Ethereum, and the Arbitrum Security Council 8,425 ETH and 74,559,805.2 ARB on Arbitrum. (Binance, Oct 30, 2026, Tether’s freeze of 0x5227…2f8c: isBlackListed on Etherscan, and 8 more in Sources)

Has the money moved?

Part of it. Read again on Nov 1, the BTC and XRP hadn’t moved since Oct 29, and 505,617.74 ETH sat in six addresses on Ethereum, not frozen, none of which has sent anything. The SOL began to move on Nov 1: 503,850.52 SOL left Affz…BEaU in 12 transfers, 485,277 SOL of it to one new wallet. The 44,231,858.70 OP moved on Oct 31 to one new address. On Tron, 199,000,000 USDT had moved on before Tether’s freeze, and on Base the VIRTUAL had moved on. (rK21…fzMx on XRPSCAN, Address Affz…BEaU, and 41 more in Sources)

Was SOL taken?

Yes. 970,521.9 SOL left 5tzF…uAi9, a wallet Solscan labels Binance 2, in five transfers between 20:10 and 20:33 UTC on Oct 29, all to one new wallet. On Nov 1 that wallet sent 503,850.52 SOL on, in 12 transfers to two new wallets. (5tzF…uAi9 on Solscan, Transaction 5Yvw…Tqk2, and 17 more in Sources)

How did it happen?

Binance’s first findings pointed to a DevOps engineer’s laptop that may have been compromised, which gave access to a service container used to submit withdrawals. Its second update adds that later findings uncovered more points of breach, and that it has found no sign that a wallet’s private key leaked. (Binance, Oct 30, 2026, Binance, Oct 30, 2026)

Timeline

  1. On the XRP Ledger, 185,017,485.5 XRP went to rK21…fzMx. Four more accounts paid it by 20:09:20: 233,461,943.1 XRP in all. (Transaction 78E3…FA6A on XRPSCAN, Transaction 6DDF…7E67 on XRPSCAN, and 3 more in Sources)

  2. 965,455.1 SOL left 5tzF…uAi9 for Affz…BEaU, a wallet with no history before it. (Transaction 5Yvw…Tqk2, Address Affz…BEaU)

  3. 1,266.7 SOL followed, then three more of 1,266.7 SOL at 20:26, 20:28 and 20:33: 970,521.9 SOL in all. (Transaction 333s…v3Rc, Transaction aLao…fxhD, and 2 more in Sources)

  4. On Base, 4,735,627.3 VIRTUAL left 0x3304…566a for 0x5227…2f8c. (0x3304…566a on BaseScan, 0x5227…2f8c on BaseScan)

  5. On Optimism, 44,231,858.2 OP left 0xacd0…435a for 0x5227…2f8c. (Transaction 0x10b5…33bf on Optimistic Etherscan)

  6. On Tron, 46,394,098 TRX left TDqS…hSCf for TG5i…zsGi by 20:21:12, then 612,729,468 USDT at 20:22:45. (Transaction 4203…253e on Tronscan, TDqS…hSCf on Tronscan, TG5i…zsGi on Tronscan)

  7. On Bitcoin, 11 transactions in one block sent 18,270.2 BTC to bc1q0mtc…2mnm. (Transaction f9dc…0313 on mempool.space, Transaction 48ba…e6a1 on mempool.space, and 9 more in Sources)

  8. On Ethereum, the first of 13 transactions reached 0x5227…2f8c. By 21:44:11 they had brought it 1,875,464,711.07 USDT, 823,000,000 USDC, 197,539.6 ETH and 62 other tokens. (Transaction 0x53bd…e2f3 on Etherscan, Transaction 0x2c45…260b on Etherscan, and 11 more in Sources)

  9. On Avalanche, five wallets began sending 0x5227…2f8c 2,258,635.9 AVAX and 8,409,928.4 USDt, the last at 23:04:30. (Transaction 0x771c…6e9a on Snowtrace, Transaction 0x23a4…da28 on Snowtrace, and 5 more in Sources)

  10. bc1q0mtc…2mnm had split the Bitcoin into 19 addresses, 17 of them holding 1,000 BTC each. (Transaction 58bb…d625 on mempool.space, Transaction 27cd…f68b on mempool.space, and 17 more in Sources)

  11. On Polygon, 46,626,589.6 POL and 6,185,900.1 USDT0 left 0xe780…e245 for 0x5227…2f8c. (Transaction 0x27f8…38c8 on PolygonScan, Transaction 0x8f5c…b25b on PolygonScan)

  12. The Arbitrum Security Council froze 8,425 ETH and 74,559,805.2 ARB on Arbitrum, at an address only an ArbitrumDAO vote can move them from. (Arbitrum Security Council, Oct 30, 2026, Transaction 0xb69c…55d6 on Etherscan)

  13. Binance published its Security Incident Update. (Binance, Oct 30, 2026)

  14. Binance published Security Incident Update #2: more than $6.34B of company funds set aside, about 80% of the losses covered, about $3B frozen. (Binance, Oct 30, 2026)

  15. On Optimism, the 44,231,858.70 OP left 0x5227…2f8c for 0x6b1b…4e3b. (Transaction 0x120a…bed7 on Optimistic Etherscan)

  16. Binance published Recovery Update #3: 90% of the losses replenished, and a Proof of Reserves snapshot from 00:00 UTC. (Binance, Oct 31, 2026)

  17. The FBI said North Korea was responsible for the theft of more than $6 billion from Binance, activity it calls “TraderTraitor”, and listed the addresses holding or that held the funds. On Solana it names one: Affz…BEaU. (FBI, Oct 31, 2026, Address Affz…BEaU)

  18. Affz…BEaU signed its first transaction: 7 SOL to Eze8…DrrD, a new wallet. At 09:39:08 it sent that wallet 485,270 SOL. (Transaction 631P…gwGV, Transaction 66E4…6wkx, Address Eze8…DrrD)

  19. Affz…BEaU began sending SOL to 7SDu…Q2fK: 18,573.52 SOL in ten transfers by 14:51:05. From 10:10:37 7SDu…Q2fK sent SOL on to 35 wallets, 27 of them 500 SOL each. (Transaction 4i9j…9kaJ, Transaction 3joF…K557, and 9 more in Sources)

What Binance has said

  • Its first findings point to a DevOps engineer’s laptop that may have been compromised. That gave access to a service container, which was used to submit withdrawal transactions Binance hadn’t authorised. (Binance, Oct 30, 2026)

  • It found no evidence that any wallet’s private key leaked, and will publish a detailed post-mortem once the facts are verified. (Binance, Oct 30, 2026)

  • It estimates the total impact at around $6.3B, and says about $3B has been frozen on chain so far, working with blockchain partners. (Binance, Oct 30, 2026)

  • It will cover all losses from its SAFU fund and the company’s funds, says user funds are safe, and will publish an updated Proof of Reserves once the cause is fixed. (Binance, Oct 30, 2026)

  • It paused withdrawals, kept deposits running, revoked the affected address authorisation, and brought in law enforcement and blockchain intelligence partners to trace and recover the funds. (Binance, Oct 30, 2026, Binance, Oct 30, 2026)

  • Its second update, on Oct 30: later findings uncovered more points of breach than the laptop, and it set aside more than $6.34B of company funds, $5B of it in the same tokens that were taken. (Binance, Oct 30, 2026)

  • By Oct 31 it had replenished 90% of the losses: BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC fully, from part of its SAFU fund and its futures insurance fund, its treasury, and purchases. The other 10% is in less liquid tokens it is still buying. (Binance, Oct 31, 2026)

  • It took a Proof of Reserves snapshot at 00:00 UTC on Oct 31, with the full proof expected by Nov 3, and expects withdrawals to reopen on Nov 1. (Binance, Oct 31, 2026)

What the chain shows

How it happened

Binance’s first findings: a DevOps engineer’s laptop that may have been compromised gave access to a service container, which was used to submit withdrawals. It found no sign of a leaked private key. (Binance, Oct 30, 2026)

On Solana, 5tzF…uAi9 signed the five transfers itself, as plain transfers: nothing on chain changed who controls it first. (Transaction 5Yvw…Tqk2, Transaction 333s…v3Rc, and 3 more in Sources)

How the access was gained in detail is for Binance’s post-mortem, which it has promised. (Binance, Oct 30, 2026)

Sources

Statements

On the chain

Every transaction and address this page links (137)

If you use Binance: what to do now

Take news of this only from Binance’s own website and X account. Never follow a refund, support or recovery link from a message. Binance’s website · X account

Ignore anyone who contacts you offering to get it back, and anyone who wants a fee upfront to recover it, however official they look: offers like these are almost always a second scam. Nobody can reverse the transaction.

Scams that follow incidents like this one: Fake support, Recovery scam and Recovery-phrase phishing.

If your own wallet was drained: Wallet drained or hacked? What to do now.

traceme can't recover funds. We'll never message you first or ask for your recovery phrase.

Updates

  1. traceme read the chains again. On Nov 1 Affz…BEaU sent 503,850.52 SOL on: 485,277 SOL to Eze8…DrrD, which still holds it, and 18,573.52 SOL to 7SDu…Q2fK, which has sent SOL on to 35 wallets. The BTC and XRP still hadn’t moved, and the 505,617.74 ETH was still held on Ethereum. (Transaction 631P…gwGV, Transaction 66E4…6wkx, and 40 more in Sources)

  2. traceme read Solana again: Affz…BEaU held 970,554.16 SOL and had signed no transaction. (Address Affz…BEaU)

  3. The FBI said North Korea was responsible and asked services to block the addresses it lists. Its list names the addresses traceme counted: Affz…BEaU on Solana, the 19 holding the Bitcoin, and the six holding ETH on Ethereum. (FBI, Oct 31, 2026, Address Affz…BEaU, and 25 more in Sources)

  4. traceme read the chains again: the BTC, XRP and SOL still hadn’t moved, 505,617.74 ETH was still held on Ethereum, the 44,231,858.70 OP had moved on to 0x6b1b…4e3b, and Tether had frozen the 8,409,928.4 USDt on Avalanche. (bc1q0mtc…2mnm on mempool.space, bc1qnq6j…8t3s on mempool.space, and 28 more in Sources)

  5. Binance published Recovery Update #3: 90% of the losses replenished, a Proof of Reserves snapshot from 00:00 UTC, and withdrawals expected back on Nov 1. (Binance, Oct 31, 2026)

  6. Binance published Security Incident Update #2: more than $6.34B set aside, about 80% of the losses covered, and more points of breach found. (Binance, Oct 30, 2026)

  7. traceme counted Ethereum, Tron, Arbitrum, Avalanche, Optimism, Polygon and Base from the chain: Tether and Circle have frozen 1,759,184,053.21 USDT and 824,563,812.78 USDC, and 505,617.72 ETH is held on Ethereum, not frozen. (Tether’s freeze of 0x5227…2f8c: isBlackListed on Etherscan, Tether’s freeze of 0xaa24…54a0: isBlackListed on Etherscan, and 11 more in Sources)

  8. traceme counted the XRP Ledger part from the chain: 233,461,943.1 XRP in five payments to rK21…fzMx, which still holds them. (Transaction 78E3…FA6A on XRPSCAN, Transaction 6DDF…7E67 on XRPSCAN, and 4 more in Sources)

  9. traceme counted the Bitcoin part from the chain: 18,270.2 BTC, split into 19 addresses by 20:48 UTC on Oct 29 and not moved since. (Transaction f9dc…0313 on mempool.space, Transaction 48ba…e6a1 on mempool.space, and 28 more in Sources)

  10. Affz…BEaU still held the 970,521.9 SOL: its balance was 970,551.17 SOL, with small deposits from other addresses. (Address Affz…BEaU)

  11. Binance published its Security Incident Update: around $6.3B impact, about $3B frozen, and all losses covered. (Binance, Oct 30, 2026)

  12. The Arbitrum Security Council froze 8,425 ETH and 74,559,805.2 ARB on Arbitrum. (Arbitrum Security Council, Oct 30, 2026, Transaction 0xb69c…55d6 on Etherscan)

traceme describes what addresses did, never who controls them. For anything more, follow the sources.

Check a wallet

Is your own wallet involved? Paste its address or a transaction to see where its money went.