DeFi Intel

Aave Reopens Markets but Keeps Nine Assets at Zero LTV

The collateral restrictions apply wherever the assets are listed, with different rules for existing V3 and V4 positions.

TL;DR

Aave reopened its V3 and V4 lending markets on 30 Oct 2026 after a 16‑hour freeze triggered by a Binance hot‑wallet breach, but nine tokens stay at zero LTV to block new collateral use. The move restores liquidity while limiting exposure to similar attacks.

Key facts

  • Aave reopened V3 and V4 markets on 30 Oct 2026.
  • Nine assets – USDT, USDC, USDT0, POL, WAVAX, sAVAX, XAUT, PAXG, OP – are set at zero LTV.
  • The Binance hack led to a wallet depositing 60 million USDT and borrowing about $44.6 million WETH.
  • Utilisation of stablecoin pools rose to 92‑100 percent during the freeze.
  • Risk adjustments removed $3.7 billion of idle capacity on V3 and $130 million on V4.
  • Aave’s smart contracts were not affected and all positions stayed fully collateralised.

Aave reopened its V3 and V4 lending markets on 30 October 2026 after a 16‑hour freeze triggered by a Binance hot‑wallet exploit. New deposits and borrowing are back online, but nine tokens – USDT, USDC, USDT0, POL, WAVAX, sAVAX, XAUT, PAXG and OP – remain at a zero loan‑to‑value (LTV) setting, meaning they cannot be used as collateral for fresh loans. The protocol said its smart contracts were untouched and all existing positions stayed fully collateralised. The freeze had been a precaution after a wallet linked to the Binance attacker deposited 60 million USDT and borrowed roughly $44.6 million worth of WETH.

Background

The emergency pause came after the Binance exchange reported a hot‑wallet breach on 29 October 2026, an incident that Elliptic estimated caused losses of about $6.43 billion. The attacker used the compromised Binance signing keys to move funds across ten blockchain networks, eventually depositing a large USDT tranche into Aave V3 Ethereum Core and borrowing Wrapped Ether. Risk monitoring firms LlamaRisk and TRM Labs highlighted that the attacker’s position was over‑collateralised – roughly $59.9 million in USDT against $43.8 million in debt – and that no other Aave users were directly exposed. In response, Aave’s guardians froze 175 reserves on V3 across 16 networks and 117 reserves on V4 across four networks, while keeping Horizon real‑world asset markets open because they use permissioned collateral. The freeze halted new deposits and borrowing but allowed withdrawals, repayments and liquidations to continue, preserving liquidity for existing lenders. After a joint war‑room involving Aave Labs, TokenLogic and Certora assessed the situation, the protocol staged a four‑wave unfreeze, restoring most functionality while keeping the nine listed assets at zero LTV as a temporary safeguard.

What happened

According to tokenpost.com, Aave announced on 30 October that it had reopened both V3 and V4 markets, restoring the ability for users to make new deposits and borrow assets, but it kept nine specific tokens at a zero LTV as a continued precaution. portalcripto.com.br added that the affected tokens include USDT, USDC, USDT0, POL, WAVAX, sAVAX, XAUT, PAXG and OP, and that wrapped and bridged versions of these tokens are also subject to the same restriction. cryptotimes.io reported that the protocol’s X post confirmed the markets were unfrozen after the Binance hot‑wallet exploit, reiterating that the nine tokens cannot serve as collateral for new loans and that the smart contracts were not compromised. coingabbar.com detailed the unfreeze process, noting that the DAO’s X update at roughly 13:57 UTC confirmed the markets were open again after a 16‑hour pause, and that the guardians executed the reopening in four waves, first unfreezing V3 reserves with zero borrowing power, then applying the zero‑collateral setting on V4, before restoring borrowing capacity for most assets. All sources agree that existing positions remained fully collateralised and that the zero‑LTV setting applies only to new risk changes, not to already open loans.

Market impact

LlamaRisk’s analysis on 30 October showed that the attacker’s single position held $59.9 million in USDT collateral against $43.8 million in debt, a loan‑to‑value of roughly 73 percent, and that this position did not threaten Aave’s liquidity providers. During the freeze, utilization rates in stablecoin pools rose to between 92 percent and 100 percent, prompting LlamaRisk to lower the Slope2 interest parameter. When the markets reopened, risk adjustments removed about $3.7 billion of idle capacity on V3 and $130 million on V4, according to the same source. The freeze also caused Aave’s native stablecoin GHO to slip from $0.998 to $0.997 as holders redeemed nearly $4.6 million. Binance reported that roughly $3 billion of its funds were frozen on‑chain after the hack, and the exchange set aside more than $6.34 billion to cover about 80 percent of the estimated $6.3 billion loss.

Why it matters

The reopening restores normal lending activity for the majority of Aave’s users, allowing fresh capital inflows and borrowing that were stalled during the freeze. Keeping nine assets at zero LTV reduces the protocol’s exposure to rapid asset swaps that could be used to launder stolen funds, a risk highlighted by the attacker’s use of USDT to obtain WETH, an asset that cannot be frozen by its issuer. The high utilization of stablecoin reserves during the pause demonstrated how quickly liquidity can become constrained in a crisis, prompting Aave’s risk team to adjust interest parameters and borrowing caps to protect suppliers. The incident also underscores the interconnectedness of centralized exchanges and DeFi platforms; a breach at Binance quickly propagated to Aave, prompting a coordinated response across multiple risk teams and governance bodies. Finally, the fact that Aave’s smart contracts remained untouched and all positions stayed over‑collateralised reinforces confidence in the protocol’s technical resilience, even as it navigates external security shocks.

DeFi Intel’s take

Editorial analysis, not a statement of fact.

DeFi Intel's take: the swift unfreeze suggests Aave’s emergency governance mechanisms are effective at containing fallout from external attacks. We read the zero‑LTV guardrails as a targeted risk mitigation that balances the need to resume market activity with the caution required to prevent further exploitation of stablecoins as a conduit for illicit transfers. The removal of billions of idle capacity indicates the protocol is actively managing supply to avoid over‑extension of liquidity, which could otherwise amplify stress in future incidents. Overall, the episode highlights the importance of rapid, coordinated response teams and the value of maintaining over‑collateralisation buffers to safeguard lenders during systemic shocks.

Frequently asked questions

Why did Aave keep nine assets at zero loan‑to‑value after reopening?

Aave set the loan‑to‑value of USDT, USDC, USDT0, POL, WAVAX, sAVAX, XAUT, PAXG and OP to zero to prevent those tokens from being used as collateral for new loans. This restriction is a precaution against the type of attack that used stablecoins to obtain unfreezeable assets, and it applies only to new risk changes, not to existing positions.

Did the Binance hack affect Aave’s smart contracts?

All sources state that Aave’s smart contracts were not affected by the Binance hot‑wallet exploit. The protocol confirmed that every existing position remained fully collateralised and that normal liquidation rules continued to apply throughout the freeze.

How much idle borrowing capacity was removed when Aave reopened its markets?

When the markets reopened, risk adjustments removed roughly $3.7 billion of unused borrowing capacity on V3 and about $130 million on V4, according to the risk analysis cited by the reporting outlets.

Direct answers

Short answers, written to be quoted.

What happened to Aave after the Binance hack?
Aave froze all V3 and V4 markets for about 16 hours, then reopened them on 30 Oct 2026 while keeping nine tokens at zero loan‑to‑value to prevent their use as collateral for new loans.
Which tokens are still restricted on Aave?
The restricted tokens are USDT, USDC, USDT0, POL, WAVAX, sAVAX, XAUT, PAXG and OP, all of which have a zero LTV setting on both V3 and V4.
Did the attacker’s position put Aave’s liquidity providers at risk?
LlamaRisk reported the attacker’s position was over‑collateralised, with $59.9 million in USDT against $43.8 million in debt, and concluded it did not pose a risk to Aave’s liquidity providers.
Read full article on The Defiant →

DeFi Intel is an entity-graph aggregator: we curate, tag and link crypto news to a typed knowledge graph of protocols, tokens, people and incidents. We do not republish the full article body. Use the link above to read the original report at The Defiant.

Discussion

Comments are reviewed before publication.

No comments yet.

Want the full article?

Continue reading on The Defiant →

Stay current on entity-tagged crypto news

Get the weekly DeFi Intel brief — entity-graph intelligence covering protocols, tokens and incidents, free to your inbox.