# Binance Hot Wallet Exploit: Aave's Response

**URL:** <https://governance.aave.com/t/binance-hot-wallet-exploit-aaves-response/25954>\
**Category:** Risk\
**Created:** [October 30, 2026, 12:59am UTC](https://governance.aave.com/t/binance-hot-wallet-exploit-aaves-response/25954 "2026-10-30T00:59:32Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![submitblock](https://avatars.discourse-cdn.com/v4/letter/s/ba9def/32.png) [@submitblock](https://governance.aave.com/u/submitblock)\
**Post date:** [October 30, 2026, 2:39am UTC](https://governance.aave.com/t/binance-hot-wallet-exploit-aaves-response/25954/5 "2026-10-30T02:39:45Z")

</div>

This is probably an overreaction. 60 million isn’t anywhere close enough to effect Aave’s stability. Aave obviously completely trusts Circle, Tether, etc so this is their problem, following the rules of crypto/defi if they were too slow to issue an erc20.burn() on the exploiter’s addresses, that’s on them and the exploiter followed all defi rules/protocol and their borrow was valid. Hyperliquid continues as normal and they have similar TVL as Aave and just as much, if not more, USDC exposure. High probability that these hacks will continue happening, if your solution is shutdown, freeze, scare everyone into withdrawing, etc every few months then aave, especially aavev3, centralized model is inferior to morpho.

---

_[View the full topic](https://governance.aave.com/t/binance-hot-wallet-exploit-aaves-response/25954)._
