Incident Overview
Bitmarket, a Polish cryptocurrency exchange, abruptly ceased operations due to a loss of liquidity.
In the days leading up to the cessation of operations, Bitmarket enforced mandatory changes to user passwords and API keys. Additionally, all withdrawals were halted under the pretext of additional KYC requirements. The abrupt closure of the exchange left users in the dark, with many speculating about the possible reasons behind the sudden loss of liquidity.
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 Bitmarket, these are the critical security checks that could have prevented this incident (July 2019).
- Verify all logic paths related to Rugpull 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 Bitmarket
The Bitmarket 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.