🔒 Investigation closed. This page is no longer updated. To follow the latest news, check Binance’s official X account: @binance.

Closed on Oct 30, 2026 · 09:20 ART (12:20 UTC)

← Back to home
Binance
🔒 Closed · Tracker ended

Binance hack — what we learned

Last updated (final): Oct 30, 2026 · 09:20 ART (12:20 UTC)
Contents
Quick facts
Status:🔒 Closed (Oct 30, 09:20 ART): this page is no longer updated. At closing, withdrawals were paused: Binance expected to resume them “within 48 hours” (01:36) and the 07:55 post gives no date. It says deposits “remain unaffected” and operate normally, although at 21:13 it had announced it was suspending deposits and withdrawals. No full post-mortem at closing. Binance Alpha suspended (20:06)
Coverage:Binance says it set aside more than US$6.34B of its own funds (US$5B already in the affected tokens) and began recovering assets for users (07:55). Official post; the amount cannot be verified on-chain until the next Proof of Reserves
Started:17:20 ART (UTC-3) — first public alert at 17:32
Verified chain:Ethereum (other chains: not verified)
Wallets:Binance 14, Binance 16 and “Binance: Hot Wallet 34”
How:Signatures made with Binance keys + EIP-7702. Binance says the incident may have started with a DevOps engineer’s compromised laptop (23:25); with no post-mortem, the root cause remains unconfirmed
Outflows:More than US$3.4B (verified floor, Ethereum only)
Frozen:~US$2.2B on Ethereum (~1,380M USDT by Tether + 823M USDC by Circle); plus 40.54M RLUSD, 27.82M USD1 and 48.5M WLFI. On Tron, ~378.7M USDT (link to the hack inferred from timing). Binance says ~US$3B in total (21:52; breakdown not verified). Arbitrum rescued ~US$30.5M on Arbitrum One
Not frozen:About 468k ETH in six attacker wallets, with no outgoing transactions at all (as of 05:34): 197,460 · 137,602 · 78,415 · 34,280 · 17,260 · 3,000. In addition, 0x5440…c942 holds 40,600 ETH, of which 7,647 came from 0xa97b…8d10 (the rest from untraced addresses)
Attribution:Chainalysis says it has “a high degree of confidence” that North Korea (DPRK) is responsible (01:31). That is its claim: the attribution has not been independently verified
🔒

Investigation closed on Oct 30, 2026 at 09:20 ART. The last data point added is Binance’s 07:55 announcement: it set aside more than US$6.34B of its own funds to cover the hack (US$5B already in the affected tokens), began recovering users’ assets and says US$3B is frozen verified: official post. This page is no longer updated: for news (post-mortem, withdrawals resuming, Proof of Reserves), follow the official @binance account.

This was a live tracker: the newest information is at the top, in the update log. All times are Argentina time (ART, UTC-3). Items marked verified were read directly from the blockchain; items marked not verified are an interpretation or third-party data we could not confirm.

1. Update log

Newest first.

Oct 30 · 09:20 ART
🔒 Investigation closed
  • We are closing the live tracker with Binance’s 07:55 announcement: the company publicly committed to covering all losses with its own funds and began recovering assets for users.
  • Still pending, and no longer going to be updated here: the full post-mortem, the date withdrawals resume, the post-incident Proof of Reserves, where the ~468k ETH held by the attacker ends up, and official confirmation of the attribution.
  • For updates, follow Binance’s official X account: @binance.
Oct 30 · 07:55 ART
Binance sets aside US$6.34B of its own funds to cover the hack and begins recovering users’ assets
  • @binance (07:55): Binance says it “has begun recovering affected assets for users” and that it keeps working with law enforcement, issuers, on-chain analytics firms and industry partners to trace, freeze and recover more funds. verified: official post
  • It set aside more than US$6.34B of company funds to cover the incident. Of that, US$5B is already held in the same tokens that were affected; the rest is being bought on the market and via OTC to replenish each token, which may take longer for low-liquidity tokens. verified: official post
  • Those figures do not include frozen funds: Binance repeats that US$3B is frozen and that it is working with partners and authorities to recover it. It says it will keep covering any confirmed shortfall with its own funds and that all user funds will be publicly verified through its Proof of Reserves. verified: official post
  • The reserved amount and its composition cannot be checked on-chain until Binance publishes its next Proof of Reserves. not verified The post gives no date for withdrawals to resume (the latest reference is still “within 48 hours”, from the 01:36 post) and does not publish the full post-mortem.
Oct 30 · 05:40 ART
Binance blames the incident on a DevOps engineer’s compromised laptop and expects to resume withdrawals within 48 hours; Chainalysis attributes the hack to North Korea; the attacker moves ETH to new addresses; Circle freezes 0xa97b
  • @binance (23:25): the initial investigation indicates the incident “may involve a compromised DevOps engineer’s laptop”, which gave the attacker access to a service container from which unauthorized withdrawal transactions were sent. The post continues with “We have found no evidence of any wallet private…” (the text we could read is cut off). verified: official post This is not the full post-mortem.
  • @binance (01:36): “Deposits remain unaffected and continue to operate as normal”. Withdrawals remain paused during a “security revamp” of the withdrawal service and its addresses, and Binance expects to resume them “within 48 hours”. Yi He (01:17) said the same. verified: official post Contradiction: at 21:13 Binance had said it was suspending deposits and withdrawals; now it says deposits were never affected.
  • Richard Teng (04:37): “your money is safe, and we’re covering every loss”, and he repeats the DevOps engineer’s laptop explanation. CZ (05:20): “The hack is more complex than that”. verified: official post There are still no SAFU amounts, no full post-mortem and no exact date for withdrawals to resume.
  • Unverified inference: the 50 EIP-7702 authorizations in the initial transaction were signed with Binance 14’s key. Binance saying it sees no evidence of stolen keys is consistent with the attacker having used Binance’s own signing system from that container, but the post-mortem is needed to confirm it. not verified
  • Attribution: Chainalysis (01:31) says it saw funds from last month’s Bitget hack mixed with funds stolen from Binance and has “a high degree of confidence that DPRK is responsible” (North Korea). verified: official Chainalysis post The attribution itself is not verified: it is Chainalysis’s claim, which we have not independently confirmed. Jony Levin (01:14) attributes it to the TraderTraitor group. ZachXBT (01:51) says funds from Binance and Bitget were pooled at the same address after arriving through THORChain (a cross-chain bridge) not verified: he did not give the address in the text we could read, and THORChain has not been seen in the Ethereum wallets being tracked.
  • Binance 14 still has no EIP-7702 delegation: its code is still empty (0x) at block 26,304,406 (05:33:59). Balance 0.80 ETH; the nonce kept rising (18,915,338). verified
  • 0x5227 sent 17,260 ETH to a new address, 0x03b0…20ea, at 02:15:47 (tx). That address has no outgoing transactions. Between 23:12 and 05:23 0x5227 made about 430 transactions, almost all to decentralized exchange routers (Uniswap SwapRouter02, Uniswap V2 and 0x1b81…eb14). It has 4.34 ETH left. verified
  • 0xa97b…8d10 sent 7,647 ETH to 0x5440…c942 at 03:36:11 (tx). Before that it made about 1,070 swap transactions on decentralized exchanges (Uniswap and SushiSwap). It has 0.37 ETH left. 0x5440 holds 40,600 ETH, with no outgoing transactions. verified Since 19:08 on Oct 29 it has received another ~33k ETH from addresses that were not traced (0xe702…958d and others); the link between those inflows and the hack is not verified.
  • 0x79e7 grew from 19,740 to 34,280 ETH: it received 11,560.8 ETH from 0xcf4c…23e0 (tx, 02:31), 2,856.9 ETH from 0xb3dd…5fdb (the one Circle froze in USDC; tx, 02:33) and small amounts from two others. Unchanged and with no outgoing transactions at all: 0x8532 197,460 ETH, 0xc887 137,602 ETH, 0x897c 78,415 ETH and 0xc209 3,000 ETH. In the Ethereum wallets being tracked there are no transfers to Tornado Cash, other mixers or bridges: everything goes to decentralized exchanges or to new addresses. verified
  • Circle blacklisted 0xa97b…8d10 for USDC at 01:11:35 (tx) and 0x8c1c…e58c at 01:19:23 (tx). verified The link between the latter and the hack is not verified. Tether added no addresses on Ethereum and PAXG has no freeze events between blocks 26,302,504 and 26,304,406. Tron was not checked in this round. Arbitrum, Tether and Paolo Ardoino posted nothing new on X.
  • Aave V3 (0x8d53): collateral US$59.94M, debt US$44.10M, health factor 1.060 (down from 1.076). Not liquidated. verified
  • Markets (CoinGecko, 05:36, 24h change): BTC US$77,967 (−2.5%), ETH US$2,226.5 (−3.8%), BNB US$706.0 (−6.1%).
Oct 29 · 23:15 ART
No major news: the attacker keeps swapping tokens for ETH on decentralized exchanges, with no mixers or bridges; Chainalysis repeats that ~US$3B is frozen
  • Chainalysis (23:02), quoting Binance’s post, mentions “~$3B frozen” and says its investigators are looking for “additional opportunities to disrupt”. It does not attribute the attack. verified: official post Since 22:48 there have been no new posts from @binance, CZ or Richard Teng; Yi He (23:10) only quoted a ZachXBT post about the Arbitrum rescue with an emoji. There is still no post-mortem, no SAFU amounts and no date for deposits and withdrawals to resume.
  • Binance 14 still has no EIP-7702 delegation: its code is still empty (0x) at block 26,302,503 (~23:13). Its nonce keeps rising (18,915,189) and it holds 0.81 ETH. verified
  • 0x5227 made more than 100 transactions between 22:48 and 23:11, almost all to decentralized exchange routers (Uniswap SwapRouter02, Uniswap V2 Router, SushiSwap and another router, 0x1b81…eb14, that was not identified). Its balance rose from 8,365 to 11,494 ETH and it sent no ETH to other addresses. 0xa97b…8d10 is doing the same: it went from 800.3 to 1,566.7 ETH, with no ETH sent to third parties. verified
  • Unchanged and with no outgoing transactions at ~23:13: 0x8532 197,460 ETH, 0x897c 78,415.25 ETH, 0x79e7 19,740 ETH and 0xc209 3,000 ETH. 0xc887 was not re-read in this check (last reading: 137,602 ETH at 22:48). No transfers to Tornado Cash, other mixers or bridges were seen. verified
  • Neither Tether (USDT) nor Circle (USDC) added addresses to their blacklists on Ethereum between 22:48 and ~23:13 (blocks 26,302,383 to 26,302,503). There were no new posts from Paxos, Arbitrum or Paolo Ardoino either. Tron and PAXG were not re-checked in this round. verified
  • Attribution: no firm or authority has publicly attributed the attack. The Lazarus/North Korea claims remain unverified.
  • Aave V3 (0x8d53): collateral US$59.93M, debt US$43.46M, health factor 1.076. Not liquidated. verified
  • Markets (CoinGecko, 23:11, 24h change): BTC US$76,640 (−4.1%), ETH US$2,192 (−4.9%), BNB US$704.4 (−5.5%).
Oct 29 · 22:50 ART
The attacker keeps swapping tokens for ETH and moves 3,000 ETH out of 0xa97b; Circle freezes 3 more addresses; Binance repeats it will cover everything, no post-mortem yet
  • @binance (22:36): repeats “Binance will cover all losses”; deposits and withdrawals remain suspended and it promises a full post-mortem. Yi He (22:23): “We are currently conducting a security scan… User funds SAFU”. verified: official post Richard Teng has posted nothing new since 21:22. No post-mortem, SAFU amounts or resumption date.
  • Binance 14 still has no EIP-7702 delegation: empty code (0x) at 22:48 (block 26,302,382), balance 0.82 ETH. Its nonce kept rising (18,915,163), so the key is still signing transactions. verified
  • 0xa97b…8d10 (the “pool” address of the attacker’s contract) started moving: at 22:17:47 it sent 3,000 ETH to a new address, 0xc209…850a (tx), which has not moved anything yet. Since 22:21 it has been approving and swapping tokens for ETH on decentralized exchanges (Uniswap, SushiSwap and others): about 70 transactions up to 22:48. Balance: 800.3 ETH. verified
  • 0x5227 sent 2,000 ETH to 0x8532 at 22:14:11 (tx). Between 21:53 and 22:48 it made 117 transactions, almost all token swaps on Uniswap and other decentralized exchanges. Balance at 22:48: 8,365 ETH. verified
  • Balances at 22:48, all with no outgoing transactions: 0x8532 197,460 ETH (+2,000), 0xc887 137,602 ETH, 0x897c 78,415 ETH, 0x79e7 19,740 ETH and 0xc209 3,000 ETH. In the addresses being tracked, no transfers to Tornado Cash, other mixers or bridges were seen: the destinations are decentralized exchange routers. verified
  • Circle blacklisted 3 more USDC addresses: 0xb3dd…5fdb at 22:06:47 (tx), the one that had received the 167 WBTC from 0x5227 and now holds 33,005 USDC and 1,775 ETH; 0xd02a…00c5 at 22:18:47, with 22,695 USDC (tx); and 0x4201…368a at 22:19:47, with 205,710 USDC (tx). verified The link between the last two and the hack is not verified.
  • No changes in the other freezes: Tether has added no addresses on Ethereum since 19:06 or on Tron since 21:38. PAXG still shows no freeze events. Arbitrum posted nothing new. verified
  • According to trackers: Lookonchain (22:01) says the attacker finished selling UNI, ENA, PEPE, LINK, AAVE, ONDO and WLD for 70,480 ETH; PeckShield (22:29) says 7.7 trillion PEPE were swapped for 14,049.9 ETH (matching the 14,040 ETH that reached 0x79e7) and the WBTC for 5,700 ETH; ZachXBT (22:01) says the total frozen exceeds US$2.83B. unverified
  • Attribution: no firm or authority has publicly attributed the attack. The Lazarus/North Korea claims circulating on X remain unverified.
  • Aave V3 (0x8d53): collateral US$59.93M, debt US$43.43M, health factor 1.077 (up from 1.068). Not liquidated. verified
  • Markets (CoinGecko, 22:49, 24h change): BTC US$76,786 (−4.1%), ETH US$2,196 (−5.2%), BNB US$697.5 (−6.7%).
Oct 29 · 22:00 ART
The revocation of Binance 14’s EIP-7702 delegation is identified (21:10); Binance raises the frozen total to ~US$3B
  • Binance 14’s EIP-7702 delegation (0x28C6…1d60) was revoked at 21:10:35 (block 26,301,896) with a type-4 transaction the wallet sent to itself, pointing the authorization to 0x0000…0000 (tx). That was ~14 minutes after the attacker’s last large sweep (2,961.9 ETH at 20:56). At 22:00 Binance 14’s code is still empty (0x). verified
  • @binance (21:52): the verified total frozen is “around US$3 billion” (previously US$2.54B), and it keeps working with law enforcement, issuers and intelligence firms. CZ retweeted it. verified: official post The breakdown is not verified. There is still no announcement on when deposits and withdrawals will resume, and no post-mortem.
  • 0x600d…8298 (the wallet that received the PEPE) sent 14,040 ETH to a new address, 0x79e7…544a, at 21:35:47 (tx). That address has no outgoing transactions and holds 19,740 ETH at 22:00. verified
  • The balance of 0xc887…286a rose from 122,310 to 137,602 ETH (+15,292). verified Where it came from is not verified: Etherscan does not show the incoming transaction yet. Unchanged: 0x8532 (195,460 ETH), 0x897c (78,415 ETH) and 0xa97b…8d10 (3,090.4 ETH), all with no outflows. No mixers or bridges seen. verified
  • Aave V3 (0x8d53): collateral US$59.93M, debt US$43.78M, health factor 1.068 (down from 1.073). verified
  • Still no public attribution from ZachXBT, Chainalysis, TRM, Elliptic or the FBI. PAXG: no freeze event seen yet. not verified
  • Market (CoinGecko, 22:00, 24h change): BTC US$77,131 (−4.8%), ETH US$2,217 (−5.7%), BNB US$693.7 (−8.2%).
Oct 29 · 21:50 ART
Binance promises to cover all losses and suspends deposits and withdrawals; Binance 14 no longer has the EIP-7702 delegation; Arbitrum rescues ~US$30.5M
  • @binance (21:13): “Binance will cover all losses. As a precaution, all deposits and withdrawals are temporarily suspended while our team conducts security checks, freezes funds, and works with law enforcement.” CZ retweeted it (21:45). verified: official post
  • Yi He (21:04): “Binance will cover all hacking losses… We will share a full post-mortem once the investigation is complete.” No post-mortem or SAFU amounts yet. verified: Yi He post
  • Richard Teng (21:22): “user funds remain SAFE”, with no figures. verified: Richard Teng post
  • At ~21:51 (block 26,302,098), Binance 14’s code is empty (0x): the EIP-7702 delegation to the attacker’s contract is no longer active. Between 21:30 and 21:48, Binance 14’s key kept sending tokens to “Binance: Cold Wallet 20” (0xf977…aceC): 17 successful transfers and 11 failed. verified
  • Binance 14 sweeps: the 4 at 20:36–20:38 took nothing (~23,100 gas and no transfers, e.g.). The one at 20:56:47 did: 2,961.91 ETH to 0xa97b…8d10 (tx), the “pool” address of the attacker’s contract, which holds 3,090.4 ETH and has no outflows. verified Unverified inference: these were user deposits that piled up before the suspension.
  • Arbitrum (21:19): its Security Council rescued 74,559,805 ARB and 8,425 ETH (~US$30.5M according to ZachXBT) from 0x3E2b…32d5 on Arbitrum One and moved them to a frozen intermediary wallet. verified: official Arbitrum post That address now holds ~0.002 ETH on Arbitrum, consistent with the rescue. verified
  • The attacker’s large ETH wallets still have no outflows: 0x8532 195,460 ETH, 0xc887 122,310 ETH and 0x897c 78,415.25 ETH. No mixers, bridges or THORChain seen on Ethereum. verified
  • 0x5227 keeps moving tokens out: 87.9M ZAMA (21:08), 3.6M ZRO (21:30), 3,382M RSR (21:32), 0.91M PROM (21:40) and 1.76M MORPHO (21:43, tx). verified
  • PAXG: 0x5227 received 1,906.67 PAXG from Binance 14 (17:44 and 18:24) and has not moved it. verified The freeze is not verified: Paxos said it confirmed the movement (19:56), but no freeze events were found on the PAXG contract.
  • Aave V3 (0x8d53): collateral US$59.93M, debt US$43.55M (previously 44.9M), health factor 1.073. Not liquidated. verified
  • Tron: Tether blacklisted 9 more USDT-TRC20 addresses at 21:26 and 21:38, with only ~0.39M USDT in total. verified on-chain The link to the hack is not verified.
  • Elliptic (20:39) has labeled the hack addresses. According to Wu Blockchain, citing Arkham, the “binance-hacker-1029” entity groups 66 addresses holding ~US$5.88B. not verified As of 21:50, no firm (ZachXBT, Chainalysis, Elliptic, TRM) and not the FBI had publicly attributed the attack; any mention of Lazarus/North Korea is not verified.
  • Market (CoinGecko, ~21:50, 24h change): BTC US$76,849 (−5.2%), ETH US$2,210 (−6.1%), BNB US$690 (−8.8%). A further drop since 20:40.
Oct 29 · 20:42 ART
Binance says US$2.54B is frozen and suspends Binance Alpha; it moves ETH to a cold wallet; the attacker sweeps Binance 14 again
  • @binance (20:22): “the current verified total frozen is $2.54 billion”, adding that the figure may rise because it is working with law enforcement, issuers and analytics firms. verified: official post Our own on-chain verified total is lower (~US$2.2B on Ethereum + ~US$379M on Tron); Binance’s breakdown is not verified.
  • @binance (20:06): temporarily suspended Binance Alpha trading (purchases with spot funds) “until the security issue is resolved”. Withdrawals remain halted. Still no post-mortem, no formal confirmation of the hack and no SAFU amounts. verified: official post
  • Paxos (19:56): confirmed through its own analysis that PAXG tokens from Binance went to the attacker’s address. verified: Paxos post The amount frozen is not verified.
  • At 20:00:23 the Binance 15, 16, 17, 18 and 20 hot wallets sent ~79,375 ETH (17,683 + 849 + 23,582 + 14,685 + 22,578) to 0xf977…aceC, labeled “Binance: Cold Wallet 20” (Etherscan). verified Unverified inference: Binance is moving ETH out of its hot wallets as a precaution.
  • There were 4 new sweep() calls on Binance 14 from 0x7c86, between 20:36:47 and 20:38:23. The EIP-7702 delegation is still active. What they took could not be seen (Etherscan returned no token transfers). verified
  • Tokens keep leaving 0x5227: 17.3M WLD (20:21), 58.4M SAND (20:27, tx) and 714.9M FUN (20:28). 0x42cd sent another 2,939.48 ETH to 0x897c (20:24:47, tx), which now holds ~78,415 ETH with no outgoing transactions. verified It is receiving many tiny (“dust”) transfers from 0xcb02…, likely address poisoning. not verified
  • 0x8532 (195,460 ETH) and 0xc887 (122,310 ETH) are still untouched. No mixers, bridges or THORChain seen. The Aave position was not re-read in this check. verified
  • Attribution: no top-tier firm has attributed the attack. Totals circulating: “US$5.7B” based on Arkham data (shared by SolanaFloor) and “more than US$5.8B” according to Lookonchain (20:27). not verified
  • Market (CoinGecko, ~20:40, 24h change): BTC US$78,530 (−3.3%), ETH US$2,260 (−4.1%), BNB US$704 (−7.1%).
Oct 29 · 20:15 ART
Binance uses its own key to pull what was left in Binance 14; the attacker gathers 75.5k ETH at 0x897c
  • Between 19:55 and 20:07, Binance 14 signed 46 token transfers to 0xf977…aceC (example). Two failed (USDT and WLFI) because Binance 14 is blacklisted on those tokens. The EIP-7702 delegation is still active. verified 0xf977…aceC is labeled on Etherscan as “Binance: Cold Wallet 20” (Etherscan). verified: public Etherscan label Unverified inference: Binance is rescuing the remaining balance.
  • 0x42cd sent ~17,584 ETH to 0x897c (~19:51), which ended up with 75,476 ETH. 0x8532 (195,460 ETH) and 0xc887 (122,310 ETH) are still untouched. No movements to mixers or bridges. verified
  • Tokens keep leaving 0x5227: 21.85M ONDO (19:53), 9.71M USDe (19:56) and 8.41M SNX (20:03, tx). verified
  • No new posts from Binance, CZ, Yi He or Richard Teng since 19:46: no post-mortem, no SAFU amounts and no resumption of withdrawals. No attribution. BWEnews (20:04) reports US$6.26B across 9 chains. not verified
  • Market (CoinGecko, ~20:15, 24h change): BTC US$78,665 (−3.2%), ETH US$2,264 (−4.0%), BNB US$703 (−7.1%).
Oct 29 · 19:50 ART
Withdrawals halted over a “security issue”, a third drain of Binance 14, and more freezes verified
  • @binance (19:15:55): “Withdrawals will resume as soon as the security issue is fully resolved. User funds remain safe.” It reposted the notice at 19:33. Binance no longer talks about a “technical error” but a “security issue” — still without using the word “hack”. No post-mortem and no SAFU amounts yet. verified: official post
  • CZ (19:23): quoted 0xngmi (net loss of ~US$1B) and wrote “Loss might be a bit higher than that, but will cover”. It is the first explicit promise of coverage, but it comes from CZ, not from a formal Binance announcement. verified: CZ post
  • Third drain of Binance 14 (19:39:35): the attacker called sweep() again and took the ~128.5 ETH that had piled up (tx). The EIP-7702 delegation is still active. verified
  • Transactions signed with the Binance 14 key: at 19:15:35 a transfer of 18,341.4 USDT to 0xfa19…1e24 that failed because the wallet is on Tether’s blacklist (tx), and at 19:27:35 a move of 20,587.5 USDC from Hot Wallet 34 to 0x172c…a439 (tx). verified Who initiated them is not verified — they may be queued Binance withdrawals.
  • New freezes on Ethereum: 40.54M RLUSD (Ripple paused 0xe702…958d at 19:00:59 and Binance 14 at 19:20:47), 27.82M USD1 at 0x5227 (19:10:35, confirmed by Zach Witkoff / USD1) and 48.5M WLFI at 0x5227 (at 17:57:47, before Tether; Binance 14 at 19:22:47; reported by @worldlibertyfi at 19:17, working with BitGo). verified The “~200M” Yi He attributed to Ripple could not be verified on-chain. not verified Unverified inference: of the 88.54M RLUSD stolen, ~48M may have been sold before the freeze.
  • Tron: Tether blacklisted 3 USDT-TRC20 addresses between 18:09 and 18:21, freezing ~378.7M USDT (TG5iBM…zsGi 312.7M, tx; TCzBTk…Y62 66.0M, tx; TPBkSj…KN4 with a zero balance). verified on-chain The link to Binance is based on timing and on Ardoino’s figure. link not verified Unverified inference: ~1,180M on Ethereum (as of 18:25) + 378.7M on Tron ≈ 1,559M, which matches Ardoino’s “more than 1,567M”.
  • The attacker keeps moving tokens out of 0x5227: 2.57M LINK to 0xcf4c…23e0 (19:34:59), 127,953 AAVE to 0xe702 (19:37:11) and 167.14 WBTC to 0xb3dd…5fdb (19:41:35, tx). The wallets that received UNI and PEPE now hold 17,584 ETH and 1,903 ETH. verified Unverified inference: the tokens are being sold for ETH.
  • The three big ETH balances are still untouched (195,460, 122,310 and 57,892 ETH; monitored until 19:48). No mixers, bridges or THORChain seen. Aave V3 (0x8d53): health factor 1.042, debt US$44.9M. verified
  • Firms and trackers, none attributing the attack: Chainalysis (19:15) is investigating and tracking funds on Bitcoin, Ethereum, Tron and L2s; Arkham (19:47) created a tracking entity (“$5B”); Lookonchain (19:21) says “over US$5.8B hacked; 1,580M USDT + 823M USDC frozen”. not verified: includes other chains
  • Market (CoinGecko, 19:48, 24h change): BTC US$78,855 (−3.0%), ETH US$2,272 (−3.8%), BNB US$702 (−7.3%).
Oct 29 · 19:24 ART
Binance suspends withdrawals until the security issue is resolved
  • @binance (19:15:55): “Our team is conducting security checks. Withdrawals will resume as soon as the security issue is fully resolved. User funds remain safe.” It is the first time the official account makes clear that withdrawals are halted and ties it to a security problem (at 18:48 it had spoken of a “technical error”). verified: official post
  • Yi He, co-founder (19:22): “withdrawals are currently disabled until the environment is confirmed to be secure… User funds are SAFU”. verified: Yi He post
  • Yi He also thanked other issuers for freezes: Ripple, “approximately 200 million” (19:08), and World Liberty Financial, 27M USD1 and 48M WLFI (~US$2M) (19:22). The posts are verified; the on-chain freezes were not at that point. freeze not verified on-chain Unverified inference: the Ripple figure would be the RLUSD that left Binance (88.5M already traced to 0x5c23…a4fc).
  • The attacker’s three big ETH balances are still untouched (19:09–19:21): 195,460, 122,310 and 57,892 ETH. The EIP-7702 delegation on Binance 14 is still active; Binance 14 sent a transaction of its own around 19:19 (contents not yet reviewed) and holds ~129.5 ETH. verified
  • Still no post-mortem, no SAFU coverage amounts and no attribution from any top-tier security firm.
Oct 29 · 19:08 ART
Tether blacklists Binance 14 itself; the attacker sells tokens; the big ETH stays put
  • At 19:06:23 Tether added Binance 14 itself to the USDT blacklist (tx), freezing ~1.35M USDT that had built up after the second drain. verified Unverified inference: the goal would be to stop the attacker from taking more USDT from that wallet, which is still “hijacked” by its contract. Binance 14 has already collected another ~129 ETH in deposits.
  • Tokens that can’t be frozen left 0x5227 for new wallets: 7.77 trillion PEPE to 0x600d…8298 (18:49:11, tx), 29,934 wBETH to 0x7f9d…15e3 (18:52:47, tx) and 217.5M ENA to 0x7f9d…15e3 (19:02:11, tx). verified
  • Whale Alert values them at US$37.5M (PEPE), US$46.8M (UNI) and US$40.4M (ENA) (PEPE, ENA). valuation not verified The wallets that received UNI (0x42cd…7810, ~5,973 ETH) and PEPE (0x600d, ~213 ETH) already hold ETH. Unverified inference: they are selling those tokens for ETH.
  • The three big ETH balances haven’t moved (checked every 60 s, 18:50–19:07): 195,460 ETH at 0x8532, 122,310 at 0xc887 and 57,892 at 0x897c. No mixers, bridges or THORChain seen. verified
  • Aave V3 (0x8d53): collateral US$59.9M, debt US$44.6M, health factor 1.047. Not liquidated. verified
  • Binance.US (18:41): says it is not affected because it is a separate platform (CZ shared it). Jeremy Allaire, Circle CEO (18:18): Circle froze “more than 800M USDC… in coordination with law enforcement”. @BinanceHelpDesk is replying with a standard message (“investigating… user funds are completely safe”, e.g.).
  • Whale Alert (18:45) reports US$2.37B in USDT + USDC frozen; on Ethereum ~US$2.2B can be verified. not verified
  • Market (CoinGecko, 19:07, 24h change): BTC US$78,778 (−3.0%), ETH US$2,259 (−4.1%), BNB US$703 (−6.9%).
Oct 29 · 18:50 ART
Binance acknowledges withdrawal problems and Binance 14 is drained a second time
  • @binance (18:48:31): “withdrawal issues some users are experiencing due to a technical error… working to restore withdrawals… funds are SAFU”. In other words: crypto withdrawals are having problems and Binance blames a “technical error”.
  • @binance (18:29): added “User funds are completely safe” to its statement. Still no confirmation of the hack and no post-mortem.
  • Second drain (18:44:11): the EIP-7702 delegation on Binance 14 was never revoked. The attacker called sweep() again and took what had accumulated: 369.83 ETH + 200.40M USDT + 7,008 UNI, LINK, PEPE, SHIB and others (tx). The USDT landed in 0x5227, which is already blacklisted, so it stays frozen (balance: 1,175.46M USDT). The ETH does not.
  • The attacker is moving ETH to fresh wallets (no mixers or bridges so far): 122,310 ETH from 0x9749292d to 0xc887af69…286a (18:47:47); a “peel chain” 0x8d53 → 0x77ed → 0x7aa4 → 0xccbe → 0xb171 ending with 57,891.77 ETH at 0x897c80d1…8df3 (18:35:59); and 7.02M UNI from 0x5227 to 0x42cd…7810 (18:46:59). The 195,460 ETH at 0x8532 are still untouched.
  • Aave V3 (read on-chain): 0x8d53 has US$59.93M of collateral and US$45.09M of debt (health factor 1.037).
  • USDT frozen and verifiable on Ethereum: ~1,380M (0x5227 1,175.5M + 0xaa24 175.0M + 0xb171 30M). Ardoino says more than 1,567M and BWEnews 1,493M; the gap could be on Tron, but it could not be verified at that point. not verified
  • BWEnews (18:31) estimates total outflows of US$5,643M (ETH 3,528M, BTC 1,449M, Tron 628M, L2s 38M). Not validated outside Ethereum. not verified
  • Market (CoinGecko, 18:48, 24h change): BTC US$79,110 (−2.6%), ETH US$2,272 (−3.8%), BNB US$707 (−6.6%).
Oct 29 · 18:28 ART
Binance speaks (without confirming a hack) and Tether freezes more addresses
  • @binance (18:15): says it is “investigating reports of a potential security issue”. It does not confirm a hack. In the 18:24 edit, the line “we have not confirmed any impact to user funds” disappeared.
  • CZ (18:15): “User funds are safe! It does look like a hack… I expect all user funds will be fully covered”. He notes he no longer runs Binance.
  • Yi He, co-founder (18:17): “User Funds SAFU”.
  • PeckShield (18:22): “Confirmed hack”. It does not say who did it.
  • Paolo Ardoino, Tether CEO (18:25): Tether froze “more than 1,567M USDT”.
  • On-chain: Tether blacklisted 4 more addresses between 18:12 and 18:19 (0x7aa4…bfd1, 0xaa24…54a0 with 175.0M USDT, 0xccbe…a263 and 0xb171…c8c3 with 30M USDT and 57,892 ETH that can’t be frozen). USDT frozen and verifiable on Ethereum at that point: ~1,180M.
  • The main receiver (0x5227) sent 88.54M RLUSD to 0x5c23…a4fc at 18:22:59 (tx).
  • The 195,460 ETH at 0x8532 and the 122,313 ETH at 0x9749292d had not moved (checked every 60 seconds between 18:14 and 18:27).
  • Binance 14 is still “hijacked” by the attacker’s contract but keeps receiving deposit sweeps (~52 ETH). At 18:24:23 it signed a batch from Hot Wallet 34 with 3 small USDC transfers (tx). Unverified inference: these could be normal user withdrawals.
  • Market (CoinGecko, 18:27, 24h change): BTC US$79,374 (−2.3%), ETH US$2,284 (−3.4%), BNB US$710.7 (−6.1%).
Oct 29 · 18:10 ART
Tether and Circle freeze stablecoins
  • Tether froze ~975M USDT across 4 addresses (18:01–18:03) and Circle froze 823M USDC (18:04:59). Both verified on-chain.
  • Transfer events confirm the 823M USDC came out of “Binance: Hot Wallet 34”.
  • Money trail: ~122k ETH obtained by selling USDT, 60M USDT deposited in Aave, and 175M + 130M USDT that left before the freeze.
  • Binance had still said nothing.
Oct 29 · 18:05 ART
First report
  • Very likely hack of the Binance 14 wallet via EIP-7702, with outflows above US$2.5B. No statement from Binance.

2. What happened, in plain terms

Exchanges like Binance keep part of their users’ money in “hot wallets”: online wallets they use every day to move funds and process withdrawals. Binance’s largest one on Ethereum is called “Binance 14”.

On October 29 at 17:20 (Argentina time), a wallet funded through Tornado Cash (a “mixer” used to hide where money comes from) sent a transaction carrying 50 authorizations signed with Binance 14’s key. With that, the Binance wallet started obeying a contract controlled by the attacker. Four minutes later, at 17:24, it was emptied in a single transaction.

Funds then also left Binance 16 (through regular transfers signed with its own key), along with USDC from “Binance: Hot Wallet 34”, which passed through Binance 14.

3. How the attack worked

This was not a bug in a Binance program (smart contract). It was something more serious: someone managed to get Binance’s keys to sign what they wanted. This is the path:

TORNADO CASH 0.1 ETH pool
→3 deposits of ~0.098 ETH (Oct 27/28)
ATTACKER 0x7c86…5ca0
→EIP-7702 tx with 50 authorizations (17:20)
BINANCE 14 now obeys contract 0x63e8…6fae
→sweep() empties it (17:24)
RECEIVER 0x5227…2f8c

What is EIP-7702 and why does it matter?

4. On-chain timeline (hour by hour)

All times in ART (UTC-3). Each row links to the transaction or wallet on Etherscan.

Time (ART)What happenedSource
Oct 27/28The attacker’s wallet 0x7c86…5ca0 receives 3 deposits of ~0.098 ETH from Tornado Cash’s 0.1 ETH pool (0x12d6…b8fc).Etherscan
Oct 29, morningThe attacker deploys the “sweeper” contracts 0x19be…f2bf and 0x63e8…6fae, with their own address hard-coded as owner, and tests them with other addresses.Etherscan
17:20:59EIP-7702 transaction to Binance 14 with 50 authorizations pointing to 0x63e8…6fae.tx
17:24:23Binance 14 is emptied into 0x5227…2f8c: 167,464 ETH + 1,615M USDT + ~63 tokens.tx
17:24:47Binance 16 sends 28,005.6 ETH and 55.74M USDT to 0x5227.ETH · USDT
17:29–17:330x5227 sends 500M USDT to 0x9749292d…c762 and 200M USDT to 0x0ddf0480…697e. At the same time, look-alike fake addresses appear (“address poisoning”).500M · 200M
17:32First public alert (Spreek).X
17:34–17:500x9749292d swaps USDT for ETH and receives ~122,316 ETH.Etherscan
17:38:470x5227 forwards 195,460 ETH to 0x8532…43d4.tx
17:39Tree News: “POTENTIAL BINANCE HACK ONGOING”.X
17:41:23780M USDC from Hot Wallet 34 go to 0x5227 (via Binance 14).tx
17:47:470x0ddf makes a large swap of USDT/USDC/DAI/WBTC into WETH.tx
17:53–17:540x0ddf sends 190M USDT + 3,552 ETH to 0x8d53…639a.USDT · ETH
17:57–18:010x8d53 deposits 10M + 50M USDT into Aave V3 and interacts with 0xd016…5722 (possibly borrowing ETH against that USDT, not verified).deposit 1 · deposit 2
17:57:47World Liberty blacklists 0x5227 (48.5M WLFI frozen), before Tether.X
17:59:110x9749292d sends 175M USDT to 0x811f…e84c (before the freeze).tx
17:59:47Another 43M USDC from Hot Wallet 34 go to 0x5227 (USDC total: 823M).tx
18:01:35Tether blacklists 0x5227 and 0x9749292d.tx 1 · tx 2
18:01:47Tether blacklists 0x0ddf0480.tx
18:02:350x8d53 sends 130M USDT and 23,314.5 ETH to 0x77ed…c3eb, which has already forwarded everything.USDT · ETH
18:02:47Tether blacklists 0x8d53…639a.tx
18:04:59Circle blacklists 0x5227: 823M USDC frozen.tx
18:05Tree News: “Tether freezes $971M USDT… no update from Binance”.X
18:09–18:21On Tron, Tether blacklists 3 USDT-TRC20 addresses (~378.7M USDT). Link to the hack inferred from timing.Tronscan
18:12–18:19Tether blacklists 4 more addresses (details in the update log).last tx
18:15Binance’s first statement: “investigating a potential security issue”.X
18:29Binance adds “User funds are completely safe” to its statement.X
18:35:59End of a hop chain (0x8d53 → 0x77ed → 0x7aa4 → 0xccbe → 0xb171): 57,891.77 ETH land at 0x897c80d1…8df3.tx
18:41Binance.US says it is not affected (separate platform).X
18:44:11Second drain of Binance 14 (the EIP-7702 authorization was still active): 369.83 ETH + 200.40M USDT + other tokens. The USDT stays frozen in 0x5227.tx
18:46:590x5227 sends 7.02M UNI to 0x42cd…7810.tx
18:47:470x9749292d sends 122,310 ETH to 0xc887af69…286a.tx
18:48:31Binance acknowledges withdrawal problems “due to a technical error” and says it is working to restore them.X
18:49:110x5227 sends 7.77 trillion PEPE to 0x600d…8298.tx
18:52:470x5227 sends 29,934 wBETH to 0x7f9d…15e3.tx
19:00:59Ripple pauses 0xe702…958d: 40.54M RLUSD immobilized.—
19:02:110x5227 sends 217.5M ENA to 0x7f9d…15e3.tx
19:06:23Tether blacklists Binance 14 itself (~1.35M USDT frozen).tx
19:08Yi He thanks Ripple for freezing “approximately 200 million”.X
19:10:350x5227 frozen in USD1 (27.82M USD1).X
19:15:35Binance 14 tries to send 18,341.4 USDT to 0xfa19…1e24; it fails because of the blacklist.tx
19:15:55Binance: withdrawals will resume once the security issue is resolved.X
19:22Yi He: withdrawals “disabled” until the environment is confirmed to be secure; World Liberty froze 27M USD1 and 48M WLFI.X
19:23CZ: “Loss might be a bit higher than that, but will cover”.X
19:27:35Binance 14 moves 20,587.5 USDC from Hot Wallet 34 to 0x172c…a439 (origin not verified).tx
19:34–19:410x5227 moves 2.57M LINK, 127,953 AAVE and 167.14 WBTC to new wallets.WBTC
19:39:35Third drain of Binance 14: ~128.5 ETH.tx
~19:510x42cd (the wallet that received the UNI) sends ~17,584 ETH to 0x897c, which ends up with 75,476 ETH.—
19:55–20:07Binance 14 signs 46 token transfers to 0xf977…aceC (“Binance: Cold Wallet 20”). Two fail (USDT and WLFI) because of the blacklist.example
19:56Paxos confirms PAXG tokens from Binance went to the attacker’s address.X
20:00:23The Binance 15, 16, 17, 18 and 20 hot wallets send ~79,375 ETH to “Binance: Cold Wallet 20”.Etherscan
20:06Binance temporarily suspends Binance Alpha trading.X
20:22Binance: “the current verified total frozen is $2.54 billion”.X
20:24:470x42cd sends another 2,939.48 ETH to 0x897c (~78,415 ETH in total, no outflows).tx
20:36:47–20:38:234 new sweep() calls on Binance 14 from 0x7c86; they took nothing.e.g.
20:56:47Fourth drain of Binance 14: 2,961.91 ETH to 0xa97b…8d10, the “pool” address of the attacker’s contract.tx
21:04Yi He: “Binance will cover all hacking losses… We will share a full post-mortem”.X
21:10:35Binance 14 revokes the EIP-7702 delegation with a type-4 transaction to itself.tx
21:13Binance: “will cover all losses” and temporarily suspends deposits and withdrawals.X
21:19Arbitrum’s Security Council rescues 74.56M ARB and 8,425 ETH (~US$30.5M) on Arbitrum One.X
21:35:470x600d sends 14,040 ETH to a new address, 0x79e7…544a.tx
21:52Binance: the verified total frozen is “around US$3 billion”.X
22:06–22:19Circle blacklists 3 more USDC addresses (0xb3dd, 0xd02a, 0x4201); the link between the last two and the hack is not verified.tx
22:14:110x5227 sends 2,000 ETH to 0x8532, which now holds 197,460 ETH.tx
22:17:470xa97b…8d10 sends 3,000 ETH to a new address, 0xc209…850a; from 22:21 it swaps tokens for ETH on decentralized exchanges.tx
22:36Binance repeats it will cover all losses; deposits and withdrawals remain suspended.X
23:02Chainalysis, quoting Binance, mentions “~$3B frozen”; it does not attribute the attack.X
23:25Binance: the incident may have started with a DevOps engineer’s compromised laptop, which gave access to a service container from which unauthorized withdrawals were sent.X
01:11:35Circle blacklists 0xa97b…8d10 for USDC.tx
01:19:23Circle blacklists 0x8c1c…e58c for USDC (link to the hack not verified).tx
01:31Chainalysis: “a high degree of confidence that DPRK is responsible” (North Korea). The attribution has not been independently verified.X
01:36Binance: deposits operate normally and it expects to resume withdrawals within 48 hours.X
02:15:470x5227 sends 17,260 ETH to a new address, 0x03b0…20ea.tx
02:31–02:330x79e7 receives 11,560.8 ETH from 0xcf4c…23e0 and 2,856.9 ETH from 0xb3dd…5fdb; it now holds 34,280 ETH.tx 1 · tx 2
03:36:110xa97b…8d10 sends 7,647 ETH to 0x5440…c942, which holds 40,600 ETH with no outflows.tx
04:37Richard Teng: “we’re covering every loss”.X
05:20CZ: “The hack is more complex than that”.X
07:55Binance: it set aside more than US$6.34B of its own funds to cover the hack and began recovering assets for users.X
09:20🔒 This tracker is closed.—

5. How much money left

Outflows from Binance wallets, verified on the Ethereum blockchain. verified

AssetFromAmountApprox. value (USD)
ETHBinance 14167,464.25~378M
ETHBinance 1628,005.6~63M
USDTBinance 141,619,327,1391,619M
USDTBinance 1655,739,80156M
USDCHot Wallet 34 (via Binance 14)823,000,000823M
RLUSDBinance 14 + 16~88.5M~88M
USD1 / USDeBinance 1427.8M / 9.7M~38M
Others (WBTC, WETH, ENA, PEPE, SHIB, LINK, UNI, AAVE, ONDO, WLFI…)Binance 14 / 16~60 tokensnot valued
ETH + USDT (2nd drain, 18:44)Binance 14369.8 ETH + 200.4M USDT~201M
Verified floormore than 3,400M

Second drain (18:44): 369.83 ETH + 200.40M USDT + 7,008 UNI, LINK, PEPE, SHIB and other tokens left Binance 14 (tx). Third drain (19:39): another ~128.5 ETH (tx). verified

ETH price used: US$2,259 (CoinGecko, 18:10 ART). Figures circulating on social media range from US$2.5B to US$3.5B; the verified floor here is more than US$3.4B on Ethereum alone. BWEnews estimates US$5.643B including BTC, Tron and L2s, and Lookonchain says more than US$5.8B. not verified

6. Where the money is: frozen and not frozen

USDT and USDC are “digital dollars” issued by companies (Tether and Circle) that can block an address so it can no longer move those tokens. That doesn’t exist for ETH: nobody can freeze it.

🧊 Frozen

🏃 Not freezable or already out of reach verified

Status of each wallet (as of 18:50 ART, block ~26,301,204) verified

Snapshot at 18:50. What happened afterwards is in the update log and in the list above.

AddressRoleBalance / status
0x5227…2f8cMain receiver1,175.46M USDT 🧊 (Tether) · 823M USDC 🧊 (Circle) · 2,078 ETH · 668 WETH · 167 WBTC · various tokens
0x8532…43d4ETH receiver197,460 ETH (no outflows, not freezable)
0xc887af69…286aETH receiver122,310 ETH, arrived from 0x9749292d at 18:47:47
0x897c80d1…8df3ETH receiver57,891.77 ETH, end of the hop chain (18:35:59)
0x9749…c762Swapped USDT for ETHBlacklisted; already empty (~4.8 ETH)
0xaa246bf6…54a0Intermediary175.0M USDT 🧊 (Tether)
0xb171ca86…c8c3Intermediary30M USDT 🧊 (Tether); forwarded 57,892 ETH to 0x897c
0x0ddf…697eIntermediarySwaps into WETH + 190M USDT to 0x8d53 · blacklisted
0x8d53…639aIntermediaryAave V3: collateral US$59.9M, debt US$45.1M, health factor 1.037 · blacklisted
0x77ed…c3eb / 0x7aa4…bfd1 / 0xccbe…a263Hop chain (EIP-7702)Empty; part of the chain to 0x897c
0x7c86…5ca0Attacker (contract owner)~1.3 ETH
Binance 14VictimBlacklisted by Tether (19:06). Still controlled by the attacker’s contract. Drained twice: 17:24 and 18:44 (369.8 ETH + 200.4M USDT + tokens)

7. What Binance said, withdrawals and markets

8. Contradictions and debunked rumors

Contradictions

Rumors and what we know

RumorWhat we know
“Binance froze/paused withdrawals”Now confirmed: @binance (19:15) says withdrawals will resume once the security issue is resolved; Yi He (19:22) says they are “disabled”; at 01:36 Binance said it expects to resume them within 48 hours. verified: official post
“Bybit, MEXC and Bitget were hit too”No evidence. no evidence
“19,000 BTC were stolen”No evidence. That number is the combined outflows of several exchanges. no evidence
“The funds were sent to Tornado Cash”Tornado Cash was used to fund the attacker; no outflows to Tornado have been seen. no evidence
“It was Lazarus / North Korea”Chainalysis says it has “a high degree of confidence that DPRK is responsible” (01:31) and Jony Levin attributes it to the TraderTraitor group (01:14). That is their claim; the attribution is not verified.
“The funds went through THORChain”ZachXBT (01:51) says funds from Binance and Bitget were pooled at one address after arriving through THORChain, but did not give the address; THORChain has not been seen in the Ethereum wallets being tracked. not verified
“Liquidity providers’ funds were hacked”No evidence. no evidence
Addresses that look like 0x9749…c762 / 0x0ddf…697eMany are address poisoning (fake addresses that mimic the real ones), not attacker wallets.

9. What we still don’t know

10. Verdict

Straight answer
The on-chain evidence is consistent with a hack (PeckShield calls it one; Binance has not confirmed it yet). It was not a contract bug: someone got Binance’s keys to sign what they wanted and used EIP-7702 to drain Binance’s largest hot wallet on Ethereum four times, until the authorization was revoked at 21:10. More than US$3.4B left on Ethereum alone. Tether and Circle froze ~US$2.2B in stablecoins on Ethereum (Binance says ~US$3B in total), but ETH can’t be frozen: about 468k ETH remain in six attacker wallets. Binance says it may all have started with a DevOps engineer’s compromised laptop, promises to cover all losses (at 07:55 it said it set aside more than US$6.34B of its own funds) and expected to resume withdrawals within 48 hours; when this tracker closed it had not published the full post-mortem. Chainalysis attributes the attack to North Korea (attribution not independently verified).

According to the investigation, what the attacker still holds on Ethereum would be around US$900M–1B, almost all in ETH. inference, not verified Until Binance publishes a report on what happened, there is no certainty about when withdrawals will resume or about coverage for users.

⚠️

Watch out for scams. Binance asks people not to trust unofficial links or messages: be suspicious of any “SAFU refund” or request for your account details that doesn’t come from its official channels.

11. Sources and verification

On-chain data was read directly from Ethereum (Etherscan API and a public RPC node): transactions, Binance 14’s EIP-7702 code, balances, and Tether (AddedBlackList) and Circle (Blacklisted) blacklist events from block 26,300,700. The drain transaction, the EIP-7702 delegation, balances and blacklists were re-read from the chain between 18:02 and 18:10 ART, and the large balances were tracked with periodic checks until 05:34 on Oct 30. Tron freezes were read via TronGrid. Block times were converted to Argentina time.

Wallets on Etherscan

Posts on X

Media and context

How reliable each source is

LevelSources
🟢 HighData read directly from the blockchain: transactions, EIP-7702 code, balances and blacklist events.
🟡 MediumOn-chain researchers with a track record (Spreek), alert accounts (Tree News, BWEnews) and media (BeInCrypto).
🔴 LowAnonymous accounts with round numbers (“3.5B”, “19k BTC”, “withdrawals frozen”) and AI-generated posts.
⚖️ BiasesAlert accounts reward speed over accuracy; pro-Binance accounts tend to downplay.
🔍

Independent, unsponsored tracker, built from public blockchain data and linked sources. Anything marked as inference is our own analysis. This is not financial advice. Closed tracker: last updated Oct 30, 2026 · 09:20 ART (12:20 UTC). For news, @binance on X.

✍️ Independent research — No sponsors
© 2026 diegodefi — built at home, over mate