MOKE Token Hack

TOTAL LOST $907K
Low Access Control

Summarize with AI

Affected Chain 2026 Incident surface
Recovered - No recovery reported
All-Time Rank #866 By amount stolen
Protocol Type Exploit/Access control Target category

Incident Overview

On August 2, 2026, the MOKE token protocol on BNB Chain was exploited for approximately $907,700 (~1,546 BNB) due to a critical access control flaw in its smart contract architecture.

The exploit was caused by an unprotected public claim() function within the MokeToken.releaseContract() contract, which lacked caller eligibility checks or role-based access control. The attacker repeatedly called claim() to drain roughly 166 million MOKE tokens directly from the protocol's internal reserve pool. To realize their profit, the attacker combined flash loans, Venus Protocol leverage, liquidity pool removal, and internal dividend distribution mechanics to swap the extracted tokens into 1,546 BNB.

Attack Transaction: 0x0776048b…756a8f

Incident Report

Protocol / Project MOKE Token
Date of Incident
Attack Technique Access Control
Classification Token

Protocol Information

Protocol Type Exploit/Access control
Official Website moketoken.com/
Protocol Twitter/X @cowsgonemad
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Solana 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 Operational-security tradecraft (phishing, malware, leaked seed phrases, or insider access) to obtain treasury signing authority
Capital Required Minimal capital - only enough to cover gas while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised wallets / multisig signers, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of MOKE Token's high-value treasury accounts and the authority / multisig structure controlling them
Execution Speed Speed to drain the compromised accounts before the team detects the breach and revokes signing authority or freezes the assets
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 Access Control audit checklist and test coverage

If you're auditing a protocol with similar architecture to MOKE Token, these are the critical security checks that could have prevented this incident (August 2026).

  • 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 Trial

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Access Control Attacks examples →

Proof-of-Concept Exploits

1 PoC available

Sources & References

Learn to Prevent the Next MOKE Token

The MOKE Token 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