Incident Overview
About 1.5 million coins were stolen after hackers tampered with a glitch at currency exchange company Crypto Rush.
The hack involved temporarily inflating the amount of coins available in accounts by about 22 million, then withdrawing the coins from the exchange.
“Once again we apologize for our own issues with both downtime and late upgrades of the client,” a representative of Crypto Rush said in a forum post. “We’ll post more when we know how we can pay back affected users or get some compensation for this massive, massive loss. 100 BTC doesn’t just come out of thin air, so please be patient while we make this right.”
Incident Report
Protocol Information
Market Context at Time of Hack
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 Crypto Rush, these are the critical security checks that could have prevented this incident (March 2014).
- 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 TrialSources & References
Learn to Prevent the Next Crypto Rush
The Crypto Rush 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.