HEI

Historical Exchange Index

A quiet registry of crypto exchanges, active and gone.

Home / Active / CoinDCX

Exchange record

CoinDCX

Indian centralized cryptocurrency exchange that confirmed a July 2025 security breach involving an internal operational account, with reports placing the loss at about USD 44 million. CoinDCX said customer funds were not affected and later restored normal withdrawal/service operations.

CEXActive
Also known as: CoinDCX Exchange

Registry sequence

Key facts

Launch date
2018-01-01
Death date
Years
2018–—
Origin
India
Confidence
high
Last verified
2026-04-26

URL handling

Preferred action
Use current URL handling based on status below.
URL status
Live unverified
Archived URL

Summary

Indian centralized cryptocurrency exchange that confirmed a July 2025 security breach involving an internal operational account, with reports placing the loss at about USD 44 million. CoinDCX said customer funds were not affected and later restored normal withdrawal/service operations.

Timeline

CoinDCX confirmed an internal operational-account hack
2025-07-19hackcritical

CoinDCX confirmed a security breach involving an internal operational account, with reports estimating about USD 44 million stolen; the company said customer funds were not affected.

CoinDCX paused or limited some services after the breach
2025-07-20withdrawal_suspendedhigh

Reports described temporary product/service restrictions after the breach, including Web3 / INR and crypto-withdrawal handling, while CoinDCX worked to contain the incident and reassure users about fund safety.

CoinDCX resumed withdrawals after the breach
2025-08-01othermedium

Indian business press reported that CoinDCX resumed withdrawals after the USD 44 million breach and reiterated that user funds were safe.

Evidence

CoinDCX2026-04-07official_statementmedium reliabilityentityarchive
TechCrunch2025-07-21news_articlehigh reliabilityeventarchive
CoinDesk2025-07-19news_articlehigh reliabilityeventarchive

Related records

Notes and record state

Record note
Do not mark dead. The July 2025 incident involved an internal operational account according to company statements and reporting, not customer-custody loss. Track hack/security incident and restoration events while keeping status active.
Revision state
Records may be incomplete, approximate, contested, or revised as better evidence becomes available.
This record may be incomplete or revised. Dead-side entries prefer archived URLs over original domains. Dates, causes, and classifications may change when stronger evidence becomes available. Contact / corrections

Navigation

Registry
Active-side
Contact / Corrections
GitHub Issues