The R0AR Hack

TOTAL LOST $790K
Low Access Control

Summarize with AI

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

Incident Overview

On April 16, 2025, The R0AR staking contract was exploited due to a backdoor vulnerability, leading to the loss of approximately $790,000.

The attack stemmed from a maliciously embedded backdoor in the staking contract during its deployment. Specifically, the attacker preset the user.amount mapping for their wallet (0x8149f775…48401F) to a large value directly in the contract's storage. This manipulation gave the appearance that the wallet had staked a substantial number of tokens.

Later, by invoking the emergencyWithdraw() function, the attacker was able to withdraw 100 million $1ROR tokens from the contract. This withdrawal was possible despite the tokens never actually being staked, resulting in the full drain of the contract's funds. The vulnerability highlights poor storage initialization and the absence of proper validation checks on state variables at contract deployment.

Incident Report

Protocol / Project The R0AR
Date of Incident
Attack Technique Access Control
Classification Other

Protocol Information

Protocol Type Exploit/Access control
Official Website www.r0ar.io/
Protocol Twitter/X @th3r0ar
Team Anonymous
Source Code Unverified

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 The R0AR'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 The R0AR, these are the critical security checks that could have prevented this incident (April 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 The R0AR

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