Aave Protocol Hack

TOTAL LOST $1.2M
Medium Phishing

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain 2023 Incident surface
Recovered - No recovery reported
All-Time Rank #795 By amount stolen
Protocol Type Synthetics Target category

Incident Overview

Quick Summary

A user's Aave Protocol assets were stolen using phishing attack, which resulted in a loss of 1,201,576 $USD.

Details of the Exploit

A user approved trading for four different tokens of Aave Protocol, such as $aArbWETH, $aFanWETH, $aArbWBTC and $aFanUSDC, possible via phishing attack. The attacker took the assets and then swapped them into 1,201,576 $USDC using four smart contract with unverified source code, and than all selfdestructed. The funds were transferred through Celer Bridge.

Block Data Reference

Attacker addresses:

https://arbiscan.io/address/0x053a85c5…8408d1

https://arbiscan.io/address/0x0a009741…f00012

Malicious transaction:

https://arbiscan.io/tx/0x3c79b996…4a2467

Approval transaction:

https://arbiscan.io/tx/0x4d8ecb31…e54ed1

This is classified as a Phishing Attacks . Compare similar hacks →

Incident Report

Protocol / Project Aave Protocol
Date of Incident
Attack Technique Phishing
Classification Borrowing and Lending
Primary Source View Post-Mortem

Protocol Information

Protocol Type Synthetics
Official Website www.ravenprotocol.com/
Protocol Twitter/X @ArableProtocol
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
AI & Big Data BNB Chain Ecosystem
Protocol Links

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of phishing and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Aave Protocol's contract logic - root cause: borrowing and lending
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Likely — with a thorough Phishing audit checklist and test coverage

If you're auditing a protocol with similar architecture to Aave Protocol, these are the critical security checks that could have prevented this incident (April 2023).

  • Verify all logic paths related to Phishing are guarded by proper access controls and input validation - see the Phishing Attacks attack class for patterns
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Phishing Attacks examples →

Phishing Attacks

Sources & References

Browse all hacks

These hacks used the same attack technique. Understanding the pattern helps prevent future exploits.

USDC Permit Signature Phishing $1.8M
Phishing
Social Engineering Scam $282M
Phishing
Address Poisoning Attack $50.0M
Phishing
Zerobase $240K
Phishing
MUBARA $55K
Phishing
Venus $13.0M
Phishing

Learn to Prevent the Next Aave Protocol

The Aave Protocol hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Start Free Trial Browse Attack Library
Recreate exploit patterns safely Free Trial