Cashera Hack
Incident Overview
Cashera was rug pulled by token deployer for the total amount of nearly $USD 90,000.
Cashera is BEP20 standard token. The Rug pull occurred after the token deployer minted 23,000,000 $CSR tokens and swapped them. It caused the token price drop by more than 70%.
Incident happened due to centralization and privileged issues of the token contract.
Address of scammer: https://bscscan.com/address/0xbaa0c352…801344
Affected contract:
https://bscscan.com/address/0x7ee05842…cf70cc
Mint transactions:
https://bscscan.com/tx/0xe7e568a8…8c1867
https://bscscan.com/tx/0x5dbc2050…a38560
0x81d3ec77438b4e99aa99ba25b1dbc3fea317fe3b0x81d3ec77438b4e99aa99ba25b1dbc3fea317fe3b
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 Cashera, these are the critical security checks that could have prevented this incident (May 2022).
- 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 TrialSecurity Audit History
- Audit Report 1 Report
Sources & References
-
01
Source 1 https://archive.is/m15rz
Learn to Prevent the Next Cashera
The Cashera 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.