Cc9f267dcNews eventClaimCoinDCX stated that it credited all affected user deposit accounts for operational losses from a failed deposit-sweeping process, and that active customer funds remain safe in cold walletsAgreeDisagree
Cc9f267dcClaimCoinDCX deprecated deposit wallet addresses created in January 2025 following a security incident in July 2025AgreeDisagree
Cc9f267dcClaimIndian cryptocurrency exchange CoinDCX initially denied that its active wallets were compromised following reportings of approximately $16 million in suspicious outflows on October 21, 2026AgreeDisagree
Cc9f267dcClaimCoinDCX updated CEO Sumit Gupta's earlier denial of a breach on October 22, 2026, acknowledging operational losses caused by a failed deposit-sweeping process from deprecated wallet addressesAgreeDisagree
Cc9f267dcClaimCoinDCX suffered a security incident in July 2025 resulting in the loss of approximately $44 million, which security firm Cyvers attributed to the Lazarus GroupAgreeDisagree
Cc9f267dcClaimAnalysis of ETF flow data indicates investors sought differentiated cryptocurrency assets with privacy features like Zcash during broader market volatility in October 2026AgreeDisagree
Cc9f267dcClaimBlockchain investigator ZachXBT challenged CoinDCX's initial breach denial, alleging that deprecated deposit address TQKJQ remained active for 10 months following the July 2025 hackAgreeDisagree
Cc9f267dcClaimCoinDCX CEO Sumit Gupta initially stated on October 22, 2026 that about $16 million in reported suspicious outflows involved old addresses compromised in July 2025 and were unrelated to current operationsAgreeDisagree
Cc9f267dcClaimZachXBT alleged that CoinDCX deposit address TQKJQ swept user deposits to CoinDCX's public hot wallet and received gas funding as recently as April and May 2026AgreeDisagree
Cc9f267dcClaimCoinDCX did not disclose the exact monetary size of the operational losses it absorbed from the failed deposit-sweeping process disclosed on October 22, 2026AgreeDisagree
Cc9f267dcClaimCoinDCX stated that despite customer notifications to stop using deprecated deposit addresses after July 2025, some users continued sending cryptocurrency to themAgreeDisagree
Cc9f267dcClaimCoinDCX treasury funds covered the $44 million loss from the July 2025 security incident, which CEO Sumit Gupta attributed to social engineeringAgreeDisagree
Cc9f267dcClaimCoinDCX reported that a temporary failure in its automated process for sweeping deposits from deprecated addresses caused operational losses that were discovered on October 22, 2026AgreeDisagree
Cc9f267dcClaimThe intrusive Monero compliance emails sent by Kraken were triggered after a Kraken employee flagged a young client holding substantial wealth as a red-flag riskAgreeDisagree
Cc9f267dcClaimKraken's compliance policy, amended on October 1, 2026, allows the exchange to restrict deposits or trading for non-compliant accounts, though withdrawals remain unaffectedAgreeDisagree
Cc9f267dcClaimKraken discontinued Monero trading and deposits for clients in the European Economic Area and the United Kingdom, citing regulatory changesAgreeDisagree
Cc9f267dcClaimArjun Sethi rejected an internal Kraken assessment that a customer's young age and large financial position constitute an automatic red flagAgreeDisagree
Cc9f267dcClaimArjun Sethi confirmed that Monero remains listed on Kraken, writing that customers can buy Monero on the exchange and withdraw it to private walletsAgreeDisagree
Cc9f267dcClaimArjun Sethi stated that no regulation required Kraken to request information about how customers intend to use Monero after withdrawing it from the exchange, calling such inquiries unacceptableAgreeDisagree
Cc9f267dcClaimKraken maintains its policy of requiring bank statements and investment records to verify the origin of customer funds under anti-money-laundering obligationsAgreeDisagree