Attacker Borrowed $44.6M in ETH Against $60M USDT 

Attacker Borrowed $44.6M in ETH Against $60M USDT 


On October 29, 2026, decentralized lending protocol Aave froze new deposits and borrowing across most of its V3 and V4 markets after wallets linked to a large outflow from Binance hot wallets used the platform to convert freezable stablecoins into ether. 

The move highlights how permissionless lending pools can function as rapid conversion mechanisms during large-scale incidents, even when the protocol itself remains uncompromised. Community voices, including prominent Aave contributor Marc Zeller, have emphasized that the resulting position poses limited systemic risk. 

Aave Position, Conversion Mechanics, and Precautionary Freeze

Between 20:58 and 21:01 UTC—roughly 40 minutes before Aave’s first freeze action—one wallet associated with the activity supplied 60 million USDT to Aave V3 Ethereum Core and borrowed 19,762 WETH, valued at about $44.6 million at the time. 

According to Aave’s detailed risk response posted on its governance forum, this was the only such position linked to the cluster across all networks and versions. The position held approximately $59.9 million in USDT collateral against roughly $43.8 million in debt, remaining overcollateralized and subject to normal liquidation rules. The forum update stated that it “does not put Aave suppliers at risk” and that no further interactions with Aave occurred after 21:01 UTC.

This sequence illustrates how a lending protocol can serve as an unofficial conversion route. Once the USDT was deposited into Aave’s contracts, it resided in the protocol’s pool rather than solely under the depositor’s direct control. Borrowing WETH against it allowed the extraction of non-freezable ether drawn from the shared liquidity of other users’ deposits. 

LlamaRisk, a risk service provider working with Aave Labs and others, confirmed in its own statement that all Aave V3 and select V4 markets were frozen to new exposure as a precaution, with existing positions unaffected, liquidations continuing normally, and user funds described as safe. The governance forum explained the breadth of the action: the group, which included Aave Labs, TokenLogic, and Certora, decided on a full freeze because the funds could be swapped into any listed asset, and a freeze could be reversed by the guardian without a multi-day governance vote required for other restrictions. 

In total, 175 reserves were frozen on V3 across 16 networks and 117 on V4 across four networks. Horizon RWA markets were left open due to their permissioned collateral. Markets were to remain frozen until funds ceased significant movement and clearer containment details emerged from Binance, followed by a staged unfreeze.

Community Assessment and Parallels to Prior Incidents

Marc Zeller, a longstanding Aave community contributor, addressed the situation directly on X shortly after the freeze, stating: “Aave protocol will be fine.” He noted that the borrower supplied 60 million USDT and borrowed 19,762 wETH (approximately $44.9 million) in three minutes—before Tether froze the address and before the Aave Guardian acted 46 minutes later. 

Zeller highlighted that the position remains overcollateralized with a health factor of 1.04, holding $59.9 million in collateral against $44.9 million in debt. Liquidation would trigger if ETH rises above roughly $2,365 (about 4% higher at the time of his post), and the debt represents only about 0.9% of the 2.16 million wETH available in the Aave V3 Core reserve. He argued there is no need for special action against the position, as normal liquidations can handle it, available wETH liquidity is sufficient to support withdrawals without a bank run, and the situation is far less severe than the earlier Kelp DAO incident involving zero-value collateral.

The episode echoes Aave’s handling of the April 18, 2026 Kelp DAO LayerZero bridge exploit, in which unbacked rsETH was deposited as collateral and used to borrow substantial WETH, creating bad debt that required coordinated recovery efforts, market freezes, and later liquidations via governance. Aave’s approach then similarly emphasized that its own contracts were not exploited and focused on containing exposure through freezes and subsequent restoration of backing. In the current case, the protocol has stressed continuous tracking of the relevant wallet cluster on Ethereum and other chains, monitoring of Chainlink price feeds, and real-time oversight for any further interactions. 

Binance Hot Wallet Outflows and Issuer Freezes

At approximately 20:24 UTC on October 29, significant amounts of cryptocurrency began moving from Binance-labeled hot wallets across multiple chains. Binance’s official support announcement stated that its initial investigation suggests the incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. 

The exchange reported finding no evidence of any wallet private key leak and estimated the total impact at around $6.3 billion. Binance stated it had worked with blockchain partners to freeze affected assets, with approximately $3 billion frozen on-chain so far, and pledged that “Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe.” Deposits and withdrawals were temporarily suspended while security checks proceeded.

Tether CEO Paolo Ardoino confirmed on X that the company froze more than 1.567 billion USDT related to a potential Binance exchange hack, writing that “Protecting the industry and our partners is our main priority.” Circle and other issuers took parallel action on assets linked to the same activity. These freezes targeted freezable stablecoins still held at identified addresses, though portions of USDT had already been moved or converted before blacklists took full effect. 

Binance has said it is engaged with law enforcement and blockchain intelligence partners to trace and recover funds, and it plans to publish an updated Proof of Reserves once remediation is complete. 

As of early October 30 (6:10 AM UTC) updates, Aave continued to monitor utilization rates on frozen reserves, noting that large withdrawals could increase borrow rates while repayments reduce them, with unfreeze sequencing informed by these dynamics. No markets were fully paused, preserving the ability for users to exit or adjust existing positions. 

The incident underscores the dual nature of decentralized lending infrastructure: it provides efficient, non-custodial liquidity for ordinary users while also offering a fast, permissionless path for converting assets that centralized issuers can freeze. 

Aave’s rapid coordination with service providers limited additional exposure in this instance, consistent with its prior risk responses. Users and observers are directed to official Aave and Binance channels for the latest status as the investigation and staged reopening proceed.

Also read: Binance Hack: $6.3B Impact, $3B Frozen After DevOps Laptop Breach


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.





Leave a Reply

Your email address will not be published. Required fields are marked *