M2 Hack

TOTAL LOST $13.7M
High Access Control

Summarize with AI

Affected Chain 2024 Incident surface
Recovered - No recovery reported
All-Time Rank #266 By amount stolen
Protocol Type Exploit/Access control Target category

Incident Overview

On October 31, 2024, the centralized cryptocurrency exchange M2, endorsed by David O'Leary and based in Abu Dhabi, experienced a hack resulting in a $13.7 million loss from multiple hot wallets.

The October 31 attack targeted M2’s hot wallets, resulting in the unauthorized transfer of Bitcoin, Ether, and Solana assets valued at nearly $13.7 million. According to on-chain investigator ZachXBT, the breach was carried out by attackers leveraging a vulnerability within the exchange’s online wallet infrastructure. The stolen assets were transferred away from M2’s wallets over a brief period, despite the exchange's swift response to prevent further escalation.

M2 immediately suspended affected wallets, activated additional security controls, and restored user funds, resuming normal operations shortly after. This quick action limited the duration of exposure, though the initial vulnerability remains under investigation, with further insights expected as M2 collaborates with cybersecurity and law enforcement agencies.

Incident Report

Protocol / Project M2
Date of Incident
Attack Technique Access Control
Classification CeFi

Protocol Information

Protocol Type Exploit/Access control
Official Website m2.com/
Protocol Twitter/X @m2exchange
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Ethereum Ecosystem

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 M2'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 audit checklist and test coverage

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

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

Related Attack Classes

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

See all Access Control Attacks examples →

Sources & References

Learn to Prevent the Next M2

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

Recreate exploit patterns safely Free Trial