/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Blockchain game Munchables, which offers rewards for looking after digital creatures, loses ~$63M in ETH in a hack; the hacker seems to have returned the funds

- Blockchain-based Munchables game confirmed a security incident  — Munchables declared all user funds safe later the same day

Bloomberg Ryan Weeks

Context & Ripple Effects

Munchables joins a recurring pattern of large crypto-protocol security incidents: Wormhole’s $322M ETH theft and Mixin’s suspension of deposits and withdrawals after a roughly $200M hack both showed how quickly an exploit can disrupt access to user assets.

The apparent return of the ETH and Munchables’ statement that user funds are safe distinguish this episode from incidents that required prolonged operational restrictions. Even so, the breach puts the game’s custody and smart-contract safeguards under immediate scrutiny.

First-order effects

  • Munchables users avoid an apparent loss of roughly $63M in ETH if the returned funds and the project’s safety assessment hold.
  • Munchables must account for the breach and demonstrate that the exploited path is closed before users can treat its reward system as secure.

Second-order effects

  • Players and prospective users are likely to place greater weight on a game’s contract security and asset-handling practices, raising the trust burden for Munchables and comparable blockchain games.
  • The incident reinforces the operational value of rapid containment and asset recovery, a contrast with Mixin’s earlier pause of deposits and withdrawals after its breach.

Third-order effects

  • Repeated high-value exploits can make security assurance and recovery readiness a competitive requirement for consumer-facing crypto products, rather than a back-end technical concern.
  • If such incidents continue, the sector may further separate projects able to preserve user access after a breach from those whose failures force asset freezes or extended disruption.

The trend: Blockchain gaming is part of a broader crypto trend in which consumer adoption increasingly depends on whether protocols can contain security failures without exposing users to lasting losses.

Discussion

  • @_munchables_ @_munchables_ on x
    Munchables has been compromised. We are tracking movements and attempting to stop the the transactions. We will update as soon as we know more.
  • @_munchables_ @_munchables_ on x
    The Munchables developer has shared all private keys involved to assist in recovering the user funds. Specifically, the key which holds $62,535,441.24 USD, the key which holds 73 WETH, and the owner key which contains the rest of the funds.
  • @pacmanblur @pacmanblur on x
    $97m has been secured in a multisig by Blast core contributors. Took an incredible lift in the background but I'm grateful the ex munchables dev opted to return all funds in the end without any ransom required. @_munchables_ and protocols integrating with it like @juice_finance..…
  • @_munchables_ @_munchables_ on x
    The Munchables developer has agreed to share the keys for the full Munchables funds without any condition.
  • @blocksecteam @blocksecteam on x
    The fund is currently in a multisig wallet 0x4D2F75F1cF76C8689b4FDdCF4744A22943c60 48C, with the threshold 2/3. Owners are 0xFfE8d74881C29A9942C9D7f7F55aa0d8049C3 04A, 0xe0C5B8341A0453177F5b0Ec2fcEDc57f6E211 2Bc, 0x94103f5554D15F95d9c3A8Fa05A9c79c62eDB D6f
  • @_munchables_ @_munchables_ on x
    All user funds are safe, lockdrops will not be enforced, all blast related rewards will be distributed as well. Updates to follow in the coming days.
  • @pacmanblur @pacmanblur on x
    big shout out @zachxbt for all his support behind the scenes on this as well!
  • @hsakatrades @hsakatrades on x
    pacman and zachxbt overseeing the unconditional surrender of the hacker [image]
  • @notthreadguy @notthreadguy on x
    zachxbt rn [image]
  • @functi0nzer0 Laurence on x
    When your napkin math tells you that your Blast points are worth more than 62 million dollars
  • @cirrusnft @cirrusnft on x
    Zach played a big role in stopping a $63m exploit today Just sent a small thank you to zachxbt.eth for his services. If you were on Munchables prior to today I suggest you do the same [image]
  • @basedkarbon @basedkarbon on x
    the north korean dev was whitehat rugging [image]