Aave Freezes Avalanche Markets, Arbitrum Locks $30.5M as $3B Frozen in Record $6.3B Exploit
Decentralized finance (DeFi) protocols have joined stablecoin issuers in trying to contain the Binance hot wallet exploit. Aave, the largest DeFi lending protocol, froze lending markets on 16 networks, including Avalanche, to stop the attacker from borrowing more funds.
Separately, the Arbitrum Security Council froze about $30.5 million in Arbitrum (ARB) tokens and Ether (ETH) linked to the attack early on October 30, 2026. Binance says about $3 billion has now been frozen. It estimates the total impact at around $6.3 billion, which analysts describe as the largest crypto theft on record.
Exploit leveraged Ethereum’s EIP‑7702, hijacking Binance hot‑wallet signing keys to authorize 50 fraudulent transactions.
Attacker drained 167,464 ETH and 1.6 bn USDT across ten blockchains, using pre‑signed authorizations that matched wallet nonces.
Aave and Arbitrum froze assets to block further borrowing, but the breach stemmed from compromised hot‑wallet infrastructure.
Aave Freezes Lending Markets, Including Avalanche
Aave said on X that it had frozen its lending markets on Avalanche to stop the Binance hacker from borrowing funds. Its full response was set out in a post on the Aave governance forum by LlamaRisk, one of Aave’s risk service providers.
The attacker borrowed before the freeze. According to the post, a wallet in the attacker’s cluster supplied 60 million Tether (USDT) to the Aave V3 Ethereum Core market between 20:58 and 21:01 Coordinated Universal Time (UTC) on October 29. Against that collateral, it borrowed 19,762 Wrapped Ether (WETH), worth about $44.6 million at the time. This turned USDT that Tether could freeze into ETH that no issuer can freeze. The wallet’s last interaction with Aave came at 21:01 UTC.
How the freeze was carried out.
- Within 10 minutes of the first reports, Aave Labs, TokenLogic and Certora formed a joint response team.
- They chose a market freeze instead of cutting supply and borrow caps. A freeze can be reversed by Aave’s guardian multisig, a group of signers with emergency powers. Restoring cut caps would have needed a governance vote and about five days.
- The first freeze transaction went through at 21:42 UTC, about 40 minutes after the attacker’s borrow. The guardian finished the freezes at around 23:04 UTC.
Avalanche was part of a second wave. That same minute, 444,537 Avalanche (AVAX) tokens reached the attacker on the Avalanche network, which LlamaRisk said suggested the compromise was still active. A wallet holding that much AVAX could post it as collateral on a lending market and borrow other assets against it, so freezing Avalanche closed off that route. TRM Labs separately reported that Binance wallets on Avalanche and Polygon were drained at around 23:05 UTC.
Markets frozen. Aave froze 175 reserves on its V3 markets across 16 networks:
- Ethereum Core and Prime, Arbitrum, Avalanche, Base, BNB Chain, Celo, Gnosis, Ink, Linea, Mantle, MegaETH, Monad, Optimism, Plasma, Polygon and X Layer
It also froze 117 reserves across four networks on its V4 deployment, including the Avalanche spokes. LlamaRisk said the attacker could swap stolen funds into any listed asset, so freezing only the stolen tokens would not have been enough. The Horizon real-world asset (RWA) market stayed open because all its collateral is permissioned, and no market was fully paused.
Is Aave at risk? LlamaRisk said the attacker’s position holds $59.9 million in USDT collateral against $43.8 million in debt. That means it is over-collateralized and can be liquidated in the normal way. It is the attacker’s only position on Aave, and LlamaRisk said it does not put suppliers at risk.
What users can and cannot do while markets are frozen:
- They cannot open new supply or borrow positions, or add collateral.
- They can still repay loans and withdraw funds.
- Liquidations continue.
- Repaying is the only way to improve a position’s health factor, the measure of how close a loan is to liquidation.
When will Aave unfreeze? Markets will stay frozen until the attacker’s funds stop moving and Binance gives more clarity on containment. A staged unfreeze will follow. LlamaRisk warned that withdrawals during the freeze push up utilization and borrowing rates.
Prices on Aave. As of 00:55 UTC, Aave’s price oracles were working normally. AAVE was down about 9% since the drain began, ARB about 6%, and ETH and Bitcoin (BTC) about 4%. GHO, Aave’s native stablecoin, slipped from about $0.998 to $0.997.
Replies on the forum were split. Some participants called the broad freeze an overreaction to a $60 million position. Others asked for automated limits on large deposits so the protocol could respond without manual freezes.
Arbitrum Security Council Freezes $30.5 Million
On-chain investigator ZachXBT first reported the Arbitrum freeze on X. He identified the exploiter address as 0x3E2..632d5 and shared the freeze transaction on Arbitrum One. The council moved 74,559,805 ARB and 8,425 ETH.
Arbitrum confirmed in an official post that the Security Council took emergency action to move the funds to an intermediary frozen wallet on Arbitrum One. It said the step did not affect any other users or applications. The original address can no longer access the assets. They can only be moved by further Security Council action or a vote of the Arbitrum Decentralized Autonomous Organization (DAO), the token-holder body that governs the network. Binance co-founder and co-chief executive officer (CEO) Yi He acknowledged the freeze on X.
The Security Council is a group of 12 members elected by the Arbitrum DAO and holds emergency powers over the network. In April 2026, it froze 30,766 ETH linked to the KelpDAO exploit, a move that set off a debate about how centralized the network really is.
How the Binance Exploit Unfolded
Suspicious outflows from Binance wallets began on the evening of October 29 UTC. The Crypto Times first reported that the Binance 14 hot wallet moved billions of dollars to a new address within minutes. A hot wallet is an exchange wallet that stays connected to the internet so it can process withdrawals.
According to a TRM Labs analysis, the attacker sent one transaction at 20:20 UTC that contained 50 pre-signed authorizations. The attack relied on EIP-7702 (Ethereum Improvement Proposal 7702), a feature added in Ethereum’s Pectra upgrade in May 2025. It lets a standard wallet hand control of its behaviour to a smart contract. The authorizations covered 50 consecutive nonces, which are the transaction counters a wallet uses, and only one of them matched the wallet’s count when it ran.
About three minutes and 24 seconds later, the attacker swept the wallet’s full balance. That balance included 167,464 ETH and 63 other tokens, among them 1.615 billion USDT.
Other chains were hit at the same time. A Binance Bitcoin hot wallet sent 18,270 BTC, worth about $1.47 billion, and a Binance hot wallet on Tron sent 612.7 million USDT and 46.4 million TRX. TRM Labs counted funds taken from Binance wallets on ten blockchains: Ethereum, Bitcoin, Tron, the XRP Ledger, Solana, Arbitrum, Optimism, Base, Avalanche, and Polygon.
How Big Is the Binance Hack?
Loss estimates vary because firms used different methods and valued the assets at different times. TRM Labs puts the total at about $6.36 billion, valued at the time of each transfer. Blockchain analytics firm Chainalysis estimated about $5.912 billion at the time of the theft. Arkham Intelligence linked nearly $6 billion in assets to 55 wallet addresses tied to the exploit.
Every one of these figures is about four times the $1.5 billion Bybit hack of February 2025, which was the previous record.
Who Is Behind the Attack?
TRM Labs attributes the attack with high confidence to TraderTraitor, a North Korean state hacking unit. It cites both on-chain and off-chain evidence. The U.S. Federal Bureau of Investigation (FBI) attributed the Bybit theft to the same group. ZachXBT has also said the attack was likely the work of North Korea’s Lazarus Group, the wider label for the country’s state-backed hacking operations.
Binance has not named an attacker. TRM Labs’ own assessment points to a compromise of Binance’s hot wallet signing infrastructure.
Freezes Reach Around $3 Billion
Within an hour of the first outflows, stablecoin issuers began blacklisting addresses. Tether and Circle froze nearly $1.8 billion in their first actions. TRM Labs reported the following totals as of 00:30 UTC on October 30:
- Tether: about 1.77 billion USDT frozen across Ethereum, Tron, Avalanche and Polygon. The main receiving wallet was frozen at 21:01 UTC.
- Circle: about 825 million USD Coin (USDC). Of that, 823 million USDC was frozen at 21:04 UTC in coordination with law enforcement.
- Ripple: 40.5 million Ripple USD (RLUSD), frozen at 22:01 UTC. Yi He separately said Ripple helped freeze about 200 million in related assets but did not name the token.
- World Liberty Financial: 27.8 million USD1, frozen at 22:10 UTC. Yi He said roughly $2 million in WLFI tokens was also frozen.
- Binance: 29,934 Wrapped Beacon ETH (WBETH), its liquid staking token, blocked through its own token contract controls.
- Arbitrum Security Council: about $30.5 million in ARB and ETH.
Binance’s verified frozen total rose from $2.54 billion to around $3 billion shortly before 01:00 UTC on October 30. The exchange said the figure could rise as tracing continues. In a follow-up post, ZachXBT put his own running tally above $2.83 billion.
According to TRM Labs, the attacker still holds more than 420,000 ETH and 18,270 BTC, worth about $2.4 billion. These are native assets, so no token issuer can freeze them.
Binance Response
In an official statement on X early on October 30, Binance said its initial investigation suggests the incident “may involve a compromised DevOps engineer’s laptop.” DevOps refers to the team that handles both software development and IT operations. According to Binance, the laptop gave the attacker access to a service container, which was then used to submit unauthorized withdrawal transactions.
The exchange said it has “found no evidence of any wallet private key leak.” It added that it will cover all losses from its Secure Asset Fund for Users (SAFU) and company funds, and that user funds are safe.
Binance also:
- temporarily suspended deposits and withdrawals while it completes security checks
- revoked the affected address authorization
- brought in law enforcement and blockchain intelligence partners to trace and recover funds
It said it will publish an updated Proof of Reserves (PoR) once remediation is complete, along with a detailed technical post-mortem once the facts are verified. Before Binance confirmed the breach, former CEO Changpeng Zhao (CZ) had said the outflows looked like a hack and that user funds were safe.
Market Reaction
The news hit prices across the market. Bitcoin, ETH and BNB dropped sharply as traders reacted to the outflows and the freezes that followed, which forced heavy liquidations. Bitcoin fell toward $77,000, and BNB, Binance’s native token, lost as much as 9% during the selloff. DeFi governance tokens were also hit, with AAVE and ARB among the decliners.
Analysis: What the Aave and Arbitrum Freezes Signal
The roughly $3 billion frozen is close to 48% of Binance’s own $6.3 billion estimate. That share is unusually high for an exchange hack, and it shows where intervention works. Tokens with a central issuer can be blacklisted, and networks or protocols with emergency governance bodies can step in. Native BTC and ETH on their base chains cannot be frozen.
The Aave episode shows both sides of this. The attacker used Aave to turn freezable USDT into ETH that no one could freeze, and did so about 40 minutes before the guardian acted. The broad freeze that followed, including Avalanche, closed off further borrowing. It also restricted ordinary users on 16 networks.
Both Aave and Arbitrum have now used emergency powers twice in 2026, after doing the same during the KelpDAO exploit in April. Supporters say these tools are reversible and limited to emergencies. Critics say they show that small groups of signers can control markets and funds on networks presented as decentralized.
Several questions remain open:
- how the Arbitrum DAO will vote on the frozen ARB and ETH
- when Aave will begin its staged unfreeze
- when Binance will publish its technical post-mortem and resume withdrawals
- where the attacker’s remaining ETH and BTC will go next
All figures in this report may change as on-chain tracing and official checks continue. Binance has asked users to rely only on its official channels for updates.
Also Read: Polymarket Restores Trading After Major Security-Related Outage
Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.


