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, 2026Opens in a new tab, Binance, Oct 30, 2026Opens in a new tab, and 30 more in Sources)
Where it stands
- Withdrawals
- Paused; Binance expects them back on Nov 1
- (Binance, Oct 30, 2026Opens in a new tab, Binance, Oct 31, 2026Opens in a new tab)
- Not moved since Oct 29
- 18,270.2 BTC and 233.46M XRP
- (bc1q0mtc…2mnm on mempool.spaceOpens in a new tab, bc1qnq6j…8t3s on mempool.spaceOpens in a new tab, and 19 more in Sources)
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, 2026Opens in a new tab, FBI, Oct 31, 2026Opens in a new tab)
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, 2026Opens in a new tab, Binance, Oct 31, 2026Opens in a new tab)
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, 2026Opens in a new tab, Binance, Oct 31, 2026Opens in a new tab)
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, 2026Opens in a new tab, Transaction 0x53bd…e2f3 on EtherscanOpens in a new tab, 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, 2026Opens in a new tab, Tether’s freeze of 0x5227…2f8c: isBlackListed on EtherscanOpens in a new tab, 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 XRPSCANOpens in a new tab, 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 SolscanOpens in a new tab, 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, 2026Opens in a new tab, Binance, Oct 30, 2026Opens in a new tab)
Where the money is now
- the impact, by Binance’s estimate (Binance, Oct 30, 2026Opens in a new tab)
- Around $6.3B
- frozen on chain so far, by Binance’s count (Binance, Oct 30, 2026Opens in a new tab)
- About $3B
- frozen by Tether on Ethereum, Tron and Avalanche (Tether’s freeze of 0x5227…2f8c: isBlackListed on EtherscanOpens in a new tab, Tether’s freeze of 0xaa24…54a0: isBlackListed on EtherscanOpens in a new tab, and 4 more in Sources)
- 1.77B USDT
- frozen by Circle on Ethereum (Circle’s freeze of 0x5227…2f8c: isBlacklisted on EtherscanOpens in a new tab, Circle’s freeze of 0xc39e…9824: isBlacklisted on EtherscanOpens in a new tab)
- 824.56M USDC
- held on Ethereum, not frozen, including stablecoins sold for ETH before the freezes (0x8532…43d4 on EtherscanOpens in a new tab, 0xc887…286a on EtherscanOpens in a new tab, and 4 more in Sources)
- 505,617.74 ETH
- on Bitcoin, not moved since Oct 29 (bc1q0mtc…2mnm on mempool.spaceOpens in a new tab, bc1qnq6j…8t3s on mempool.spaceOpens in a new tab, and 18 more in Sources)
- 18,270.2 BTC
Solana
Traced by tracemeLast checked
What happened here
970,521.9 SOL left 5tzF…uAi9 in five transfers, between 20:10 and 20:33 UTC on Oct 29, 2026. (Transaction 5Yvw…Tqk2, Transaction 333s…v3Rc, and 3 more in Sources)
Where it is now
All of it went to Affz…BEaU, a new wallet: its first transaction is the first transfer. (Address Affz…BEaU, Transaction 5Yvw…Tqk2)
On Nov 1 at 04:19 UTC Affz…BEaU held 970,554.16 SOL: the 970,521.9 SOL, and small deposits from other addresses since. (Address Affz…BEaU)
Then it signed its first transactions. At 09:38 and 09:39 UTC it sent 485,277 SOL to Eze8…DrrD, a new wallet, which has sent nothing since. (Transaction 631P…gwGV, Transaction 66E4…6wkx, Address Eze8…DrrD)
Between 10:09 and 14:51 UTC it sent 18,573.52 SOL to 7SDu…Q2fK in ten transfers. By 16:14 7SDu…Q2fK, which also took in SOL from other wallets, had sent 17,351.5 SOL on to 35 wallets, 27 of them 500 SOL each. (Transaction 4i9j…9kaJ, Transaction 3joF…K557, and 9 more in Sources)
At 18:30 UTC Affz…BEaU held 466,703.66 SOL, Eze8…DrrD 485,277.01 SOL and 7SDu…Q2fK 4,473.33 SOL. (Address Affz…BEaU, Address Eze8…DrrD, Address 7SDu…Q2fK)
Tokens shown leaving Affz…BEaU’s token accounts were moved by those tokens’ own permanent delegates, not by the wallet. (Address Affz…BEaU, Transaction 2Yjf…KF3r)
The FBI’s list of addresses holding or that held funds from the theft names one on Solana: Affz…BEaU. (FBI, Oct 31, 2026Opens in a new tab, Address Affz…BEaU)
Open the trace Prices · Powered by JupiterOpens in a new tab
Ethereum
Linked to its explorerLast checked
What happened here
1,875,464,711.07 USDT, 823,000,000 USDC, 197,539.6 ETH and 62 other tokens left for 0x5227…2f8c in 13 transactions, between 20:24:23 and 21:44:11 UTC on Oct 29, 2026. (Transaction 0x53bd…e2f3 on EtherscanOpens in a new tab, Transaction 0x2c45…260b on EtherscanOpens in a new tab, and 11 more in Sources)
Where it is now
Tether has frozen 1,380,464,585.21 USDT: 1,175,464,712.88 at 0x5227…2f8c, 174,999,872.33 at 0xaa24…54a0 and 30,000,000.00 at 0xb171…c8c3. (Tether’s freeze of 0x5227…2f8c: isBlackListed on EtherscanOpens in a new tab, Tether’s freeze of 0xaa24…54a0: isBlackListed on EtherscanOpens in a new tab, Tether’s freeze of 0xb171…c8c3: isBlackListed on EtherscanOpens in a new tab)
Circle has frozen the 823,000,000 USDC at 0x5227…2f8c. (Circle’s freeze of 0x5227…2f8c: isBlacklisted on EtherscanOpens in a new tab)
Not frozen: 505,617.74 ETH is held in six addresses, none of which has sent anything. It includes stablecoins sold for ETH before the freezes. (0x8532…43d4 on EtherscanOpens in a new tab, 0xc887…286a on EtherscanOpens in a new tab, and 4 more in Sources)
The FBI’s list of addresses holding or that held funds from the theft names all six. (FBI, Oct 31, 2026Opens in a new tab, 0x8532…43d4 on EtherscanOpens in a new tab, and 5 more in Sources)
Where the 62 other tokens are now isn’t counted yet. (0x5227…2f8c on EtherscanOpens in a new tab)
Its addresses, live
- 0x5227…2f8cOpens in a new tabFrozen: 1,175,464,712.88 USDT by Tether, 823,000,000 USDC by Circle
- 0xaa24…54a0Opens in a new tabFrozen: 174,999,872.33 USDT by Tether
- 0xb171…c8c3Opens in a new tabFrozen: 30,000,000.00 USDT by Tether
- 0xc39e…9824Opens in a new tabFrozen: 1,563,812.78 USDC by Circle, from Avalanche
- 0x8532…43d4Opens in a new tab197,460.01 ETH, not frozen
- 0xc887…286aOpens in a new tab137,602.00 ETH, not frozen
- 0x897c…8df3Opens in a new tab78,415.25 ETH, not frozen
- 0x5440…c942Opens in a new tab40,600.67 ETH, not frozen
- 0x79e7…544aOpens in a new tab34,279.69 ETH, not frozen
- 0x03b0…20eaOpens in a new tab17,260.10 ETH, not frozen
Bitcoin
Linked to its explorerLast checked
What happened here
18,270.2 BTC left bc1qm34l…7s3h in 11 transactions in one block, at 20:20:06 UTC on Oct 29, 2026, all to bc1q0mtc…2mnm. (Transaction f9dc…0313 on mempool.spaceOpens in a new tab, Transaction 48ba…e6a1 on mempool.spaceOpens in a new tab, and 9 more in Sources)
Where it is now
By 20:48:14 UTC bc1q0mtc…2mnm had split it into 19 addresses: 17 of 1,000 BTC, one of 832.49990088 BTC and one of 437.69998739 BTC, 18,270.19988827 BTC in all after network fees. (Transaction 58bb…d625 on mempool.spaceOpens in a new tab, Transaction 27cd…f68b on mempool.spaceOpens in a new tab, and 17 more in Sources)
Nothing has left those 19 addresses since. (bc1q0mtc…2mnm on mempool.spaceOpens in a new tab, bc1qnq6j…8t3s on mempool.spaceOpens in a new tab, and 18 more in Sources)
The FBI’s list of addresses holding or that held funds from the theft names these 19, and no other Bitcoin address. (FBI, Oct 31, 2026Opens in a new tab, bc1qnq6j…8t3s on mempool.spaceOpens in a new tab, and 18 more in Sources)
Its addresses, live
- bc1qnq6j…8t3sOpens in a new tab1,000 BTC
- bc1q42fl…lsyxOpens in a new tab1,000 BTC
- bc1qm8v8…s2l8Opens in a new tab1,000 BTC
- bc1qs6xn…7w3vOpens in a new tab1,000 BTC
- bc1q63qr…sjxpOpens in a new tab1,000 BTC
- bc1qz8hd…updpOpens in a new tab1,000 BTC
- bc1qdfhm…88gwOpens in a new tab1,000 BTC
- bc1qjwdw…nz7wOpens in a new tab1,000 BTC
- bc1qm2j6…jaatOpens in a new tab1,000 BTC
- bc1qg3nr…3t53Opens in a new tab1,000 BTC
- bc1qepc7…4lagOpens in a new tab1,000 BTC
- bc1qs3ae…7s56Opens in a new tab1,000 BTC
- bc1qf5cy…a35uOpens in a new tab1,000 BTC
- bc1qalwn…tca8Opens in a new tab1,000 BTC
- bc1q2wvz…znn6Opens in a new tab1,000 BTC
- bc1q0ts8…mfv3Opens in a new tab1,000 BTC
- bc1qxrxu…968sOpens in a new tab1,000 BTC
- bc1qrg02…6zytOpens in a new tab832.49990088 BTC
- bc1qxg0l…s9raOpens in a new tab437.69998739 BTC
Tron
Linked to its explorerLast checked
What happened here
46,394,098 TRX left TDqS…hSCf for TG5i…zsGi at 20:20:00 and 20:21:12 UTC on Oct 29, 2026, then 612,729,468 USDT at 20:22:45. (Transaction 4203…253e on TronscanOpens in a new tab, TDqS…hSCf on TronscanOpens in a new tab, TG5i…zsGi on TronscanOpens in a new tab)
Where it is now
Tether has frozen 378,719,468 USDT: 312,729,468 at TG5i…zsGi and 65,990,000 at TCzB…7Y62. (Tether’s freeze of TG5i…zsGi: isBlackListed on TronscanOpens in a new tab, Tether’s freeze of TCzB…7Y62: isBlackListed on TronscanOpens in a new tab)
Before that, TG5i…zsGi sent 300,000,000 USDT on to TPBk…bKN4, which Tether froze later; 199,000,000 of it left through TSUU…vZpx. (Transaction fd80…6222 on TronscanOpens in a new tab, Transaction d40f…20ee on TronscanOpens in a new tab, and 2 more in Sources)
Not frozen: TRBd…PRki held 113,279,939.64 TRX on Oct 30, and was moving it on. (TRBd…PRki on TronscanOpens in a new tab)
Its addresses, live
- TG5i…zsGiOpens in a new tabFrozen: 312,729,468 USDT by Tether
- TCzB…7Y62Opens in a new tabFrozen: 65,990,000 USDT by Tether
- TPBk…bKN4Opens in a new tabReceived 300,000,000 USDT before its freeze
- TSUU…vZpxOpens in a new tab199,000,000 USDT left through it
- TRBd…PRkiOpens in a new tab113,279,939.64 TRX on Oct 30, moving
Avalanche
Linked to its explorerLast checked
What happened here
2,258,635.9 AVAX and 8,409,928.4 USDt left five wallets for 0x5227…2f8c in seven transfers, between 20:33:18 and 23:04:30 UTC on Oct 29, 2026. (Transaction 0x771c…6e9a on SnowtraceOpens in a new tab, Transaction 0x23a4…da28 on SnowtraceOpens in a new tab, and 5 more in Sources)
Where it is now
AVAX went on to 0x8035…c397. Part of it crossed to Ethereum through Circle’s CCTP, as USDC, and Circle has frozen the 1,563,812.78 USDC that arrived at 0xc39e…9824. (0x8035…c397 on SnowtraceOpens in a new tab, Circle’s freeze of 0xc39e…9824: isBlacklisted on EtherscanOpens in a new tab)
Tether has frozen the 8,409,928.4 USDt at 0x5227…2f8c. (Tether’s freeze of 0x5227…2f8c: isBlocked on SnowtraceOpens in a new tab)
Its addresses, live
- 0x5227…2f8cOpens in a new tabReceived 2,258,635.9 AVAX and 8,409,928.4 USDt; the USDt frozen by Tether
- 0x8035…c397Opens in a new tabAVAX went on here
XRP Ledger
Linked to its explorerLast checked
What happened here
233,461,943.1 XRP left five accounts in five payments between 20:05:00 and 20:09:20 UTC on Oct 29, 2026, all to rK21…fzMx. (Transaction 78E3…FA6A on XRPSCANOpens in a new tab, Transaction 6DDF…7E67 on XRPSCANOpens in a new tab, and 3 more in Sources)
Where it is now
rK21…fzMx still holds them, and has made no outgoing payment. (rK21…fzMx on XRPSCANOpens in a new tab)
Its addresses, live
- rK21…fzMxOpens in a new tabReceived all 233,461,943.1 XRP
Optimism
Linked to its explorerLast checked
What happened here
44,231,858.2 OP left 0xacd0…435a for 0x5227…2f8c in one transaction, at 20:18:23 UTC on Oct 29, 2026. (Transaction 0x10b5…33bf on Optimistic EtherscanOpens in a new tab)
Where it is now
It stayed at 0x5227…2f8c until Oct 31: at 00:12:15 UTC all 44,231,858.70 OP left in one transaction for 0x6b1b…4e3b, which still held it at 18:14 UTC. (Transaction 0x120a…bed7 on Optimistic EtherscanOpens in a new tab, 0x6b1b…4e3b on Optimistic EtherscanOpens in a new tab)
At 00:39 UTC a token whose name imitates OP’s showed a transfer of the same amount from an address that looks like 0x5227…2f8c to 0x6b1b…4e3b: a trick to get an address copied wrongly. Check every character of an address before you copy it. (Transaction 0x413e…dafc on Optimistic EtherscanOpens in a new tab)
Its addresses, live
- 0x6b1b…4e3bOpens in a new tab44,231,858.70 OP on Oct 31
- 0x5227…2f8cOpens in a new tabNone left on Oct 31
Arbitrum
Linked to its explorerLast checked
What happened here
8,426 ETH and 74,559,805.2 ARB left four wallets, among them 0xb38e…891d, and reached 0x3e2b…32d5. The transactions themselves aren’t counted yet. (0xb38e…891d on ArbiscanOpens in a new tab, 0x3e2b…32d5 on ArbiscanOpens in a new tab)
Where it is now
On Oct 30 at 00:08 UTC the Arbitrum Security Council froze 8,425 ETH and 74,559,805.2 ARB, moving them from 0x3e2b…32d5 to 0x0000…0DA0. Only an ArbitrumDAO governance vote can move them from there. (Arbitrum Security Council, Oct 30, 2026Opens in a new tab, Transaction 0xb69c…55d6 on EtherscanOpens in a new tab, 0x0000…0DA0 on ArbiscanOpens in a new tab)
Its addresses, live
- 0x0000…0DA0Opens in a new tab8,426.0477 ETH and 74,559,805.2 ARB on Oct 30
- 0x3e2b…32d5Opens in a new tab0.48 ETH left on Oct 30
Polygon
Linked to its explorerLast checked
What happened here
46,626,589.6 POL and 6,185,900.1 USDT0 left 0xe780…e245 for 0x5227…2f8c at 23:05:55 UTC on Oct 29, 2026. (Transaction 0x27f8…38c8 on PolygonScanOpens in a new tab, Transaction 0x8f5c…b25b on PolygonScanOpens in a new tab)
Where it is now
0x5227…2f8c still held the POL: 46,626,593.99 POL. (0x5227…2f8c on PolygonScanOpens in a new tab)
Where the USDT0 is now, and whether it is frozen, isn’t counted yet. (0x5227…2f8c on PolygonScanOpens in a new tab)
Its addresses, live
- 0x5227…2f8cOpens in a new tab46,626,593.99 POL on Oct 30
Base
Linked to its explorerLast checked
What happened here
4,735,627.3 VIRTUAL left 0x3304…566a for 0x5227…2f8c at 20:16:19 UTC on Oct 29, 2026. (0x3304…566a on BaseScanOpens in a new tab, 0x5227…2f8c on BaseScanOpens in a new tab)
Where it is now
It has moved on: 0x5227…2f8c held no VIRTUAL on Oct 30. Where it went isn’t counted yet. (0x5227…2f8c on BaseScanOpens in a new tab)
Its addresses, live
- 0x5227…2f8cOpens in a new tabReceived 4,735,627.3 VIRTUAL; none left on Oct 30
Timeline
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 XRPSCANOpens in a new tab, Transaction 6DDF…7E67 on XRPSCANOpens in a new tab, and 3 more in Sources)
965,455.1 SOL left 5tzF…uAi9 for Affz…BEaU, a wallet with no history before it. (Transaction 5Yvw…Tqk2, Address Affz…BEaU)
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)
On Base, 4,735,627.3 VIRTUAL left 0x3304…566a for 0x5227…2f8c. (0x3304…566a on BaseScanOpens in a new tab, 0x5227…2f8c on BaseScanOpens in a new tab)
On Optimism, 44,231,858.2 OP left 0xacd0…435a for 0x5227…2f8c. (Transaction 0x10b5…33bf on Optimistic EtherscanOpens in a new tab)
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 TronscanOpens in a new tab, TDqS…hSCf on TronscanOpens in a new tab, TG5i…zsGi on TronscanOpens in a new tab)
On Bitcoin, 11 transactions in one block sent 18,270.2 BTC to bc1q0mtc…2mnm. (Transaction f9dc…0313 on mempool.spaceOpens in a new tab, Transaction 48ba…e6a1 on mempool.spaceOpens in a new tab, and 9 more in Sources)
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 EtherscanOpens in a new tab, Transaction 0x2c45…260b on EtherscanOpens in a new tab, and 11 more in Sources)
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 SnowtraceOpens in a new tab, Transaction 0x23a4…da28 on SnowtraceOpens in a new tab, and 5 more in Sources)
bc1q0mtc…2mnm had split the Bitcoin into 19 addresses, 17 of them holding 1,000 BTC each. (Transaction 58bb…d625 on mempool.spaceOpens in a new tab, Transaction 27cd…f68b on mempool.spaceOpens in a new tab, and 17 more in Sources)
On Polygon, 46,626,589.6 POL and 6,185,900.1 USDT0 left 0xe780…e245 for 0x5227…2f8c. (Transaction 0x27f8…38c8 on PolygonScanOpens in a new tab, Transaction 0x8f5c…b25b on PolygonScanOpens in a new tab)
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, 2026Opens in a new tab, Transaction 0xb69c…55d6 on EtherscanOpens in a new tab)
Binance published its Security Incident Update. (Binance, Oct 30, 2026Opens in a new tab)
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, 2026Opens in a new tab)
On Optimism, the 44,231,858.70 OP left 0x5227…2f8c for 0x6b1b…4e3b. (Transaction 0x120a…bed7 on Optimistic EtherscanOpens in a new tab)
Binance published Recovery Update #3: 90% of the losses replenished, and a Proof of Reserves snapshot from 00:00 UTC. (Binance, Oct 31, 2026Opens in a new tab)
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, 2026Opens in a new tab, Address Affz…BEaU)
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)
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, 2026Opens in a new tab)
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, 2026Opens in a new tab)
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, 2026Opens in a new tab)
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, 2026Opens in a new tab)
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, 2026Opens in a new tab, Binance, Oct 30, 2026Opens in a new tab)
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, 2026Opens in a new tab)
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, 2026Opens in a new tab)
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, 2026Opens in a new tab)
What the chain shows
On five chains, Ethereum, Optimism, Polygon, Base and Avalanche, what left went to one address: 0x5227…2f8c. (0x5227…2f8c on EtherscanOpens in a new tab, 0x5227…2f8c on Optimistic EtherscanOpens in a new tab, and 3 more in Sources)
Read on chain on Oct 30 and 31, Tether’s USDT contracts list 1,767,593,981.61 USDT as frozen at six addresses on Ethereum, Tron and Avalanche, and Circle’s USDC contract 824,563,812.78 USDC at two on Ethereum. (Tether’s freeze of 0x5227…2f8c: isBlackListed on EtherscanOpens in a new tab, Tether’s freeze of 0xaa24…54a0: isBlackListed on EtherscanOpens in a new tab, and 6 more in Sources)
Solscan, a Solana explorer, labels 5tzF…uAi9 “Binance 2”. (5tzF…uAi9 on SolscanOpens in a new tab)
Affz…BEaU signed no transaction until Nov 1, when it sent 503,850.52 SOL on. The tokens shown leaving its token accounts were moved by each token’s permanent delegate, which can move that token from any account: each such transfer is signed by the delegate alone, as Gs5F…6YeX signed this one. (Transaction 2Yjf…KF3r, Address Affz…BEaU, and 12 more in Sources)
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, 2026Opens in a new tab)
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, 2026Opens in a new tab)
Sources
Statements
- Binance: “Security Incident Update”, Oct 30, 2026Opens in a new tab
- Binance: “Security Incident Update #2”, Oct 30, 2026Opens in a new tab
- Binance: “Security Incident | Recovery Update #3: 90% of Stolen Assets Replenished; Proof of Reserves Snapshot Provided”, Oct 31, 2026Opens in a new tab
- FBI: “North Korea Responsible for $6 Billion+ Binance Attack”, Oct 31, 2026Opens in a new tab
- Arbitrum Security Council: “Security Council Emergency Action – 30/10/2026”, Oct 30, 2026, 01:22 UTCOpens in a new tab
On the chain
Every transaction and address this page links (137)
- Transaction 0x53bd…e2f3 on EtherscanOpens in a new tab
- Transaction 0x2c45…260b on EtherscanOpens in a new tab
- Transaction 0x2e10…feb3 on EtherscanOpens in a new tab
- Transaction 0x9f21…ecf2 on EtherscanOpens in a new tab
- Transaction 0xa87c…5653 on EtherscanOpens in a new tab
- Transaction 0xb1f9…f295 on EtherscanOpens in a new tab
- Transaction 0xcb5b…ccfe on EtherscanOpens in a new tab
- Transaction 0xd4e0…c49c on EtherscanOpens in a new tab
- Transaction 0xe07f…2b52 on EtherscanOpens in a new tab
- Transaction 0xdc10…7481 on EtherscanOpens in a new tab
- Transaction 0x3b96…9ca7 on EtherscanOpens in a new tab
- Transaction 0x31c4…a91d on EtherscanOpens in a new tab
- Transaction 0x55ba…0556 on EtherscanOpens in a new tab
- Transaction f9dc…0313 on mempool.spaceOpens in a new tab
- Transaction 48ba…e6a1 on mempool.spaceOpens in a new tab
- Transaction d308…410d on mempool.spaceOpens in a new tab
- Transaction 5de2…f0ba on mempool.spaceOpens in a new tab
- Transaction 3b1d…2b32 on mempool.spaceOpens in a new tab
- Transaction 574b…190f on mempool.spaceOpens in a new tab
- Transaction 82c0…04ce on mempool.spaceOpens in a new tab
- Transaction d9bf…f651 on mempool.spaceOpens in a new tab
- Transaction 6722…cec0 on mempool.spaceOpens in a new tab
- Transaction 6736…ca84 on mempool.spaceOpens in a new tab
- Transaction 8b02…5cbf on mempool.spaceOpens in a new tab
- Transaction 5Yvw…Tqk2
- Transaction 333s…v3Rc
- Transaction aLao…fxhD
- Transaction 3w5U…NXap
- Transaction 2z7x…hkeC
- bc1q0mtc…2mnm on mempool.spaceOpens in a new tab
- bc1qnq6j…8t3s on mempool.spaceOpens in a new tab
- bc1q42fl…lsyx on mempool.spaceOpens in a new tab
- bc1qm8v8…s2l8 on mempool.spaceOpens in a new tab
- bc1qs6xn…7w3v on mempool.spaceOpens in a new tab
- bc1q63qr…sjxp on mempool.spaceOpens in a new tab
- bc1qz8hd…updp on mempool.spaceOpens in a new tab
- bc1qdfhm…88gw on mempool.spaceOpens in a new tab
- bc1qjwdw…nz7w on mempool.spaceOpens in a new tab
- bc1qm2j6…jaat on mempool.spaceOpens in a new tab
- bc1qg3nr…3t53 on mempool.spaceOpens in a new tab
- bc1qepc7…4lag on mempool.spaceOpens in a new tab
- bc1qs3ae…7s56 on mempool.spaceOpens in a new tab
- bc1qf5cy…a35u on mempool.spaceOpens in a new tab
- bc1qalwn…tca8 on mempool.spaceOpens in a new tab
- bc1q2wvz…znn6 on mempool.spaceOpens in a new tab
- bc1q0ts8…mfv3 on mempool.spaceOpens in a new tab
- bc1qxrxu…968s on mempool.spaceOpens in a new tab
- bc1qrg02…6zyt on mempool.spaceOpens in a new tab
- bc1qxg0l…s9ra on mempool.spaceOpens in a new tab
- rK21…fzMx on XRPSCANOpens in a new tab
- Transaction 4203…253e on TronscanOpens in a new tab
- Transaction 78E3…FA6A on XRPSCANOpens in a new tab
- Transaction 6DDF…7E67 on XRPSCANOpens in a new tab
- Transaction 9FE8…6AAA on XRPSCANOpens in a new tab
- Transaction 27C7…85F5 on XRPSCANOpens in a new tab
- Transaction 0571…5DB0 on XRPSCANOpens in a new tab
- 0x3e2b…32d5 on ArbiscanOpens in a new tab
- Tether’s freeze of 0x5227…2f8c: isBlackListed on EtherscanOpens in a new tab
- Tether’s freeze of 0xaa24…54a0: isBlackListed on EtherscanOpens in a new tab
- Tether’s freeze of 0xb171…c8c3: isBlackListed on EtherscanOpens in a new tab
- Tether’s freeze of TG5i…zsGi: isBlackListed on TronscanOpens in a new tab
- Tether’s freeze of TCzB…7Y62: isBlackListed on TronscanOpens in a new tab
- Tether’s freeze of 0x5227…2f8c: isBlocked on SnowtraceOpens in a new tab
- Circle’s freeze of 0x5227…2f8c: isBlacklisted on EtherscanOpens in a new tab
- Circle’s freeze of 0xc39e…9824: isBlacklisted on EtherscanOpens in a new tab
- Address Affz…BEaU
- Transaction 631P…gwGV
- Transaction 66E4…6wkx
- Transaction 4i9j…9kaJ
- Transaction 3joF…K557
- Transaction BEH3…ECnL
- Transaction 3qXG…R94f
- Transaction 5WqX…U7zK
- Transaction 3xqp…GRDs
- Transaction 63Zq…kdSH
- Transaction 3ZWC…1meA
- Transaction 5XjH…uVQM
- Transaction 4Wz6…erty
- Transaction 0x120a…bed7 on Optimistic EtherscanOpens in a new tab
- 0x8532…43d4 on EtherscanOpens in a new tab
- 0xc887…286a on EtherscanOpens in a new tab
- 0x897c…8df3 on EtherscanOpens in a new tab
- 0x5440…c942 on EtherscanOpens in a new tab
- 0x79e7…544a on EtherscanOpens in a new tab
- 0x03b0…20ea on EtherscanOpens in a new tab
- TSUU…vZpx on TronscanOpens in a new tab
- 0x5227…2f8c on BaseScanOpens in a new tab
- 5tzF…uAi9 on SolscanOpens in a new tab
- Address Eze8…DrrD
- Address 7SDu…Q2fK
- Transaction 2Yjf…KF3r
- 0x5227…2f8c on EtherscanOpens in a new tab
- Transaction 58bb…d625 on mempool.spaceOpens in a new tab
- Transaction 27cd…f68b on mempool.spaceOpens in a new tab
- Transaction b167…8922 on mempool.spaceOpens in a new tab
- Transaction 50a9…b109 on mempool.spaceOpens in a new tab
- Transaction 8fc8…adb3 on mempool.spaceOpens in a new tab
- Transaction 97e1…e71c on mempool.spaceOpens in a new tab
- Transaction d5b1…1f13 on mempool.spaceOpens in a new tab
- Transaction 2034…b0f5 on mempool.spaceOpens in a new tab
- Transaction 7c06…f6da on mempool.spaceOpens in a new tab
- Transaction 7954…6d70 on mempool.spaceOpens in a new tab
- Transaction f47b…f467 on mempool.spaceOpens in a new tab
- Transaction 38d6…a499 on mempool.spaceOpens in a new tab
- Transaction b27d…dbdd on mempool.spaceOpens in a new tab
- Transaction a9ed…c676 on mempool.spaceOpens in a new tab
- Transaction b147…ae00 on mempool.spaceOpens in a new tab
- Transaction fb59…2492 on mempool.spaceOpens in a new tab
- Transaction aa4e…65ec on mempool.spaceOpens in a new tab
- Transaction 046a…2687 on mempool.spaceOpens in a new tab
- Transaction 07f4…3eb6 on mempool.spaceOpens in a new tab
- TDqS…hSCf on TronscanOpens in a new tab
- TG5i…zsGi on TronscanOpens in a new tab
- Transaction fd80…6222 on TronscanOpens in a new tab
- Transaction d40f…20ee on TronscanOpens in a new tab
- Tether’s freeze of TPBk…bKN4: isBlackListed on TronscanOpens in a new tab
- TRBd…PRki on TronscanOpens in a new tab
- Transaction 0x771c…6e9a on SnowtraceOpens in a new tab
- Transaction 0x23a4…da28 on SnowtraceOpens in a new tab
- Transaction 0x2a3e…40f9 on SnowtraceOpens in a new tab
- Transaction 0x1b52…dcb2 on SnowtraceOpens in a new tab
- Transaction 0xe935…cd0a on SnowtraceOpens in a new tab
- Transaction 0x0d6f…dfae on SnowtraceOpens in a new tab
- Transaction 0x1673…4287 on SnowtraceOpens in a new tab
- 0x8035…c397 on SnowtraceOpens in a new tab
- Transaction 0x10b5…33bf on Optimistic EtherscanOpens in a new tab
- 0x6b1b…4e3b on Optimistic EtherscanOpens in a new tab
- Transaction 0x413e…dafc on Optimistic EtherscanOpens in a new tab
- 0xb38e…891d on ArbiscanOpens in a new tab
- Transaction 0xb69c…55d6 on EtherscanOpens in a new tab
- 0x0000…0DA0 on ArbiscanOpens in a new tab
- Transaction 0x27f8…38c8 on PolygonScanOpens in a new tab
- Transaction 0x8f5c…b25b on PolygonScanOpens in a new tab
- 0x5227…2f8c on PolygonScanOpens in a new tab
- 0x3304…566a on BaseScanOpens in a new tab
- 0x5227…2f8c on Optimistic EtherscanOpens in a new tab
- 0x5227…2f8c on SnowtraceOpens in a new tab
If you use Binance: what to do now
Rely only on Binance’s official channels, as Binance asks, and take questions to its Customer Support. (Binance, Oct 30, 2026Opens in a new tab)
If you hold funds on Binance, watch its announcements for when withdrawals reopen, and check its Proof of Reserves page once the full proof is out, expected by Nov 3. (Binance, Oct 31, 2026Opens in a new tab)
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 websiteOpens in a new tab · X accountOpens in a new tab
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
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)
traceme read Solana again: Affz…BEaU held 970,554.16 SOL and had signed no transaction. (Address Affz…BEaU)
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, 2026Opens in a new tab, Address Affz…BEaU, and 25 more in Sources)
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.spaceOpens in a new tab, bc1qnq6j…8t3s on mempool.spaceOpens in a new tab, and 28 more in Sources)
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, 2026Opens in a new tab)
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, 2026Opens in a new tab)
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 EtherscanOpens in a new tab, Tether’s freeze of 0xaa24…54a0: isBlackListed on EtherscanOpens in a new tab, and 11 more in Sources)
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 XRPSCANOpens in a new tab, Transaction 6DDF…7E67 on XRPSCANOpens in a new tab, and 4 more in Sources)
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.spaceOpens in a new tab, Transaction 48ba…e6a1 on mempool.spaceOpens in a new tab, and 28 more in Sources)
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)
Binance published its Security Incident Update: around $6.3B impact, about $3B frozen, and all losses covered. (Binance, Oct 30, 2026Opens in a new tab)
The Arbitrum Security Council froze 8,425 ETH and 74,559,805.2 ARB on Arbitrum. (Arbitrum Security Council, Oct 30, 2026Opens in a new tab, Transaction 0xb69c…55d6 on EtherscanOpens in a new tab)
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.