en
Back to the list

ZebPay alerts users after MoEngage cloud breach

source-logo  bitcoinworld.co.in 27 m
image

ZebPay told affected customers on November 21, 2026 that an unauthorised party had used compromised credentials to reach customer data inside the cloud infrastructure of MoEngage, the third-party platform the Indian exchange uses for customer communications. In the notice, ZebPay said its own servers, wallets, databases and trading systems were untouched and that holdings remain secure. The disclosure was first reported by Crypto.news.

ZebPay’s notice says a breach at MoEngage exposed some customer contact details, online and device data and recent account activity. The exchange says customer funds were not affected and that it has reported the incident to the authorities.

What ZebPay’s notice actually says

The exchange framed the exposure narrowly. Its notice listed the broad categories of data involved rather than itemising individual records, and it said it had found no unauthorised activity in the account of the customer receiving the message.

Know when your
coins move

Alerts, real-time prices, and market news — all in one app
qr-code Point your phone camera to install
4.8 based on 40K reviews in the App Store and Google Play

MoEngage’s own data agreement, as described in the reporting, lists email addresses, device data, app settings and event data among the types of information clients can supply to the platform, which clients use to group audiences and send messages across channels.

The vendor side of the story is still partial. According to The Economic Times, some businesses could not access MoEngage for nearly a week, and some customers regained access on November 19. Crypto.news noted that the ZebPay disclosure is separate from two earlier service issues at the exchange: a technical problem at a banking partner on November 11 that slowed Indian rupee withdrawals, and a pause on crypto withdrawals during platform upgrades while deposits stayed open.

The warning is about impersonation, not withdrawals

ZebPay’s customer message centred on fraud risk rather than account safety. The exchange warned that a caller, texter or emailer may cite personal or transaction details to sound like a genuine ZebPay representative, and it set out what its staff will never do:

  • Ask for a password, one-time password, two-factor authentication code or wallet seed phrase
  • Ask a customer to install a remote-access app
  • Ask a customer to transfer funds to a wallet or account

Customers who want to verify a message can open the Help section of the ZebPay app and start a chat through the Support Centre. The exchange asks anyone opening a support ticket to use the email address registered to their ZebPay account, and its security guidance lists a dedicated address for reporting suspicious emails. Customers in India were directed to the National Cyber Crime Helpline on 1930 or to the cybercrime portal; the government’s reporting instructions for financial cyber fraud in Delhi say callers should have the transaction ID, date and amount ready, and that they receive an acknowledgment number to finish the complaint online.

Why it matters

Support and marketing systems have become a recurring weak point for crypto exchanges, because the data held there — contact details, device fingerprints, activity logs — is exactly what impersonation scams need. The pattern is well documented: Coinbase disclosed in May 2025 that criminals paid overseas customer support workers to copy records for less than 1% of its monthly transacting users, declined a $20 million ransom demand and offered the same amount as a reward, while Kraken dealt with a separate extortion attempt in April 2026 after improper access by people linked to its support operations.

For ZebPay’s users, the practical risk is not a drained wallet but a convincing phone call. Anyone holding a ZebPay account should treat unsolicited contact that quotes real transaction details as suspicious by default and verify it inside the app.

What it means for India

The incident lands on an Indian exchange with an Indian customer base, which puts it inside the country’s cyber-fraud reporting system rather than in a purely offshore dispute — hence ZebPay’s pointers to the 1930 helpline and the national cybercrime portal. It also arrives in a market where exchanges serving Indian users are registered with FIU-IND as reporting entities, so how promptly a platform discloses a vendor-side incident is part of its compliance posture, not just its public relations.

What to watch

The open questions are the scope of the MoEngage incident across other clients and what the authorities do with ZebPay’s report. MoEngage’s public account of the credential compromise at its service provider, and any further customer notices from the vendor, will determine whether this remains a single-exchange story.

bitcoinworld.co.in