Meebits Hack
Incident Overview
The exploiter's address:
https://etherscan.io/address/0x009988ff…74933e
The exploiter's smart contract:
https://etherscan.io/address/0x270ff230…d46ffb
Affected NFT smart contract:
https://etherscan.io/address/0x7bd29408…716bc7#code
Minting function in NFT uses pseudo randomization depends on block values:
uint index = uint(keccak256(abi.encodePacked(nonce, msg.sender, block.difficulty, block.timestamp))) % totalSize.
It means close to zero randomnesses of the returned index. The exploiter has used a bot and deployed a contract to interact with the NFT contract. The exploiter used open information which exactly what metadata he should receive to sell NFT with the highest profit. If the bot minted an undervalued NFT, the bot reverted the transaction. This vulnerability allowed exploiter minting predictable expensive NFTs.
Incident Report
Protocol Information
Market Context at Time of Hack
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 Meebits, these are the critical security checks that could have prevented this incident (May 2021).
- 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 Meebits
The Meebits 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.