Blog  โ€บ Crypto News
CRYPTO NEWS

Binance Hack Fears: Nearly $3 Billion Leaves Hot Wallets as Tether and Circle Freeze $2.4 Billion

By Moderator Alex ยท October 29, 2026
Binance Hack Fears: Nearly $3 Billion Leaves Hot Wallets as Tether and Circle Freeze $2.4 Billion

October 29, 2026 ยท Updated 22:30 UTC


It took about 40 minutes. On Thursday evening, wallets labeled as belonging to Binance began sending billions of dollars in ETH, USDT, USDC and dozens of other tokens to a freshly created address. By the time the exchange posted its first statement, on-chain trackers had counted an estimated $2.5 billion to $3.5 billion in outflows. It is one of the largest suspected exchange breaches in crypto history.

Binance has not confirmed a hack. Its official position is that it is investigating "a potential security issue" and that user funds are "completely safe." Founder Changpeng Zhao, who no longer runs the company, was more direct: on X, he wrote that the activity "does look like a hack on Binance."

Here is what we know, what is still unconfirmed, and what it means for anyone holding funds on an exchange right now. Below, we also look at how community tools like ApeWatch are rethinking how traders get and verify information when the market is moving faster than official statements.


Binance Hack Timeline: What Happened on October 29


According to on-chain data compiled by Unchained and ShiftDelete, the sequence unfolded like this (all times UTC):

  1. 20:20 โ€” An EIP-7702 delegation is set on the hot wallet known as "Binance 14." How that delegation was authorized is still unknown.
  2. 20:24 โ€” Funds begin leaving Binance 14, including roughly 167,000 ETH and about $1.6 billion in USDT. "Binance 16" sends a further 28,005 ETH to the same receiving address seconds later.
  3. 21:01 โ€” Tether blacklists the receiving address.
  4. 21:04 โ€” Circle freezes around 823 million USDC.
  5. 21:16 to 21:29 โ€” Binance publishes and edits its statement several times, settling on "user funds are completely safe."

Security firm PeckShield first flagged "unexpected large outflows" from Binance hot wallets, before labeling the incident a hack. Reports from FXStreet and Bloomingbit initially put the total at $2.77 billion across five blockchains. Later estimates range higher as analysts finished tracing the funds.


Stablecoin Freezes Limit the Damage, but ETH Can't Be Frozen


The fast response from stablecoin issuers is the most important development so far. Tether CEO Paolo Ardoino said more than 1.567 billion USDT has been frozen, and Crypto News Flash reports that Circle's 823 million USDC freeze was done in coordination with law enforcement. Combined, roughly $2.4 billion to $2.5 billion in stablecoins is now locked.

Ether is a different story. The receiving wallet still holds about 195,469 ETH, worth around $452 million, according to Etherscan data cited by Crypto News Flash. ETH has no central issuer, so nobody can freeze it. If this is confirmed as a theft, that is the portion most likely to be lost or laundered.

Reports from BeInCrypto, cited by ShiftDelete, also say the address that triggered the transfer was funded through Tornado Cash. That detail has not been independently confirmed, but it is a pattern seen in many past exploits.


Market Reaction: BNB Drops 9%, Bitcoin Slips Below $79,000


Markets moved before the facts were in. BNB fell as much as 9%, according to CoinGecko data cited by ShiftDelete, and Bitcoin dropped from above $80,800 to below $79,000. Leveraged long positions across the market were wiped out as traders rushed to cut risk.

If Binance confirms a loss, the most likely backstop is its Secure Asset Fund for Users (SAFU), set up in 2018 from trading fees. It was last used in May 2019, when hackers stole 7,000 BTC and Binance covered affected users in full. Binance has not said whether SAFU will be used this time, and some users have reported problems withdrawing, which the exchange has not addressed.


Is Binance Safe Right Now? What Users Should Do


Until Binance publishes a full incident report, a cautious approach makes sense:

  1. Follow official channels only. Binance warned users against unofficial links and anyone asking for account details. Phishing campaigns always spike after incidents like this.
  2. Don't trade on rumors with leverage. The first hours of a breach are when liquidations hit hardest and misinformation spreads fastest.
  3. Review where your funds sit. This is a reminder of the old rule: assets you don't need to trade actively are safer in self-custody.


Why This Story Broke On-Chain First, and Where ApeWatch Fits


Look at how tonight played out. The first alerts didn't come from Binance. They came from on-chain watchers and security firms who spotted the wallet movements in real time, and were posted on X long before any official statement. Within an hour, though, timelines were also full of conflicting numbers, fake "Binance support" accounts and wild guesses. Traders had to figure out on their own whose information they could trust.

That trust problem is exactly what ApeWatch is built around. ApeWatch is a community discovery terminal where the people sharing calls are ranked by their actual track record, not by follower count or how loud they are:

  1. Post to the Jungle: users drop a token contract from Solana, Ethereum or BNB Chain, and the community votes "Ape It" or "Nah."
  2. Earn Banz: good calls earn Bananaz (Banz), XP and streaks, and users earn more when their calls actually perform.
  3. Climb the Ranks: hit rate, winning calls and streaks push users up the Ape leaderboard, so the best callers become the voices the community watches.

The whole system runs on $APEDG, the utility token behind ApeWatch, built by ApeDegen. $APEDG powers community participation, reputation, rewards, staking and the future expansion of the terminal.

To be clear, ApeWatch doesn't monitor exchange hot wallets and couldn't have prevented tonight's incident. What it addresses is the problem traders faced right after: in a market driven by anonymous posts, who has actually been right before? A public, performance-based reputation score is one answer. As with any early-stage project, $APEDG carries high risk, so do your own research before getting involved.

Learn more at apedegen.io or join the community on Telegram.


What to Watch Next


The next 24 to 48 hours will decide how big this story becomes. The key questions: will Binance confirm a breach and explain how the EIP-7702 delegation was authorized? Will it say if SAFU covers any losses? Will the unfrozen ETH start moving through mixers? And can BNB hold its levels once the dust settles? We will update this article as official information comes in.


FAQ


Was Binance hacked?

Not officially confirmed. Binance says it is investigating a potential security issue and that user funds are completely safe. CZ said the activity "does look like a hack," and PeckShield labeled it a hack.

How much money left Binance wallets?

Estimates range from about $2.5 billion to $3.5 billion, depending on the chains counted. Initial reports said $2.77 billion across five blockchains.

How much has been frozen?

Tether says more than 1.567 billion USDT is frozen and Circle froze around 823 million USDC, about $2.4 billion combined. Roughly 195,469 ETH (around $452 million) cannot be frozen.

What is ApeWatch?

ApeWatch is a community token discovery terminal by ApeDegen. Users post tokens from Solana, Ethereum and BNB Chain, vote "Ape It" or "Nah," and earn Banz, XP and leaderboard rank based on how their calls perform. It is powered by the $APEDG token.

Disclaimer: This article is for information only and is not financial advice. Details of the Binance incident are still developing and have not been fully confirmed by the exchange. This article features ApeDegen and ApeWatch, projects promoted by this publication. Crypto assets, especially early-stage tokens, are highly volatile. Do your own research.

Share: ๐• Twitter โœˆ๏ธ Telegram LinkedIn