ACB Hack

TOTAL LOST $60K
Low Other

Summarize with AI

Affected Chain 2025 Incident surface
Recovered - No recovery reported
All-Time Rank #1676 By amount stolen
Protocol Type Exploit/Other Target category

Incident Overview

On April 23, 2025, the ACB token on BNB Chain was exploited through an airdrop vulnerability, resulting in losses of approximately $60,000.

The attacker, funded via Tornado Cash, exploited a vulnerability in the ACB token’s airdrop mechanism that allowed them to claim rewards multiple times, draining the airdrop contract. The exploit involved abusing a cash exploit flaw without proper eligibility or duplication checks. After successfully extracting around $60,000, the attacker moved the stolen funds back to Tornado Cash to obfuscate their trail.

The compromised contract was a proxy pointing to a vulnerable implementation contract, and the exploit has been confirmed as fully executed.

Incident Report

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

Protocol Information

Protocol Type Exploit/Other
Official Website ab.org
Protocol Twitter/X @ABDAO_Global
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Mineable Marketplace Enterprise Solutions BNB Chain Ecosystem Binance Alpha Binance Alpha Airdrops Binance 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 other 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 ACB'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? Likely — with a thorough Other audit checklist and test coverage

If you're auditing a protocol with similar architecture to ACB, these are the critical security checks that could have prevented this incident (April 2025).

  • Verify all logic paths related to Other 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

Sources & References

Learn to Prevent the Next ACB

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