CoinDCX Hack

TOTAL LOST $44.2M
High #141 All-Time Access Control

Summarize with AI

Affected Chain 2025 Incident surface
Recovered - No recovery reported
All-Time Rank #141 By amount stolen
Protocol Type CEX Target category

Incident Overview

July 19, 2025 — Indian exchange CoinDCX suffered a $44 million exploit due to a server breach targeting an internal liquidity account; user funds were not affected and operations continue normally.

The breach occurred at 4 a.m. IST on July 19 when an attacker gained unauthorized access to a CoinDCX liquidity provisioning account used on a partner exchange. The company attributed the incident to a sophisticated server-level compromise, not a smart contract flaw.

Funds were routed through Tornado Cash and bridged between Solana and Ethereum before being dispersed across several wallets. The attacker initially masked their activity with a small Tornado Cash transfer, later conducting larger outflows. Although CoinDCX delayed disclosure by ~17 hours to conduct internal analysis, it has since confirmed full reimbursement from its treasury and is collaborating with CERT-In and blockchain forensics firms.

A Recovery Bounty Program is being launched, and affected wallets were identified by ZachXBT and Arkham.

Incident Report

Protocol / Project CoinDCX
Date of Incident
Attack Technique Access Control
Classification Infrastructure / CeFi
Primary Source View Post-Mortem

Protocol Information

Protocol Type CEX
Official Website coindcx.com/
Protocol Twitter/X @CoinDCX
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Memes Base 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 CoinDCX'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 CoinDCX, these are the critical security checks that could have prevented this incident (July 2025).

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

Sources & References

Learn to Prevent the Next CoinDCX

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