Kling Digital
en
Contact
2026-10-29
6 MIN READ
Featured Guide

Was Binance Hacked? Breaking Statement from Changpeng Zhao (CZ) as Tether ($971M) and Circle ($823M) Freeze $1.79 Billion

Following massive unauthorized outflows from Binance's Ethereum hot wallets, founder Changpeng Zhao (CZ) confirmed: 'User funds are safe. It does look like a hack on Binance.' Here is the complete technical breakdown of how Tether froze $971M in USDT, Circle froze $823M in USDC, and what it means for user assets.

Was Binance Hacked? Breaking Statement from Changpeng Zhao (CZ) as Tether ($971M) and Circle ($823M) Freeze $1.79 Billion
Breaking Executive Summary & Key Facts
  • Confirmation from Changpeng Zhao (CZ): Following massive on-chain outflows from Binance's primary Ethereum hot wallets, Binance founder Changpeng Zhao issued a breaking statement: "User funds are safe. It does look like a hack on Binance."
  • $1.794 Billion Frozen at the Smart-Contract Level: Acting within minutes of anomaly detection, Tether froze approximately $971 million (USDT) and Circle froze approximately $823 million (USDC), locking down nearly $1.8 billion before attackers could launder the stablecoins.
  • Shareholder Backing & User Solvency: While noting he no longer runs day-to-day operations at Binance, CZ emphasized that as a major shareholder, he expects all user assets to be covered in full.

Global cryptocurrency markets were jolted after on-chain security monitors flagged billions of dollars in sudden, unauthorized outflows from Binance's primary Ethereum operational hot wallets (Binance 14 and Binance 16). Shortly after blockchain analysts raised the alarm, Binance co-founder and former CEO Changpeng Zhao (CZ) publicly addressed the incident.

In his statement shared across X, CZ confirmed the breach while reassuring depositors:

"User funds are safe. It does look like a hack on Binance. Appreciate Tether for freezing ~$971M and Circle for freezing ~$823M quickly. While I don't run Binance anymore, as a shareholder, I expect all user assets to be covered in full."

How did a multi-billion-dollar outflow occur from one of the most heavily fortified exchanges in the world? How were Tether and Circle able to freeze $1.794 billion in minutes, and what happened to the unfreezable native Ethereum (ETH) assets? Below is our deep technical and cybersecurity analysis.


1. Anatomy of the Binance 14 Hot Wallet Outflow

Centralized exchanges (CEXs) maintain a two-tier custody architecture: a small percentage of liquid assets is kept in internet-connected hot wallets to process instant user withdrawals, while the vast majority of customer deposits remain isolated in air-gapped cold storage vaults.

On-chain telemetry indicates that the breach targeted Binance's high-volume Ethereum hot wallet infrastructure, primarily Binance 14:

  1. Approximately $971 million in Tether (USDT),
  2. Approximately $823 million in USD Coin (USDC),
  3. And over 195,000 native Ether (ETH) alongside various ERC-20 tokens were rapidly drained into freshly generated external addresses with no prior transaction history.
Binance Hot Wallet Outflow and Stablecoin Smart-Contract Freeze Mechanism
Figure 1: Architectural contrast between centralized ERC-20 stablecoins halted via smart-contract blacklisting versus native Layer-1 assets (ETH) moving across decentralized nodes.

An unauthorized sweep of this magnitude points not to a user-level account compromise, but to an advanced intrusion targeting either the Multi-Party Computation (MPC) / private-key signing orchestration layer or the internal withdrawal authorization pipeline.


2. How Tether ($971M) and Circle ($823M) Executed a $1.79B Smart-Contract Freeze

The most decisive turning point of the incident was the rapid intervention by the world's two largest stablecoin issuers. Before the threat actor could swap the stolen stablecoins through decentralized exchanges (DEXs) or cross-chain bridges:

  • Tether's Intervention: Executed the addBlackList(address) function on the Ethereum USDT smart contract, immediately freezing ~$971 million in USDT inside the attacker's wallet.
  • Circle's Intervention: Simultaneously invoked the blacklist(address) method on the USDC smart contract, immobilizing ~$823 million in USDC.
Asset ClassEstimated VolumeSmart-Contract Freeze CapabilityOn-Chain StatusUser Recovery & Coverage Mechanism
Tether (USDT)~$971 MillionYes (addBlackList contract method)Frozen in attacker address (Non-transferable)Can be burned (destroyBlackFunds) and re-issued to Binance
Circle (USDC)~$823 MillionYes (blacklist contract method)Frozen in attacker address (Non-transferable)Recoverable via issuer compliance & law enforcement
Ethereum (ETH)195,000+ ETHNo (Permissionless Layer-1 asset)Dispersed across secondary wallets; under forensic trackingCovered by SAFU Fund & Binance corporate treasury
Cold Storage Vaults>$100 BillionAir-Gapped / HSM Hardware Isolation100% Secure (Unaffected by hot wallet incident)Direct 1:1 customer Proof-of-Reserves (PoR) backing

Because blacklisted ERC-20 addresses fail validation on every transfer and transferFrom call, that $1.794 billion in USDT and USDC is effectively neutralized and recoverable. However, as detailed in our guide on how cryptocurrency architecture works, native Layer-1 assets like ETH have no central issuer kill-switch, requiring on-chain forensics and exchange-level deposit freezes to track the dispersed ETH.


3. Are User Funds Truly Safe (SAFU)? What Investors Need to Know

CZ's statement—"While I don't run Binance anymore, as a shareholder, I expect all user assets to be covered in full"—carries significant weight for three reasons:

  1. Isolated Blast Radius: The compromise was strictly confined to operational hot wallets; Binance's multi-signature cold storage reserves remain untouched.
  2. Drastically Reduced Net Loss: By freezing $1.794 billion in USDT and USDC immediately, Tether and Circle eliminated the vast majority of the raw headline loss.
  3. SAFU & Treasury Cushion: Binance's SAFU (Secure Asset Fund for Users) emergency insurance pool and corporate retained earnings are more than sufficient to absorb the remaining unrecovered hot-wallet shortfall without impacting customer account balances.
Security Alert: Beware of Fake "SAFU Refund" & Phishing Links!

Immediately following high-profile exchange incidents, threat actors flood X (Twitter), Telegram, and email with fake "Binance Compensation Portal" or "Emergency Wallet Revoke" links. Binance will never ask you to connect a Web3 wallet, sign a transaction, or enter your seed phrase to secure your account.


4. Enterprise Cybersecurity & FinTech Architecture Lessons

When even the world's largest digital asset exchange experiences a hot-wallet signing breach, it underscores a fundamental law of custom software and financial systems engineering: cryptographic keys alone are not a complete security architecture.

Enterprise Crypto and FinTech Defense-in-Depth Security Architecture
Figure 2: Defense-in-depth custody architecture combining HSM hardware isolation, MPC key sharding, and real-time velocity circuit breakers.

Enterprise-grade payment gateways, custody platforms, and financial applications must implement four mandatory defense-in-depth layers:

  • Deterministic Velocity Circuit Breakers: Hardcoded rate limits at the signing enclave level that automatically halt all outbound transfers if cumulative outflow exceeds a defined threshold within a rolling time window—even if valid signing credentials are presented.
  • Geographically Isolated MPC & HSM Enclaves: Distributing cryptographic key shards across independent hardware security modules (HSMs) with separate network and cloud providers.
  • Zero-Trust Internal Orchestration: Preventing compromised internal microservices or CI/CD pipelines from injecting unauthorized batch withdrawal payloads into the signing queue.
  • Automated On-Chain Anomaly Hooks: Real-time mempool monitoring wired directly to issuer compliance APIs and emergency circuit breakers.
Enterprise Security & Architecture Audits

Building high-volume FinTech, e-commerce, or Web3 infrastructure? Partner with the Kling Digital Custom Software & Systems Engineering team to architect Zero-Trust backend systems and resilient transaction pipelines.

Frequently Asked Questions

Frequently asked questions regarding this guide.

Back to News
Share

Comments (0)

Share your thoughts and insights with the community.

No comments yet. Be the first to share your thoughts!

Leave a Comment

Your comment will be published after administrator approval.