Incident Overview
On March 17 2025 the Arcade Token on BSC was exploited due to a vulnerability in its public signer mechanism with a loss of about 5k USD.
The contract had an insecure public signer verification system, making it susceptible to signature replay attacks. The attacker exploited this by crafting valid signatures that the contract mistakenly recognized as legitimate, allowing them to mint and transfer tokens without proper authorization. As a result, a significant amount of funds were drained.
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 Arcade, 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 TrialRelated Attack Classes
The technique used in this hack maps to these vulnerability classes in our security curriculum:
Sources & References
Learn to Prevent the Next Arcade
The Arcade 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.