Aave’s risk‑management team, LlamaRisk, announced plans to impose a time‑based borrowing cap on its protocol after a wallet linked to the recent Binance hot‑wallet hack extracted roughly $44.6 million worth of ether using USDT as collateral. The proposal, outlined by LlamaRisk CEO Adam Sadowski on the Uneasy Money podcast on Nov. 4, aims to limit how much can be borrowed within defined intervals, though specific parameters have not yet been disclosed.

ETH / USD
Source: CoinGecko. Prices are indicative.

Background of the exploit

Six days prior to the announcement, a wallet identified by Etherscan as a Binance hot‑wallet exploiter posted USDT— a stablecoin that can be frozen by its issuer— as collateral on Aave and immediately borrowed ether. According to on‑chain data cited by Unchained, the attacker withdrew 19,762 WETH (about $44.6 M) in roughly three minutes on Oct. 29, backed by 60 million USDT. The loan’s health factor fell to 1.24, prompting partial liquidation and a freeze of new deposits and borrowing on Aave’s Ethereum Core market.

Proposed risk‑oracle solution

Sadowski described the upcoming feature as a “risk oracle” that would translate real‑world signals into protocol actions, specifically throttling borrowing capacity over set periods. He referenced Chainlink’s Runtime Environment (CRE) as the technical foundation, noting that LlamaRisk already runs a Pendle‑token oracle on CRE and plans to extend the framework to supply and borrow caps. The approach is intended to replace manual multisig decisions— currently a four‑of‑seven multisig that must align to act— with automated safeguards.

Community response and challenges

The proposal has sparked debate among Aave participants. Some community members, such as user gnarvaja, suggested automated supply‑cap updaters, while others warned that per‑account limits could be circumvented by splitting loans across multiple addresses. Synthetix founder Kain Warwick echoed concerns about unintended consequences, noting the high risk of altering core risk parameters. Sadowski acknowledged the trade‑offs, emphasizing that the Aave DAO ultimately governs the scope and frequency of any delegated operator’s actions.

What to watch next

The next steps involve a formal governance proposal from LlamaRisk and a vote by the Aave DAO. Observers will monitor the specific design of the borrowing caps, the timeline for implementation, and any impact on liquidity and user experience. Additionally, the broader DeFi community will watch how other protocols respond to rapid‑borrow exploits and whether automated risk oracles become a standard defensive tool.