Cashera Hack

TOTAL LOST $90K
Low Rugpull

Summarize with AI

Affected Chain 2022 Incident surface
Recovered - No recovery reported
All-Time Rank #1561 By amount stolen
Auditors 1 Prior security audit

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 / Project Cashera
Date of Incident
Attack Technique Rugpull
Classification Token
Primary Source View Post-Mortem

Protocol Information

Protocol Type Bridge
Affected Token CSR
Official Website cashmere.exchange/
Protocol Twitter/X @cashmerelabs
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Solana Ecosystem Pump Fun Ecosystem

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.

Technical Knowledge Deep understanding of rugpull and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Cashera's contract logic - root cause: token
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Hard to catch — private key / OpSec failures are outside smart contract audit scope
Audited by Audit Report 1 — still lost $90K. Prior audits don't guarantee safety, especially after post-audit code changes.

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 Trial

Security Audit History

Sources & References

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.

Recreate exploit patterns safely Free Trial