← CoinDCXreviewed 2026-11-02 · 10 claims checked
Fact-check findings
What an automated fact-checker found when it re-read CoinDCX against the sources the page cites. Only the most recent review is shown.
Read this first
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
disputed
5 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #1[disputed][awaiting moderator]in the timeline
“2023-10”
reviewerCoinbase's investment at a $2.45B valuation occurred in October 2023Multiple outlets date the Coinbase investment at $2.45B valuation to October 2025, not 2023. Coinbase had invested earlier, at a lower valuation.Proposed correction (not yet applied)2025-10 - #2[disputed][awaiting moderator]in section: Background and Corporate Structure
“a subsequent investment in 2023 placed the company's valuation at $2.45 billion”
reviewerA subsequent Coinbase investment in 2023 placed valuation at $2.45BSame error as the timeline date. The summary also implies the hack came after the valuation, which is the reverse of the actual order.Proposed correction (not yet applied)a subsequent investment in 2025 placed the company's valuation at $2.45 billion - #3[disputed][awaiting moderator]in the timeline
“2025-07-21”
reviewerZachXBT publicly identified the theft on July 21, 2025The cited TechCrunch piece gives July 19 for both the ZachXBT report and the CEO confirmation. July 21 is the article date.Proposed correction (not yet applied)2025-07-19 - #4[disputed][awaiting moderator]in section: July 2025 Security Breach — $44.2 Million Hack
“The breach remained undisclosed for approximately 17 hours until blockchain investigator ZachXBT identified and publicly reported the theft via his Telegram channel on July 21, 2025.”
reviewerBreach undisclosed about 17 hours until ZachXBT reported on July 21; CEO confirmed the same dayA July 19 hack with a 17-hour gap cannot produce a July 21 report. The page is internally inconsistent. The 17-hour figure itself was not independently checked.Proposed correction (not yet applied)The breach remained undisclosed for approximately 17 hours until blockchain investigator ZachXBT identified and publicly reported the theft via his Telegram channel on July 19, 2025. - #5[disputed][awaiting moderator]in the timeline
“2026-03-22”
reviewerCo-founders arrested March 22, 2026A March 22 arrest date does not fit the source: the founders were already in remand by the weekend, with a March 21 CoinDCX statement. The source's location is also internally conflicting.Proposed correction (not yet applied)2026-03-21
unverifiable
2 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #7[unverifiable][awaiting moderator]in section: Regulatory Standing
“the FBI has attributed the WazirX hack to North Korean state actors”
reviewerThe ZachXBT section says WazirX hack was attributed by the FBI to North KoreaI found no FBI statement on WazirX and did not fetch the Crystal page. This may be confused with the Bybit hack. - #10[unverifiable][awaiting moderator]in section: Attack Vector — Social Engineering and Employee Compromise
“Agarwal was arrested on July 26, 2025 by Bengaluru's Whitefield Police.”
reviewerEmployee arrest, malware, bail, Digital Suraksha Network, WazirX Lithuania allegations, withdrawal complaintsNot fetched due to limited effort. The employee details (age, earnings, test transfer times) and the other sections remain unchecked. The 'Telegram' wording for ZachXBT is also plausible but unchecked.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #6[partially supported][awaiting moderator]in section: July 2025 Security Breach — $44.2 Million Hack
“Cybersecurity firm Cyvers attributed the attack to North Korea's Lazarus Group, citing 'hallmarks' consistent with prior state-sponsored operations and the same exploit pattern as the 2024 WazirX hack.”
reviewerCyvers attributed the attack to Lazarus Group citing same exploit pattern as WazirXCyvers attribution is real but a private-sector assessment, not confirmed by authorities. The page should present it that way.
confirmed
2 claimsThe cited evidence supports the claim as written.
- #8[confirmed][no action needed]in section: July 2025 Security Breach — $44.2 Million Hack
“CoinDCX stated that customer funds held in cold storage were unaffected and pledged to cover all losses from its own treasury reserves.”
reviewerTheft was $44.2M, customer funds unaffected, loss covered from treasury, CERT-In engagedCore claims match TechCrunch. The 'cold storage' qualifier was not seen in that source. - #9[confirmed][no action needed]in section: Co-Founder Arrests and Fraud Allegations — March 2026
“The First Information Report (FIR), registered on March 16, 2026, was filed by a 42-year-old insurance consultant from Mumbra”
reviewerCo-founders arrested over a Rs 71.6 lakh fraud complaint; FIR March 16; coindcx.pro impersonation; 1,212 fake sitesBail terms and the affidavit were not independently fetched.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.