CoinDCX Plotline Breach: What Indian Users Must Know

CoinDCX, one of India's largest crypto exchanges, told its customers on 17 November 2026 that some of their personal data was exposed in a breach at a third-party vendor. The exchange's messaging vendor, Plotline, was accessed without authorisation in two windows in October, and the data taken includes customers' names, email addresses and the names of the banks linked to their accounts. CoinDCX says its own systems, trading platforms and customer funds were not affected — but the details that did leak are exactly the ones scammers use to write convincing fake messages.
> Educational content only. This is not financial advice. Crypto markets are volatile — never invest money you can't afford to lose. This guide explains a reported security incident and its practical implications for Indian users; it does not recommend any exchange, coin or trade, and it makes no prediction about future prices.
What Happened: The Facts at a Glance
The facts below are drawn from CoinDCX's own customer notice, shared on X on 17 November 2026, and from same-day reporting by crypto.news, TokenPost and cryptonews.net. Where a claim rests only on the company's word, this guide says so.
| Fact | Detail |
|---|---|
| What happened | Unauthorised access to Plotline, a messaging vendor CoinDCX uses to send in-app messages and notifications |
| When the access happened | Two windows in October 2026: 24–26 October and 30–31 October |
| When CoinDCX was told | Plotline told the exchange on 31 October that data belonging to a "small number" of customers had been accessed |
| When customers were told | 17 November 2026, via a notice shared on X — about two and a half weeks after the second window |
| What was exposed | Registered names, email addresses, and the names of banks linked to customer accounts |
| What was not listed as exposed | Bank account numbers, passwords, private keys and wallet balances |
| How many customers | Not disclosed — CoinDCX says only a "small number" |
| How the access happened | Not disclosed — the notice gives no detail on the method |
| What CoinDCX says about its own systems | Trading systems, infrastructure, customer funds and wallets unaffected; Plotline has no access to internal databases, trade execution engines or user wallets |
| Independent verification | None so far — the containment claim rests on the exchange's account of what Plotline reported to it |
| Confirmed misuse | None reported as of 17 November |
Why Names, Emails and Bank Names Matter
At first glance, the list of exposed data looks mild. No passwords, no account numbers, no private keys, no wallet balances. That is genuinely better than a breach that exposes login credentials or funds. But the three fields that were taken are the raw material of targeted phishing, and that is where the real risk sits.
A generic phishing email — "Dear customer, your account has a problem, click here" — is easy to spot. A targeted one is not. Imagine a message that addresses you by your full registered name, arrives at the email address you actually use for the exchange, and mentions the bank you actually linked to your account. It might say your bank has flagged a transaction, or that your CoinDCX withdrawal to that bank has failed, or that you need to re-verify the bank account to keep withdrawals working. The details are all correct, because they came from the breach. Only the link is wrong.
That is why the bank-name field matters more than it sounds. In India, an exchange account is usually linked to a bank account for INR deposits and withdrawals, and the bank's name is a personal detail that a stranger would not normally know. Combined with a name and an email address, it lets a scammer write a message that feels like it came from inside the system. The CoinDCX notice itself describes Plotline as a tool for sending in-app messages and notifications — the very channel through which users expect to hear from the exchange — which makes the impersonation risk sharper still.
The other risk is patience. Exposed email addresses do not have to be used today. They can be sold, combined with data from other breaches, and used months later, when the CoinDCX story has faded from the news. A phishing message in January that mentions your bank by name will not obviously trace back to an October breach. That is why the right response is a lasting change in habits, not a one-day check.
How This Differs From CoinDCX's October Loss
Indian users have heard the name CoinDCX in security headlines before, and it is worth being precise about how this incident differs from the earlier ones, because they are not the same story.
The first was the October loss of about $16 million, covered in our earlier guide. Blockchain investigators flagged outflows from retired wallets, and CoinDCX confirmed that customer deposits had continued reaching a retired wallet connected to an earlier security incident, while the process meant to sweep those deposits into the exchange's primary wallet had failed for a period of time. The company absorbed the loss of approximately $15.99 million itself and said customer balances, active wallets and trading systems were unaffected. That was a loss of money — the company's money, not customers' — caused by an internal process failure around old wallets.
The second was the Enforcement Directorate's searches of three Bengaluru premises linked to CoinDCX and Delta Exchange on 4–5 November, covered in our earlier guide to the FEMA investigation. The ED alleges that INR deposits were converted into USDT through a Costa Rica-based paper entity and routed to overseas exchanges for spot, futures and tokenised-stock trading. That is a regulatory investigation, not a security incident, and it is still open, with no charges or findings announced.
The Plotline breach is a third, separate thing: a vendor data exposure. No money was reported stolen, no trading system was reported compromised, and no regulator is involved. It sits in the same category as the vendor breaches that have hit other crypto companies this year — and that category is worth understanding on its own, because it keeps recurring.
The Vendor-Breach Pattern of 2026
CoinDCX is not the first crypto company to learn about a breach from a vendor, and it is unlikely to be the last. Three other incidents covered on this site follow the same shape.
In November 2025, CoinDCX itself told users that some customer data had been exposed through a breach at Mixpanel, a US-based analytics provider. The company said no passwords, OTPs, seed phrases or critical KYC data were accessed, and that its own wallets and user funds were unaffected. The pattern is identical to Plotline: a third-party tool with access to customer data, a breach at the vendor, and an exchange reassuring users that its own systems were untouched.
Coinbase disclosed a similar incident around the same time, when a breach at analytics vendor Amplitude exposed data on a small subset of its customers, again with funds stated to be unaffected. And in the last two days alone, this site has covered two more vendor breaches: Coinone, the South Korean exchange, whose support vendor MetaM was accessed on 12 November, exposing eleven types of customer data including names, phone numbers, emails, dates of birth, bank account numbers and passwords; and Trezor, whose retail partner Skladon exposed the names, phone numbers, delivery addresses and emails of about 27,000 customers who had placed orders between August and November.
The pattern is the lesson. Modern exchanges do not run everything in-house. They use outside vendors for analytics, messaging, customer support and retail distribution, and each vendor holds some slice of customer data. When the vendor is breached, the exchange's customers are exposed even though the exchange itself was never attacked. CoinDCX's own notice makes the point in its defence — Plotline has no access to internal databases, trade execution or wallets — but that is also the point of the risk: the data Plotline did hold was enough to enable convincing impersonation, and the exchange had no way to prevent the vendor's breach.
For Indian users, the practical consequence is simple: your data is only as safe as the weakest vendor your exchange uses, and you cannot audit that vendor yourself. The defence has to be on your side — verification habits, two-factor authentication, and treating every message as untrusted until proven otherwise.
What CoinDCX Has and Has Not Said
CoinDCX's notice is short, and its silences are worth noting, because they define what users still do not know.
What it has said: the vendor, the two windows, the three exposed fields, the fields not listed as exposed, that its own systems and funds were unaffected, and that it worked closely with Plotline to confirm the incident was fully contained.
What it has not said: how many customers were affected, beyond "a small number"; how the unauthorised access happened; whether the exposed data has been seen circulating anywhere; whether any affected customer has reported phishing or fraud linked to the breach; and why the public notice came about two and a half weeks after Plotline informed the exchange.
The containment claim deserves particular care. Cryptonews.net, reporting the story on 17 November, noted that the primary record is the exchange's own notice, and that the containment statement rests on the company's account of what Plotline reported to it — no outside party has verified it so far. That does not mean the claim is wrong. It means it is unverified, and users should treat it as a company statement rather than an established fact.
There is also an important distinction in the notice's wording. CoinDCX says bank account numbers, passwords, private keys and wallet balances were "not listed among the exposed information". That is a statement about what Plotline held and what was accessed, not a guarantee that no other data was involved. If you are a CoinDCX customer, the safe assumption is that your name, your email and your bank's name are known to an unknown party, and you should act accordingly even if nothing else was taken.
What Indian Users Should Do Now
If you have a CoinDCX account, the following steps are worth taking this week, in order of importance.
First, change how you handle messages. Do not click links, scan QR codes or download attachments from any message claiming to be from CoinDCX, your bank or a support team — even if it uses your name and mentions your bank. Open the official CoinDCX app yourself, or type the website address into your browser, and check for any alert there. If a message claims your withdrawal has failed or your account needs re-verification, that is the place to check, not the link in the message.
Second, protect the email address that was exposed. Your email is now in the hands of an unknown party, and it is the address you use to reset passwords elsewhere. Make sure it has a strong, unique password and two-factor authentication switched on. If you reuse the same email password on other sites, change those too — a leaked email address combined with a reused password is a common route into other accounts.
Third, switch on two-factor authentication on your CoinDCX account if you have not already, and prefer an authenticator app over SMS where the option exists. Two-factor authentication does not stop phishing on its own, but it makes a stolen password far less useful.
Fourth, expect the message to be personal. The most dangerous phishing after a breach like this is not a mass email but a targeted one. A message that mentions your bank by name, or that refers to a recent deposit or withdrawal, should be treated with extra suspicion, not less. The detail is the bait. If in doubt, call your bank on the number on its official website, or contact the exchange through its official support channel inside the app.
Fifth, report what you receive. If you get a suspicious message claiming to be from CoinDCX or your bank, report it to the exchange and to the government's cybercrime helpline at 1930, or through the National Cyber Crime Reporting Portal. Reporting helps the authorities track the campaign, and it helps other users, because phishing campaigns that target one exchange's customers usually target many.
Finally, do not panic about your funds. Nothing in the reporting so far suggests customer funds were touched, and the exposed data does not include anything that would let someone withdraw from your account on its own. The risk is impersonation, not a direct raid on your balance. The right response is vigilance, not a rush to move funds — and certainly not a rushed transfer in response to a message telling you to move them.
The Tax and Regulation Position Is Unchanged
For completeness: this breach changes nothing about the tax or regulatory position of Indian crypto users. Gains on crypto transfers are taxed at a flat 30% plus a 4% cess, with 1% TDS on sales, and those rules apply whether or not your data was exposed in a vendor breach. Tax note: crypto tax rules can change — the 30% rate and 1% TDS described here were current as of September 2026. Verify the latest rules before filing.
The regulatory picture is also unchanged. The ED's FEMA investigation into CoinDCX and Delta Exchange, which began with searches on 4–5 November, is a separate matter and remains open, with no charges or findings announced. The Plotline breach is a data-security incident, not a regulatory finding, and it should not be confused with the investigation. Likewise, the exchange's FIU-IND registration as a reporting entity under the Prevention of Money Laundering Act is about anti-money-laundering compliance, not a guarantee of data security — and this incident is a reminder of the difference.
One more context point for Indian users: Bitcoin was trading near $64,000–64,500, or roughly ₹60–67 lakh on Indian exchanges, in the early hours of 18 November, with the India premium — the gap between what Indians pay and the world price converted at the rupee rate — at about +11% in live readings. That price and that premium are background context for the market, not a consequence of this breach, and nothing in this guide should be read as a comment on where prices go next.
What to Watch Next
Three things will determine how this story develops, and all three are worth watching over the coming days.
The first is whether CoinDCX gives a number. The "small number" of affected customers is the biggest open question, and a count — or a confirmation that affected users have been contacted individually — would let users know whether they are in the group. Watch for a follow-up notice from the exchange, or for customers reporting that they received a direct notification.
The second is whether any misuse appears. So far no confirmed phishing campaign or fraud linked to the Plotline data has been reported. If one does appear — messages that mention bank names, or fake CoinDCX notifications referencing the October windows — that would change the story from a data exposure into an active scam campaign, and this guide's checklist would become urgent rather than precautionary.
The third is the vendor question itself. CoinDCX has said it worked closely with Plotline to confirm containment, and that it initiated a full review of the vendor's security posture after the earlier Mixpanel incident in November 2025. Whether this breach leads to a change in how the exchange vets and limits its vendors — and whether other Indian exchanges review their own messaging and analytics providers — is the structural question behind the incident. The Coinone and Trezor vendor breaches of the last two days suggest the problem is industry-wide, not specific to one exchange, and the answer will matter more than any single notice.
The Bottom Line
On 17 November 2026, CoinDCX told its customers that a breach at its messaging vendor Plotline had exposed the names, email addresses and linked bank names of a "small number" of customers, in two windows in October — 24–26 October and 30–31 October. Bank account numbers, passwords, private keys and wallet balances were not listed among the exposed data, and the exchange says its own systems, trading platforms and customer funds were unaffected. No count of affected customers has been given, no detail on how the access happened, and no outside party has independently verified the containment claim. No misuse of the data has been confirmed.
For Indian users, the practical meaning is narrow but important. Your money is not reported to be at risk from this breach. Your identity, in three small fields, is. A name, an email and a bank's name are enough to write a phishing message that feels genuine, and the weeks ahead are when that message is most likely to arrive. Do not click links in messages claiming to be from the exchange or your bank. Open the app yourself. Switch on two-factor authentication. And report anything suspicious to the exchange and to the cybercrime helpline at 1930. A vendor breach is a reminder that your data travels further than your exchange account — and that the best defence is on your side of the screen.
Keep Learning
Frequently asked questions
What data was exposed in the CoinDCX Plotline breach?
According to CoinDCX's notice of 17 November 2026, an unauthorised party accessed its messaging vendor Plotline and obtained the registered names, email addresses and linked bank names of a 'small number' of customers. The access happened in two windows in October 2026, from 24 to 26 October and from 30 to 31 October. Bank account numbers, passwords, private keys and wallet balances were not listed among the exposed data. CoinDCX has not given a count of affected customers, so the exact scale is unknown.
Are my funds safe on CoinDCX after the Plotline breach?
CoinDCX says its trading systems, infrastructure, customer funds and wallets were unaffected, because Plotline is an external messaging tool with no access to internal databases, trade execution engines or user wallets. That is the company's own account, and no outside party has independently verified it so far. No misuse of the exposed data has been confirmed. The practical risk is not theft from the exchange, but targeted phishing: someone who knows your name, your email and your bank's name can write a far more convincing fake message.
What should I do if I am a CoinDCX user?
First, do not click links or download attachments from any message claiming to be from CoinDCX, your bank or a support team — open the official app or type the website address yourself instead. Second, check that two-factor authentication is on and consider changing your email password, since your email address is now in the hands of an unknown party. Third, treat any message that mentions your bank by name with extra suspicion, because that detail may have come from this breach. Finally, report any suspicious message to the exchange and to the government's cybercrime helpline at 1930.
Related guides
- GTA 6 Crypto Scams: 8,800 Fake Tokens Target Indians — GTA VI launches today — and scammers are ready. Blockaid flagged 8,800+ fake GTA tokens on Solana. How the drainers work and how Indian gamers stay safe.
- Can You Insure Crypto in India? A Beginner's Guide 2026 — Can you insure your crypto in India? Learn what crypto insurance covers, where protection exists, and the safety steps that matter more today.
- Etherscan Support Hack Attempt: What Indian Users Must Know — Etherscan says attackers tried to break into its Freshworks support system on 18 November. No breach is confirmed — but fake-support phishing is the real risk.