Platform · Restaurant discovery and food delivery · Marketplace + logistics network · India · Global

Zomato Data Breach (2017)

Restaurant discovery and delivery platform.

Pilot record · BRI 2.0
Breach Risk Index
LowGuardedElevatedHighSevere
Low
First of five bands on the Breach Risk Index
Observed minimumAt least this much was seen. Read it as a floor · as of November 9, 2026
What this rating measures

The Index rates how dangerous a breach is right now rather than how large it was. It values each exposed field on its own, ages each one according to what that field is, and models what the assembled set lets an attacker do.

It is read against what is observed circulating, not what was announced. Five bands run from Low through Guarded, Elevated and High to Severe.

Every rating carries a status. Observed means it rests on fields seen circulating. Observed minimum means at least that much was seen, so read it as a floor. Childhood minimum is an observed minimum on data that includes children; read it as a low floor, because the rating does not yet count how long a child carries the exposure. Provisional means the field list comes from breach catalogues and is not yet verified. How sure we are of the evidence is shown separately, and it never lowers the rating. How the Index works →

Data sensitivity
Standard

Contact and account data. Rotatable, though still useful for phishing.

Circulating
16,472,873 email addresses
Field types
3 seen
Breach date
May 2017
Observed as of
Nov 9, 2026
Attributed
Nclay
Vector
Credential Theft
Catalogued by Have I Been Pwned
How it unfoldedAbout 4 months from breach to listing
  1. Breach
  2. 9 years laterListed in breach catalogues
  3. Observed · scored
What came out

What data was exposed

Email AddressContact
Password (salted MD5 hash)Credential
UsernameCredential
Red cannot be reissued or taken back · Blue is the residence · Black is movement, where you go rather than where you live · Grey is high-signal data that is not standard breach material
What it enables

How this data can be used against you

Partial

Account access

Account material that is weakened or incomplete.

Not enabled

Identity

No usable identity package in what circulates.

Not enabled

Physical targeting

No usable location detail in what circulates.

Not enabled

Social engineering

Contact details only, with too little context for a convincing approach.

Not enabled

Financial

No usable financial detail in what circulates.

Not enabled

Coercion

Nothing in what circulates is sensitive enough for leverage.

Not enabled

Health

No medical detail in what circulates.

Not enabled

Crypto

Nothing in what circulates is tied to crypto assets.

Enabled: the set on its own is enough · Partial: part of what is needed, or weakened · Not enabled: nothing usable in what circulates
What you should do

Two key actions to take

Change your Zomato password

Change it anywhere you reused it too, and turn on two-step sign-in.

Treat messages about Zomato with care

Do not act on a call, email or text about this breach. Contact Zomato using a number you already have.

Check it yourself

Check whether you were affected

Most people in a breach like this do not need an engagement. They need to know whether their address is in it, and when it turns up somewhere new. HackNotice does both, free: an Instant Check now, alerts after.

HackNoticeRuns on HackNotice · ObscureIQ never sees the address you check
Run the Instant Check →
If this matters to you

Talk to us about your exposure

If you are exposed in a way that cannot be rotated away, or you are responsible for someone who is, a call establishes what is actually reachable about you and what is worth doing first. No charge for the conversation.

Request a confidential call →
Full record · 9 sections

The full breach analysis

What happened, what the company reported against what is circulating, the field-by-field record, the actor and the advisory.

  • What happened
  • Recent developments
  • Reported and circulating
  • Data points exposed
  • Downstream risk
  • Principal risk advisory
  • Threat actor
  • Background
  • Data context
No sign-in · nothing is recorded
What happened

How this breach happened

In May 2017, Zomato was breached and nearly 17 million accounts were redistributed online. Exposed data included user IDs, names, usernames, email addresses, and passwords stored as salted MD5 hashes. Zomato said the incident stemmed from a compromised employee development account; a hacker using the name "Nclay" claimed responsibility.

Recent developments

What has happened since the breach

Zomato attributed the breach to a hacked developer account belonging to an employee and worked with the hacker, who withdrew the data from sale.

Reported and circulating

What was reported vs. what is circulating

The company's notice

Reported

Status
Not yet researched
Observed by ObscureIQ

Circulating

Observed as of
Nov 9, 2026
Breach date
May 2017
Volume
16,472,873 email addresses
Fields seen
3email address, password (salted MD5 hash), username

The score is built only on what is seen circulating.

Data points exposed

Every exposed field, and how long it stays useful

FieldShelf lifeIn noticeCirculating
Email AddressLasts for yearsNoYes
Password (salted MD5 hash)Fades over a few yearsNoYes
UsernameLasts for yearsNoYes

Shelf life is how long a field stays useful to someone holding it. A password expires fast. A government ID number or a date of birth lasts for years. An address stays useful long after it stops being current.

Downstream risk

How attackers can use this data

Exposure enables phishing, order fraud, delivery impersonation, and household targeting. Dining and address data can also reveal routines, social habits, and consumer preferences.

Principal risk advisory

Risks for executives and other high-profile people

A consumer-service breach: contact and account data supports phishing, account takeover and profile enrichment. For a high-profile principal the main risk is credible impersonation and enrichment of existing exposure.

Threat actor

Who is behind this breach

Attributed to Nclay.

Profile of Nclay and the other breaches in our records tied to it →

Background

About the company

Zomato is a major Indian platform for finding restaurants and ordering food serving millions of users.

Data context

Why the company holds this data

Restaurant-discovery and food-delivery platforms collect customer identity, phone numbers, addresses, payment-adjacent data, order history, and dining behavior across marketplace and logistics workflows.

Nclay →Credential TheftFood & DiningFood Delivery & OrderingPublic company2017

About this record

No reported total is on record for this breach. The circulating figure, 16,472,873 email addresses, is what has been observed in the published data. Circulation was last verified on Nov 9, 2026. The rating was last computed on Nov 9, 2026. Scores come from the Breach Risk Index, which rates what the exposed fields still let an attacker do, not how large the breach was. Breach records change as evidence does. If you hold a notice, a filing or a dataset observation this page does not reflect, report a correction.

ObscureIQ · Circulating breach record How the Index works · Contact MMXXVI