Incident Overview
Radiant v2 introduces a migration to the LayerZero OFT format, improving cross-chain fee sharing, enabling faster launches on additional chains, and allowing native ownership of bridging contracts. This update addresses utility exchange concerns and eligibility for RDNT emissions by implementing changes to core protocol mechanics, emissions, utility, and enhancing cross-chain functionality
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 Radiant V2, these are the critical security checks that could have prevented this incident (October 2024).
- Verify all logic paths related to Access Control Exploit 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 TrialSecurity Audit History
- Audit Report 1 Report
Related Attack Classes
The technique used in this hack maps to these vulnerability classes in our security curriculum:
Sources & References
Learn to Prevent the Next Radiant V2
The Radiant V2 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.