M2 Exchange Hack

TOTAL LOST $13.7M
High Access Control Exploit bitcoin ethereum solana

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain bitcoin 3 chains affected
Recovered - No recovery reported
All-Time Rank #266 By amount stolen
Auditors 2 Prior security audits

Incident Overview

O2 is a high-performance, fully onchain spot orderbook on Ignition, a rollup powered by the Fuel Virtual Machine. It offers a CEX-like trading experience with DEX security (self-custody, no KYC) and ultra-low fees. It supports multichain deposits and withdrawals and has a highly performant API for programmatic traders

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

Incident Report

Protocol / Project M2 Exchange
Date of Incident
Affected Chain(s) bitcoin ethereum solana
Attack Technique Access Control Exploit
Classification Protocol Logic
Primary Source View Post-Mortem

Protocol Information

Protocol Type Dexs
Official Website o2.app
Protocol Twitter/X @o2dotapp

Market Context at Time of Hack

Token Categories
Base Ecosystem Mode Ecosystem
Protocol Links
GitHub Discord

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 Solana network fees while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised stake accounts and treasury wallets, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of M2 Exchange'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 Access Control Exploit audit checklist and test coverage
Audited by Audit Report 1, Audit Report 2 — still lost $13.7M. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • Verify all logic paths related to Access Control Exploit 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

Security Audit History

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

Browse all hacks

These hacks used the same attack technique. Understanding the pattern helps prevent future exploits.

Radiant V2 $53.0M
Access Control Exploit
WXETA $110K
Access Control Exploit
OKX NFT Aggregator $14K
Access Control Exploit
YOLO Games $1.5M
Access Control Exploit
Ara Finance $131K
Access Control Exploit
Gamma $8.2M
Access Control Exploit

Learn to Prevent the Next M2 Exchange

The M2 Exchange 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