0x1fb0036b1fb0…1fb0036e
CoinDCX Vendor Breach Exposed Customer Bank Data
CoinDCX says Plotline exposed customer names, email addresses and linked bank names in two October 2026 windows. The exchange says trading systems and funds remained unaffected.

Outputs
Plotline data access occurred during October 24-26 and October 30-31, 2026.
Three exposed categories were registered names, account emails and linked bank names.
CoinDCX said trading systems, infrastructure and customer funds remained unaffected.
No affected-customer count or explanation of the intrusion has been disclosed.
Plotline reported that 10% of new users who saw one token-discovery widget placed a trade.
By Tom Whitfield
Indian exchange CoinDCX disclosed on November 17 that an unauthorized party accessed customer information held by messaging vendor Plotline during two October 2026 windows: October 24-26 and October 30-31. The exposed fields were registered names, account email addresses and the names of banks customers linked to their accounts.
What did the vendor breach expose?
Plotline told CoinDCX on October 31 that an unauthorized party had accessed data belonging to a "small number" of customers. CoinDCX identified three exposed categories:
- Registered customer name
- Account email address
- Name of the bank the customer had added
CoinDCX described the exposed fields as the sort of identifying data collected during know-your-customer (KYC) verification. The notice said the exposed information did not include bank account numbers, passwords, private keys or wallet balances.
CoinDCX said the incident left its trading systems, infrastructure and customer funds unaffected. It described Plotline as an external tool without access to internal databases, trade execution engines or user wallets. No outside party had verified those claims as of publication, and the incident occurred at the vendor rather than the exchange's servers.
What remains unverified?
The notice disclosed no affected-customer count and no explanation of how the unauthorized access occurred. CoinDCX also did not state the timing of individual customer notifications. Pushpendra Singh, whose post on X circulated the customer notice, described the incident as a third-party vendor breach and named the same three exposed categories.
CoinDCX said it worked closely with Plotline to confirm the incident was fully contained. Its follow-up questions had gone unanswered at publication, leaving the containment statement dependent on the exchange's account of what the vendor reported.
Are the login alerts connected?
No published evidence tied the login alerts to Plotline. X user Sasi shared a screenshot of two messages carrying the sender name COINDC-S and described them as "sudden login alert messages." Both texts referred to a new login on November 16, 2026, at 22:48 IST.
The messages advised recipients to change their password or contact support if they did not recognize the activity. Portions of the location and other details were obscured in the screenshot. The posts did not establish whether the alerts reflected actual account access, and CoinDCX's notice reported no unauthorized logins to customer trading accounts.
A name, email address and bank name cannot by themselves open an account or move funds. A message naming a recipient's real bank reads as more credible than generic spam, making the dataset usable raw material for impersonation attempts. No confirmed misuse had surfaced by publication, and the number of affected customers remained undisclosed.
How much did Plotline's integration matter?
Plotline's published case study with CoinDCX documents more than 20 campaigns for the exchange's product and growth teams over three months. The work included widgets highlighting heavily traded tokens, prompts introducing futures trading, a product category that uses leverage, and a guided walkthrough for new users.
CoinDCX executive vice president of growth Minal Thukral credited the service with helping build app widgets and cutting internal workload, according to the case study. Plotline reported that 10% of new users who saw one token-discovery widget went on to place a trade.
That reach helps explain why customer contact information sat with the vendor in the first place. It also makes the vendor's access to messaging data an operational issue for an exchange whose assurance rests on the separation between a vendor compromise and unauthorized customer-account access.
The notice leaves the affected-customer count, intrusion method and notification timing unstated. Absent a disclosure deadline, those details remain the clearest test of whether this stays a contained vendor event or becomes a broader account-security problem.
via cryptonews.net (Source)
More from Tom Whitfield
Show full bio
News editor covering technology and product news in crypto and web3 industry at Mempool Brief.
1,374 articles