Incident Overview
Because of the weak password storage system at Mt. Gox, users who used the same password for both MyBitcoin and Mt. Gox were infiltrated and significant amounts of assets were lost there too.
By MyBitcoin's estimation, about 1% of all users were affected by the security breach/ incident/ illegal hack.
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 MyBitcoin, these are the critical security checks that could have prevented this incident (June 2011).
- 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 MyBitcoin
The MyBitcoin 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.