Sources
Loading...
Additional media
Loading...
DeepNewz, mobile.
People-sourced. AI-powered. Unbiased News.
A peripheral contract linked to Aave was hacked due to an arbitrary call or logic error, but the core Aave protocol and user funds remain unaffected. The exploit targeted a UI peripheral contract used for swaps, and the extracted funds were leftovers from successful swaps. The incident did not compromise user funds or pose any risk to approvals. Aave users and the protocol are safe, and there is no need to activate the Aave safety module. The hack involved positive slippage dust accumulation from "repay with collateral" Paraswap integration.
A few hours ago, someone raided a peripheral sc linked to positive slippage dust accumulation from "repay with collateral" Paraswap integration. The Aave protocol & Aave users are safe, and no funds are at risk. There's no need to use the Aave safety module. More info here 👇 https://t.co/w6HQXjpPMN
TLDR: - No user funds affected in any way and no risk with approvals - what was compromised is not the Aave protocol but a UI peripheral contract used for swaps - funds extracted were leftovers from successful swaps (needed to minimize failed txs) accumulated for a *long* time https://t.co/OXevikqHmO
Today, a series of transactions across different networks were detected showing what it looked like an exploit on some Aave peripheral contracts (not part of the Aave Protocol itself). Before any further detailed report, we would like to clarify the following for transparency…
