This is a MapMyTimes opinion piece. It responds to the data breach that customer-engagement software company MoEngage confirmed on 21 November 2026. Attackers used credentials stolen from one of MoEngage's own vendors to get into part of its cloud systems in late October, and took data on some customers of its clients, among them users of the Indian crypto exchange ZebPay. Our view: India's data-protection debate keeps focusing on the brand a customer signs up with, while the real weak point is increasingly the chain of software suppliers behind that brand.
What do we actually know?
As our news report set out, MoEngage says fewer than 1% of its customer accounts were affected, that it contained the intrusion, notified the affected clients and brought in independent cybersecurity experts to validate its findings. ZebPay told users on 21 November that the exposed data included basic identifiers, contact details, online and device data and recent account activity, and said its own servers, wallets and trading systems and customer funds were not affected. It has reported the incident to the authorities. MoEngage has not named the vendor or said how many end users were affected.
Why should one vendor's password worry everyone?
It should worry everyone because the person whose data leaked never chose MoEngage, and certainly never chose MoEngage's supplier. A ZebPay customer handed details to an exchange; the exchange used a marketing platform; the platform relied on another firm whose login was stolen. And the risk is concrete: anyone holding a person's phone number together with their recent account activity can pose convincingly as the company's support desk.
Isn't the law already dealing with this?
Only partly, and not yet in full. The Digital Personal Data Protection Rules were notified on 14 November 2025 with an eighteen-month period for phased compliance, according to a PIB backgrounder. Once fully in force, a data fiduciary must tell affected people about a breach without delay, in plain language, covering what happened, the likely impact and what is being done. The same document says failing to keep reasonable security safeguards can attract a penalty of up to ₹250 crore, and failing to notify the Data Protection Board or affected individuals up to ₹200 crore. Separately, CERT-In's April 2022 directions already require covered organisations to report specified cyber incidents within six hours of noticing them.
What is the strongest argument against pushing harder?
The fair counter-argument is that the system worked roughly as intended here. By MoEngage's account, it detected and contained the intrusion, limited it to a small share of accounts, informed clients and called in outside experts; ZebPay, in turn, warned its users in clear terms. Naming a vendor in the middle of an investigation could shift blame before facts are settled, or help other attackers. And the eighteen-month runway in the DPDP Rules exists precisely because startups and smaller firms need time to rebuild systems; piling on new obligations early could raise costs without making anyone safer.
So what should change?
None of that argues for silence once the facts are in. Four steps seem reasonable to us without waiting for May 2027:
- A full post-incident account. Once its review is complete, MoEngage should publish how the vendor's credentials were stolen, how long access lasted and how many end users were affected.
- Collect less, share less. The PIB note lists data minimisation among the law's core principles. Companies should ask whether a marketing tool really needs a customer's recent account activity.
- Tell users who holds their data. Plain-language lists of the processors that receive customer data would make breach notices easier to understand.
- Treat vendor logins as crown jewels. Access granted to suppliers deserves the same scrutiny as a company's own administrator accounts.
For customers, ZebPay's own guidance is the right starting point: its staff will never ask for passwords, OTPs, 2FA codes or seed phrases, or ask users to install remote-access apps or move funds. Suspected fraud can be reported on the 1930 helpline or the National Cyber Crime Reporting Portal. Trust in India's digital economy rests on every link in the chain, not just the one with the logo on it.




