Incident Overview
Jul-26-2024 Abandoned Karastar project was drained for about $69k USD.
On Jul-26-2024 Karastar GameFi contracts were drained with losses of about 120BNB. Exploiter upgraded a few implementations and used a backdoor function for token stealing: transfer(address token, address fromUser, uint256 value).
Proxy upgrade tx:
https://bscscan.com/tx/0x289a3107…909b61
Drain TX:
https://bscscan.com/tx/0x50cc6e73…922373
Funds held by:
https://bscscan.com/address/0x2b8D9E63…F05a6A
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 Karastar, these are the critical security checks that could have prevented this incident (July 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 Karastar
The Karastar 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.