Incident Overview
The exploiter's address:
https://arbiscan.io/address/0x9b1acd43…d48e68
The example of the transaction:
https://arbiscan.io/tx/0x37222d3a…a89269
The protocol was exploited in several transactions, leading to more than 100 NFTs being stolen from different collections of Treasure Marketplace.
The exploiter:
- called buyItem() with valid NFT token and NFT ID, but with the invalid 0 quantity
- Treasure Marketplace sells the NFT but charges 0 MAGIC (due to 0 quantity)
The hack is made possible due to a bug in distinguishing ERC721 and ERC1155 in buyItem(), which miscalculates the price of ERC721 as ERC1155 with the given 0 quantity.
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 TreasureDAO, these are the critical security checks that could have prevented this incident (March 2022).
- Verify all logic paths related to Other are guarded by proper access controls and input validation
- 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 TrialSources & References
Learn to Prevent the Next TreasureDAO
The TreasureDAO 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.