Incident Overview
The attackers exploited a leak inside the lending protocol that allowed them to initiate loans under users’ collateral.
The examples of the attacker’s transaction:
https://www.bscscan.com/tx/0x2a389d05…2f1355
https://www.bscscan.com/tx/0x636c6829…935fc8
The project’s contract was attacked by the following addresses:
Incident Report
Protocol Information
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.
What Auditors Should Check
If you're auditing a protocol with similar architecture to Maze Protocol, these are the critical security checks that could have prevented this incident (August 2021).
- Verify all logic paths related to Other are guarded by proper access controls and input validation
- 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 TrialFunds Recovery
Recovered
$3.8M
Net Loss
200000
Security Audit History
- Certik Report
Sources & References
Learn to Prevent the Next Maze Protocol
The Maze Protocol 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.