CheddaToken Hack

TOTAL LOST $1.2M
Medium Rugpull

Summarize with AI

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

Incident Overview

CheddaToken was rugged by the privileged role. The CHEDDA token was dumped with losses of about 1.2M $USD,

The function `emergencyRewardWithdraw` was invoked by the owner. It allows the caller to take off the available CHEDDA token balance in the MasterChef. After that the tokens were sold which led to significant price dumping.

Onwer addresses:

https://etherscan.io/address/0xb0d51fb4…8d97e3

emergencyRewardWithdrawΒ  transaction:

https://etherscan.io/tx/0xff904928…2b5733

https://etherscan.io/tx/0x685b3d39…25608d

Incident Report

Protocol / Project CheddaToken
Date of Incident
Attack Technique Rugpull
Classification Token
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exit Scam/Rugpull
Affected Token CHEDDA
Official Website www.a-ha.io/
Protocol Twitter/X @CheddaToken
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Web3

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 CheddaToken'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 Certik β€” still lost $1.2M. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to CheddaToken, these are the critical security checks that could have prevented this incident (April 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

  • Certik 2022-02-15 Report unavailable

Sources & References

Learn to Prevent the Next CheddaToken

The CheddaToken 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