We analyzed this claim: is it true that

gradual collateral-credit activation or borrowing-velocity limits could have prevented the Binance attacker from obtaining 19,762 WETH before Aave's emergency freeze without imposing disproportionate restrictions on legitimate borrowers?

Aave’s Proposed Speed Limit Would Have Missed Binance’s HackerAI generatedDeveloping

Transaction records confirm the $44.6 million loan took three minutes, well before Aave's emergency freeze 41 to 46 minutes later. A long waiting period on new collateral would have blocked the loan, but risk manager LlamaRisk's own November 11 simulation shows its proposed borrowing speed limit would still have released the entire $44.6 million before freezes took effect, leaving the trade-off between security and ordinary user access unresolved.

CryptoStory in development
  • ClaraAuthorComing December 1
  • RafaVisual artistComing December 1
  • JolinaMarketingComing December 1

Aave’s Proposed Speed Limit Would Have Missed Binance’s Hacker

Simulations show a planned borrowing cap could still have let a thief take $44.6 million in crypto before emergency freezes arrived.

Published
Quantum Otter — crypto markets and AI trading bots

In a nutshell

After thieves stole $6.34 billion from Binance on October 29, 2026, an attacker wallet used $60 million in freezable USDT stablecoins to instantly borrow $44.6 million in unfreezable ether on Aave in just three minutes—more than 40 minutes before Aave's emergency guardians could freeze the market. While Aave suffered no financial losses because the loan remained over-collateralized and was half-liquidated on November 4, the incident sparked a governance debate over how to slow down malicious borrowing. Risk manager LlamaRisk proposed an automated $25 million borrowing cap with a 30-minute refill, yet its own simulation showed the attacker could still have extracted the full $44.6 million within 36 minutes, leaving Aave torn between strict collateral waiting periods and keeping open lending fast for legitimate users.

Highlights

  • An attacker wallet deposited $60 million in stolen USDT on Aave and borrowed 19,762.42 WETH worth $44.6 million in exactly three minutes on October 29, 2026.
  • Aave's first emergency freeze arrived 41 minutes and 12 seconds after the final loan, and the specific V3 Core market was frozen after 46 minutes and 24 seconds.
  • An automated liquidation on November 4 repaid 9,884.42 WETH of the debt in exchange for $24.38 million in USDT, leaving Aave with zero bad debt.
  • LlamaRisk's November 11 simulation found its proposed $25 million borrowing buffer with a 30-minute refill would still have released the full $44.6 million in 31 to 36 minutes.
  • Modeling shows LlamaRisk's borrowing speed limit would cause roughly 162 hours of annual wait times for legitimate borrowers across 68 large WETH loans.

How Proposed Defenses Perform Against the October 29 Loan

Defense DesignOutcome in Replay and User Impact
Collateral maturation (waiting period over 72 seconds)Blocks both October 29 loans completely, but lacks an approved formula…
LlamaRisk rate limiter ($25M buffer, 30-minute refill)Releases full $44.6M within 31 to 36 minutes before freeze; creates 162 hours…
Tighter rate limiter ($10M cap per 10 minutes)Slows initial burst, but still allows full $44.6M draw before the 41-minute…
  • A side-by-side comparison of how three proposed Aave safeguards fare against the three-minute Binance loan and their cost to regular borrowers.
  • Shows why Aave has not yet implemented a permanent fix: simple speed limits do not buy enough time for manual freezes, while strict waiting periods risk slowing legitimate traders.

From the Editor’s Diary

In automated financial markets, emergency brakes that rely on human reaction times cannot beat software that settles transactions in seconds—forcing platforms to choose between frictionless access for everyone and built-in delays that give defenders a chance to intervene.

Who's involved

  • Binance-linked attacker wallet cluster

    Digital wallet addresses controlled by the thieves behind the October 29 exchange breach, linked by the FBI to North Korea's TraderTraitor group

    goal → Swap stolen, freezable digital tokens for unfreezable cryptocurrency before defenders intervene

  • Aave DAO and Protocol Guardians

    The community governance group and emergency security team overseeing the Aave crypto lending platform

    goal → Protect lenders and platform funds while keeping normal borrowing and repayments open

  • LlamaRisk

    An independent risk-management firm advising Aave

    goal → Replace slow manual emergency freezes with automated borrowing caps that react quickly without hurting regular users

  • Tether

    The company that issues USDT, a digital token pegged to the US dollar that it can freeze via blacklists

    goal → Block stolen USDT tokens without disrupting innocent users or entire lending pools

  • Binance

    The major cryptocurrency exchange hit by a roughly $6.34 billion theft from its online wallets

    goal → Contain the breach, restore customer funds and recover stolen assets

  • Aave borrowers and liquidity suppliers

    Everyday traders and institutions who deposit crypto into Aave to earn interest or take out loans

    goal → Keep instant access to legitimate loans and avoid sudden freezes or forced liquidations

  • Independent Aave governance contributors

    Researchers and users proposing waiting periods on new deposits and automated supply limits

    goal → Build clear, automated safeguards without adding identity checks or manual censorship

In short

Automated crypto lenders face a fundamental design flaw: instant borrowing lets thieves swap freezable tokens for untraceable cash before defenders can react. Following the October 29 theft from cryptocurrency exchange Binance, Aave—a decentralized lending app where users deposit digital coins as collateral to borrow others without a bank—is debating new automated limits on how fast money can be borrowed. Whether these new rules can stop a fast-moving attacker without penalizing ordinary borrowers remains uncertain, as risk managers have yet to agree on parameters that pass both tests.

On October 29, 2026, a wallet linked to the Binance attackers deposited $60 million in Tether's USDT, a dollar-pegged digital coin that its issuer can freeze, into Aave. Within just over three minutes, the wallet borrowed 19,762 wrapped ether, or WETH, worth $44.6 million, and converted it into standard ether, a cryptocurrency with no central company able to freeze it. Aave's software was not hacked; it simply followed its automated rules.

Aave's emergency guardians did not begin freezing markets until 41 minutes after the final loan, and the specific Ethereum V3 Core pool used by the attacker was not frozen for 46 minutes. Because the borrowed ether was backed by $60 million in USDT collateral, Aave avoided financial loss when ether's price rose on November 4 and an automated liquidator repaid half the debt in exchange for $24.38 million of the collateral. However, the episode exposed a timing gap that Aave's risk manager, LlamaRisk, and independent contributors are now trying to close through borrowing speed limits or collateral waiting periods.

Previously in this story

How it unfolded

01

Binance's stolen assets reach permissionless lending

2026-10-29 – 2026-10-29

The crisis began at 20:05 UTC on October 29, 2026, when attackers broke into Binance's online wallets and began draining roughly $6.34 billion in cryptocurrency. By 20:57:59 UTC, part of those stolen funds arrived at Aave, turning an exchange security breach into an immediate stress test for decentralized lending.

Blockchain records confirm the timeline. Aave acknowledged the incident at 22:44 UTC, and LlamaRisk published the first detailed breakdown early on October 30, showing how quickly stolen funds moved into automated credit markets.

1 source
02

Two deposits, two loans, three minutes

2026-10-29 – 2026-10-29

To keep the stolen money, the attacker needed to trade USDT—which Tether can blacklist—for ether, which has no central authority. Aave made this easy because its software lets anyone deposit collateral and borrow immediately.

At 20:52:59 UTC, an attacker-controlled wallet received 190 million USDT. Five minutes later, it deposited 10 million USDT into Aave and borrowed 3,271.43 ether after 72 seconds. It then deposited another 50 million USDT and borrowed 16,490.99 ether just 48 seconds later. In three minutes, the wallet used $60 million in stolen USDT to walk away with 19,762.42 WETH, making an automated safeguard look urgent.

6 sources
03

The emergency freeze loses the race

2026-10-29 – 2026-10-29

Spotting a theft is much faster than stopping funds inside automated software. At 21:02:35 UTC, the attacker's wallet sent 23,314.5 ETH—including the fresh Aave loan—to another address. Tether blacklisted the wallet twelve seconds too late, and because the USDT was already locked inside Aave's shared pool, blacklisting the wallet could not freeze the deposit.

Aave's emergency guardians began freezing markets at 21:42:11 UTC on its newer V4 system, and froze the affected V3 Core market at 21:47:23 UTC—46 minutes and 24 seconds after the final loan. By then, the borrowed ether was long gone, proving manual emergency interventions cannot match automated speed.

6 sources
04

A broad defense creates costs for innocent borrowers

2026-10-30 – 2026-11-02

Fearing the thief would use other stolen tokens across different pools, Aave's emergency team—including Aave Labs, LlamaRisk, TokenLogic and Certora—froze 175 lending pools on V3 and 117 on V4. While users could still repay loans, they could not add collateral to protect against market swings, and risk managers cut $3.7 billion in unused V3 borrowing capacity.

When markets reopened on October 30, stablecoins like USDT and USDC remained blocked from serving as loan collateral, and the FBI later linked the theft to North Korea's TraderTraitor group. Broad lockdowns protected the platform, but the collateral freeze frustrated innocent users and made a targeted, automated alternative far more attractive.

6 sources
05

The abandoned loan survives its first liquidation

2026-11-04 – 2026-11-05

The thief abandoned the Aave account, leaving $60 million in USDT collateral exposed to market rules. When ether's price climbed on November 4, the loan became too risky under Aave's automated thresholds, triggering a partial liquidation—a process where third parties repay part of a risky debt in exchange for discounted collateral.

An independent liquidator repaid 9,884.42 WETH, roughly half the debt, and claimed $24.38 million in USDT. Aave suffered zero financial loss, and on November 4, LlamaRisk chief executive Adam Sadowski revealed work on automated borrowing speed limits to slow future attackers without halting entire markets.

5 sources
06

From cooldown proposals to an automated borrowing brake

2026-11-09 – 2026-11-11

Two competing solutions soon emerged in Aave's public governance forums. On November 9, a community member proposed Aave Security Shield, an idea to study waiting periods before new collateral can be used for loans, while avoiding universal 24-hour delays or user identity checks.

Two days later, LlamaRisk released a formal plan called LlamaGuard Caps, proposing a $25 million borrowing buffer that refills every 30 minutes at the pool level so thieves cannot bypass it using multiple wallets. Yet LlamaRisk's own historical replay revealed a flaw: the attacker could still have drained the full $44.6 million within 31 to 36 minutes—before Aave's actual freeze occurred.

5 sources
07

The three-minute test exposes the unresolved compromise

2026-11-13 – 2026-11-14

By November 14, Aave contributors narrowed the problem to a clear trade-off between stopping fast thefts and serving regular borrowers. A strict waiting period on newly deposited collateral—giving zero borrowing power during the first 72 seconds—would have stopped both of the attacker's October 29 loans.

In contrast, LlamaRisk's $25 million cap and 30-minute refill only slowed the drain, while tighter caps like a 60-minute wait would delay legitimate large borrowers, who took out 68 ether loans of at least $25 million over the past year. Meanwhile, ordinary users remained locked out of using stablecoins as collateral, keeping pressure on Aave to find a workable compromise.

5 sources

Where things stand

As of November 15, 2026, the blockchain record of the October 29 loan is settled, but Aave has not adopted a permanent fix. The attacker used $60 million in stolen USDT to borrow 19,762.42 WETH in three minutes, roughly 41 minutes before Aave's first emergency freeze and 46 minutes before the affected V3 Core market was paused. Half the loan was repaid via liquidation on November 4, and as of November 14, the remaining position held 35.61 million USDT against 9,890 WETH of debt with zero lender losses.

Designing a preventive control that blocks thieves without hurting honest traders remains an open engineering problem. A collateral waiting period longer than 72 seconds would have stopped the October 29 loans, whereas LlamaRisk's proposed $25 million borrowing buffer with a 30-minute refill would have allowed the full $44.6 million draw within 31 to 36 minutes—still ahead of Aave's emergency response.

LlamaRisk estimates its proposed limits would create about 162 hours of borrower wait times per year across 68 large WETH loans, with a maximum queue of 6.7 hours, while special exemptions for institutional traders risk creating new loopholes. Before any system goes live, Aave must publish final parameters, complete security audits, hold community votes and lift the ongoing restrictions on stablecoin collateral.

Sources