Key Takeaways

  • Cryptocurrency exchange CoinDCX has informed customers about a data breach involving its third-party messaging vendor, Plotline.
  • The unauthorised access occurred during two periods in October 2026: October 24–26 and October 30–31.
  • Information reportedly exposed includes customer names, email addresses and the names of banks linked to their CoinDCX accounts.
  • CoinDCX described the affected group as a “small number” of customers but did not disclose an exact figure.
  • The exchange says its internal databases, trading infrastructure, execution systems, customer wallets and funds were not affected.
  • Plotline provides technology used by CoinDCX to send in-app messages and notifications.
  • CoinDCX says it has informed affected customers, worked with Plotline to contain the incident and begun reviewing its vendor-risk controls.
  • The incident highlights the cybersecurity risks cryptocurrency platforms face through external technology providers.

Indian cryptocurrency exchange CoinDCX has disclosed a customer-data breach involving Plotline, a third-party vendor that provides messaging and notification services to the platform. According to the customer communication reported by Inc42, an unauthorised party accessed information held by Plotline during two separate periods in October 2026. The exposed information included customer names, email addresses and the names of banks linked to their CoinDCX accounts.

CoinDCX said the incident affected a “small number” of users and maintained that its internal systems, trading infrastructure, wallets and customer funds remained unaffected. The company has not disclosed how many customers were affected or whether the information was downloaded, copied or distributed beyond the vendor’s systems. The disclosure comes amid increased scrutiny of third-party technology providers used by financial institutions and cryptocurrency platforms.

What Happened in the CoinDCX Data Breach?

The incident involved Plotline, an external messaging technology provider used by CoinDCX to deliver in-app messages and notifications.

According to CoinDCX’s communication to customers, an unauthorised party gained access to information held by the vendor during two separate periods.

The reported timeline is:

DateDevelopment
October 24–26, 2026First period of unauthorised access at Plotline
October 30–31, 2026Second period of unauthorised access
October 31, 2026Plotline informed CoinDCX about the incident
November 17, 2026CoinDCX publicly shared a customer notice about the breach
November 19, 2026Inc42 reported further details about the incident

CoinDCX said Plotline informed it that information belonging to a small number of customers had been accessed.

The exchange subsequently worked with the vendor to understand the scope of the incident and confirm that the unauthorised access had been contained.

The company has not publicly identified the attacker or explained the precise method used to gain access to Plotline’s systems.

What CoinDCX User Information Was Exposed?

Based on information provided by Plotline, the exposed data was limited to three categories:

  1. Customer names: Names associated with affected CoinDCX accounts.
  2. Email addresses: Email IDs linked to those accounts.
  3. Linked bank names: Names of banks that customers had added to their CoinDCX accounts.

The company has not reported that bank account numbers, passwords, one-time passwords, private keys, wallet seed phrases or cryptocurrency balances were exposed in this incident.

It is important to distinguish between the name of a linked bank and the underlying bank-account credentials. The reported disclosure concerns the former.

CoinDCX also did not provide an exact count of affected users.

The phrase “small number” offers only a broad description of the scope. Without a confirmed figure, customers and investors cannot independently assess how many accounts were involved.

There is also an important distinction between information being accessed and information being downloaded or circulated. CoinDCX’s public communication does not establish whether the exposed records were copied, retained or shared with other parties.

Why Was Plotline Connected to CoinDCX?

Plotline is a third-party technology provider that CoinDCX uses for in-app messaging and notifications.

Such services help digital platforms communicate with customers through messages displayed inside mobile applications.

For a cryptocurrency exchange, these notifications can support product announcements, feature discovery, onboarding communication and other customer-engagement activities.

Using an external vendor can help a company develop and operate these communication features without building every component internally.

However, the arrangement also creates a security dependency.

A vendor may receive or process customer information to provide its services. If that vendor experiences a security incident, information belonging to the platform’s customers may become exposed even when the platform’s own infrastructure remains secure.

That is what makes the CoinDCX incident significant.

The reported breach did not originate in CoinDCX’s trading infrastructure. It involved a company that supported one part of its customer communication operations.

CoinDCX Says Trading Systems and Customer Funds Were Not Affected

CoinDCX has emphasised that the Plotline incident did not compromise its core cryptocurrency exchange infrastructure.

In its communication, the company said Plotline had no access to CoinDCX’s internal databases, trade execution engines or user wallets.

The exchange also said customer funds and wallets remained secure and untouched.

This distinction matters because cryptocurrency exchanges manage several different categories of technology and information.

System or informationReported status in the Plotline incident
Customer namesExposed for a limited number of users
Email addressesExposed for a limited number of users
Names of linked banksExposed for a limited number of users
Internal CoinDCX databasesCompany says unaffected
Trade execution systemsCompany says unaffected
Customer walletsCompany says unaffected
Customer fundsCompany says unaffected
Passwords and private keysNot identified as exposed in the reported incident

The assessment above reflects CoinDCX’s disclosures and does not represent an independent forensic verification.

A breach at an external vendor does not automatically mean an exchange’s wallets or trading systems have been compromised. Equally, the fact that core systems remain unaffected does not make the exposure of customer information insignificant.

Personal information can still be misused for targeted phishing, impersonation and social engineering.

Why Exposed Customer Details Could Create Phishing Risks

The most immediate concern for affected customers is the possibility of targeted fraud.

Names and email addresses can help attackers create messages that appear more credible than generic spam.

The inclusion of a linked bank’s name can make an impersonation attempt more convincing.

For example, a fraudulent message could claim that a customer’s bank connection needs verification or that a CoinDCX account requires an urgent security update.

An attacker could then direct the customer to a fake website designed to collect login credentials or request sensitive information.

This is particularly relevant in cryptocurrency because transactions can be difficult or impossible to reverse once funds have been transferred to an attacker-controlled wallet.

How attackers could misuse exposed information

1. Phishing emails

Attackers may send messages pretending to come from CoinDCX or a linked financial institution.

2. Fake customer-support calls

A fraudster could use a customer’s name and bank association to make a phone call sound legitimate.

3. Account-security impersonation

Messages claiming that an account has been compromised could pressure users into revealing passwords or authentication codes.

4. Fake verification links

Fraudulent websites may imitate exchange login pages and attempt to capture customer credentials.

5. Social engineering

Attackers may combine exposed information with details obtained from other sources to create more convincing scams.

These are potential misuse scenarios, not confirmed consequences of the Plotline incident.

What CoinDCX Is Doing After the Incident

CoinDCX said it worked closely with Plotline to confirm that the incident had been contained.

The exchange has also initiated a review of the vendor’s security posture and its own third-party risk-management processes.

The review reportedly covers:

  • Plotline’s security controls.
  • Data-minimisation practices.
  • Internal vendor-risk procedures.
  • The handling of customer information by external service providers.

CoinDCX said it had informed affected customers.

The company also said it was strengthening its vendor-risk controls.

The effectiveness of these measures will depend on how the company evaluates external providers, limits the customer information they can access and monitors their security practices.

For customers, the most important immediate step is to remain cautious about messages or calls claiming to represent CoinDCX.

CoinDCX Has Faced Earlier Security Incidents

The Plotline disclosure comes after previous security-related incidents involving CoinDCX.

These incidents should be treated separately because they involved different systems, circumstances and types of exposure.

July 2025: Approximately $44 million stolen from an internal account

In July 2025, CoinDCX disclosed a security breach involving an internal account used to provide liquidity on a partner exchange.

The incident resulted in a loss of approximately $44 million.

The company said the affected account was an internal operational account and that customer assets were not impacted. It also said it would absorb the loss using its own treasury reserves.

CoinDCX subsequently described the incident as involving a server compromise and said it had engaged external forensic specialists.

October 2026: Approximately $15.99 million in USDT lost through a retired-wallet process

In October 2026, CoinDCX disclosed a separate loss involving approximately 15.99 million USDT.

The company said customers continued depositing cryptocurrency into old operational wallet addresses that had been retired after the July 2025 incident.

A failure in an automated service responsible for transferring those deposits into secure wallets allowed funds to accumulate.

CoinDCX said it absorbed the loss and that active wallets, customer balances and trading remained unaffected.

November 2026: Plotline vendor breach exposes limited customer information

The latest incident concerns information held by an external messaging provider.

It is not the same as the earlier wallet-related incidents.

IncidentNature of incidentReported impact
July 2025Compromise of an internal operational accountApproximately $44 million loss
October 2026Failure involving deposits to retired operational wallet addressesApproximately $15.99 million in USDT
October 2026 Plotline incidentUnauthorised access at a third-party messaging vendorNames, email addresses and linked bank names for a small number of users

The incidents demonstrate why exchange security must cover more than customer wallets. Operational processes, third-party providers, customer communications and access management all form part of a platform’s wider security environment.

The Growing Risk of Third-Party Vendor Breaches

The CoinDCX incident highlights a broader challenge facing fintech companies, banks and cryptocurrency exchanges.

Digital businesses increasingly depend on external vendors for services such as:

  • Customer notifications and messaging.
  • Data analytics.
  • Identity verification.
  • Customer support.
  • Payment processing.
  • Cloud infrastructure.
  • Marketing automation.

These partnerships can reduce development costs and improve operational efficiency.

However, every additional provider creates another point that must be secured.

A company may maintain strong controls over its own servers while customer information is being processed by an external platform with different security practices.

This is commonly described as third-party or supply-chain cybersecurity risk.

The problem is especially important in financial services because even limited customer information can be valuable for fraud.

Companies therefore need to understand not only what information they collect but also which external providers can access it, how long they retain it and what happens when a vendor experiences a breach.

What CoinDCX Users Should Do Now

Customers who receive a breach notification should take basic precautions against impersonation and phishing.

1. Be careful with unexpected emails

Do not open suspicious links or attachments, even if a message uses your name or refers to your linked bank.

2. Never share OTPs or passwords

CoinDCX users should never disclose one-time passwords, passwords, two-factor authentication codes or wallet recovery phrases to someone claiming to be customer support.

3. Use the official application or website

If you need to check an account notification, open CoinDCX directly through its official app or website instead of following a link in an unsolicited message.

4. Enable two-factor authentication

Use the security features available on your account and protect the email account associated with it.

5. Treat unexpected login alerts seriously

If you receive an unfamiliar login notification, access your account through official channels and contact the exchange’s support team.

6. Be cautious about requests involving remote-access software

Do not install applications or share your screen with someone claiming they need to fix your cryptocurrency account.

These precautions are useful even when customer funds and wallet infrastructure have not been affected by a reported data breach.

The Bigger Picture

The CoinDCX incident demonstrates how a cybersecurity problem at an external service provider can affect customers of a financial platform without directly compromising the platform’s own trading systems. Plotline’s role in sending in-app messages and notifications created a connection to customer information, and unauthorised access at the vendor exposed a limited set of personal details. The incident reinforces the need for fintech and cryptocurrency companies to treat vendor security as part of their own data-protection responsibilities. Strong internal infrastructure is not enough if external providers have access to customer information without equally robust safeguards.

For CoinDCX, the immediate challenge is to establish the full scope of the exposure, maintain communication with affected customers and demonstrate that its vendor-risk controls are being strengthened. The company says wallets, trading systems and customer funds were unaffected, but the exposed contact details could still create opportunities for phishing and impersonation. As cryptocurrency platforms expand their use of external technology providers, their ability to manage data access, monitor vendors and respond transparently to security incidents will remain an important measure of customer trust.

Looking Ahead

The next important developments will be whether CoinDCX provides a clearer estimate of the number of affected customers and whether further details emerge about how the attacker accessed Plotline’s systems. Customers will also want clarity on whether the exposed information was merely accessed or copied and whether the vendor has completed its forensic investigation. The exchange’s review of Plotline’s security posture and its broader vendor-risk processes will be important indicators of how it intends to prevent similar incidents.

For India’s cryptocurrency industry, the incident is another reminder that protecting digital assets and protecting customer information are related but separate security responsibilities. Exchanges need safeguards covering wallets and trading infrastructure, but they also need strict controls over messaging providers, analytics platforms and other external partners. CoinDCX’s response will be judged not only by whether customer funds remained safe but also by how effectively it protects affected users from follow-on fraud and improves the security of its wider technology ecosystem.

Get the day’s top stories in your inbox

One concise email. No spam, unsubscribe anytime.