Munchables Hack

TOTAL LOST $62.5M
High #105 All-Time Storage Slot Exploit / Access Control blast

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain blast Incident surface
Recovered $62.5M 100.0% returned
All-Time Rank #105 By amount stolen
Protocol Type Farm Target category

Incident Overview

Quick Summary

Munchables protocol has been compromised and drained for 17.4K ETH ($62.5M)

Details of the Exploit

Before the attack munchables contract 0x29958E used Upgradeable proxy patterns with unverified source code, thus we can't be sure if this was a rug pull event or access control vulnerability. The exploiter called function 0x7eee288d directly on the victim contract and withdrew ether. After a short period, all funds were returned to the protocol-related multi-signature wallet.

Block Data Reference

Attacker:

https://blastscan.io/address/0x6e8836f0…3d09c5

Exploit tx:

https://blastscan.io/tx/0x9a7e4d16…f55c95

Unverified proxy implementation:

https://blastscan.io/address/0xf563Ce43…42aFcd

Proxy admin:

https://blastscan.io/address/0x87684Be6…dAD153

This is classified as a Access Control Attacks . Compare similar hacks →

Incident Report

Protocol / Project Munchables
Date of Incident
Affected Chain(s) blast
Attack Technique Storage Slot Exploit / Access Control
Classification Protocol Logic / Other
Primary Source View Post-Mortem

Protocol Information

Protocol Type Farm
Smart Contract Language Solidity
Official Website www.munchables.app/
Protocol Twitter/X @_munchables_
Team Anonymous
Source Code Unverified

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 Operational-security tradecraft (phishing, malware, leaked seed phrases, or insider access) to obtain treasury signing authority
Capital Required Minimal capital - only enough to cover gas while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised wallets / multisig signers, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of Munchables's high-value treasury accounts and the authority / multisig structure controlling them
Execution Speed Speed to drain the compromised accounts before the team detects the breach and revokes signing authority or freezes the assets
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 Storage Slot Exploit / Access Control audit checklist and test coverage

If you're auditing a protocol with similar architecture to Munchables, these are the critical security checks that could have prevented this incident (March 2024).

  • Verify all logic paths related to Storage Slot Exploit / 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 Trial

Funds Recovery

100.0%

Recovered

$62.5M

Net Loss

0

Related Attack Classes

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

See all Access Control Attacks examples →

Access Control Attacks

Sources & References

Learn to Prevent the Next Munchables

The Munchables 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