Incident Overview
The malicious actor sent emails to OpenSea users, which contained information about fake migration to the new contract. In total, 17 users became victims of email fishing.
The malicious actor's address:
https://etherscan.io/address/0x3E0DeFb8…7A8A74
Stolen NFTs list:
https://docs.google.com/spreadsheets/d/1XQNIXuAl2E1XO_cP8pm_vbzskI_Pka4E5sizfcrLITM/edit#gid=0
Stolen NFTs were sold out on LooksRare marketplace, the example transactions:
https://etherscan.io/tx/0xd910c67a…989221
https://etherscan.io/tx/0x9a9bb48a…71e8ee
https://etherscan.io/tx/0x70c8622c…e360f9
Stolen funds were deposited into the Tornado Cash mixer:
https://bloxy.info/txs/transfers_from/0x3e0defb8…7a8a74?currency_id=1
Incident Report
Protocol Information
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.
What Auditors Should Check
If you're auditing a protocol with similar architecture to OpenSea, these are the critical security checks that could have prevented this incident (February 2022).
- Verify all logic paths related to Access Control are guarded by proper access controls and input validation - see the Access Control 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 TrialRelated Attack Classes
The technique used in this hack maps to these vulnerability classes in our security curriculum:
Sources & References
Learn to Prevent the Next OpenSea
The OpenSea 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.