What was exposed, when it happened, and which databases confirm it.
- accounts
- 32,948,470
- Breached
- May 17, 2017
- Last Update
- September 4, 2017
Were you caught in this breach?
Search your email, phone number or username against every record CheckLeaked indexes.
Your address never leaves this page: it is hashed in your browser and only a short fragment of that hash is sent.
What happened
In May 2017, the restaurant guide website Zomato was hacked resulting in the exposure of almost 17 million accounts. The data was consequently redistributed online and contains email addresses, usernames and salted MD5 hashes of passwords (the password hash was not present on all accounts). This data was provided to HIBP by whitehat security researcher and data analyst Adam Davies.
Compromised Info
- Email addresses
- Passwords
- Usernames
Attestation
Four independent databases catalog this breach and they do not always agree. Each lane below is one source’s own count.
Sources & Link Methods
- LeakCheck— linked via automatic string matching
- Dehashed— linked via domain matching
- HIBP
FAQ
What was leaked in the Zomato breach?
The Zomato breach exposed: Email addresses, Passwords, and Usernames.
When did the Zomato breach happen?
The Zomato breach was disclosed on May 17, 2017 and affected 32,948,470 records.
Am I affected by the Zomato breach?
Search your email, phone or username at checkleaked.cc to find out whether your data appears in the Zomato leak.