MAID Hack

TOTAL LOST $166K
Low Access Control

Summarize with AI

Affected Chain 2025 Incident surface
Recovered - No recovery reported
All-Time Rank #1357 By amount stolen
Protocol Type Staking Pool Target category

Incident Overview

On March 13, 2025, the $MAID token suffered a private key leak, allowing an attacker to mint 0x10000000000000000000000000 MAID tokens and swap them for 89 ETH ($166K). The deployer wallet was also drained, increasing the total loss to 101 ETH ($190K). Funds were dispersed to four different addresses.

The attacker used the compromised deployer wallet to mint 0x10000000000000000000000000 MAID tokens and immediately swapped them for 89 ETH ($166K). Additionally, the deployer wallet held 12.4 ETH, which was also drained, bringing the total stolen amount to 101 ETH ($190K). The stolen funds were distributed across four different addresses for further obfuscation.

This incident highlights the critical importance of securing deployer and multisig keys, implementing timelocks or additional security layers for minting functions, and actively monitoring wallet activity to detect suspicious transactions early. There has been no official response from the $MAID team regarding fund recovery or mitigation actions.

Incident Report

Protocol / Project MAID
Date of Incident
Attack Technique Access Control
Classification Token
Primary Source View Post-Mortem

Protocol Information

Protocol Type Staking Pool
Official Website mai.finance/
Protocol Twitter/X @0xLaoZi
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Stablecoin Algorithmic Stablecoin

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 MAID'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 MAID, these are the critical security checks that could have prevented this incident (March 2025).

  • 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 MAID

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