Incident Overview
On October 31, 2024, SUNRAY DEX suffered a private key compromise, allowing an attacker to gain ownership of SUN and ARC tokens. The attacker minted large amounts of these tokens and dumped them, draining DEX liquidity pairs and stealing approximately $2.855M.
The attacker exploited a compromised private key to gain control over token contracts and mint large sums of SUN and ARC tokens. These tokens were then dumped on the market, crashing their value and draining liquidity pools. The stolen funds were consolidated at 0xC4059d92…eccC9A.
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 Sunray, these are the critical security checks that could have prevented this incident (October 2024).
- 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 Sunray
The Sunray 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.