Aave froze 292 reserves across its lending deployments following the October 29 Binance wallet exploit, according to an October 30 update from risk service provider LlamaRisk. The emergency measure was designed to stop attacker-controlled assets from entering new lending positions while keeping essential repayment and withdrawal functions available.
Which Aave markets were frozen
According to LlamaRisk’s update on the Aave governance forum, the freeze covered 175 reserves on Aave V3 across 16 networks and 117 on Aave V4 across four networks. Aave Labs, TokenLogic, Certora and guardian multisigs coordinated the response, with freeze transactions executed between 21:42 and 23:04 UTC on October 29.
The team said the Horizon real-world-asset market was left open because its collateral is permissioned. It also emphasized that freezing reserves is different from pausing entire markets.
What users can still do
Under the temporary freeze, users cannot open new supply or borrowing positions in affected reserves. Existing users may generally repay debt, withdraw assets and have positions liquidated under the normal risk mechanisms.
However, because deposits and additional collateral are blocked, a borrower who wants to improve a deteriorating health factor may have to repay instead. Users should check the exact reserve and network before assuming a particular transaction remains possible.
Attacker’s borrowing position
LlamaRisk reported that an attacker-linked wallet deposited about 60 million USDT on Aave V3 Ethereum Core and borrowed roughly 19,762 WETH, valued at approximately $44.6 million when opened. It described the position as overcollateralized and subject to the usual liquidation rules.
The risk provider said no known attacker wallet had interacted with Aave since 21:01 UTC on October 29, based on its investigation as of 01:00 UTC October 30. That observation is a time-specific snapshot, not a guarantee against later activity.
Next steps and lending-market consequences
The team said it would track attacker-controlled wallets, price feeds, utilization and liquidity while considering a staged reopening. A prolonged freeze could change borrow rates: supplier withdrawals reduce liquidity, while new deposits remain disabled.
The incident illustrates how a breach at a centralized exchange can trigger defensive actions in unrelated decentralized protocols. BlockBriefing’s introduction to decentralized finance explains the lending-market structures involved. Aave’s response is a containment measure, not a statement that the protocol itself was exploited. The separate exchange-side incident is detailed in BlockBriefing’s Binance security report.
Primary source and verification
Read the original announcement or data record for the underlying evidence. Figures and circumstances reflect the publication dates specified in this report and may change with subsequent disclosures.
BlockBriefing reports on digital assets for information, not as investment, legal or trading advice. Images created for this report are editorial illustrations, not documentation of the event.
