Was your data in the Dunzo breach?

2020 · dunzo.com3,465,259 accountsSeverity 7 / 10 — high, because phone numbers and location data leaked

Check whether your email address was in it

Check my exposure

Free. No password — we email you a six-digit code. This breach and every other one your address appears in.

Dunzo (dunzo.com) suffered a data breach in 2020 that exposed around 3,465,259 accounts. If you had an account, some of your personal data may be circulating in leaked databases. The fastest way to know is to check your own email — free, in about 30 seconds, no password required.

What happened

In approximately June 2019, the Indian delivery service Dunzo suffered a data breach. Exposing 3.5 million unique email addresses, the Dunzo breach also included names, phone numbers and IP addresses which were all broadly distributed online via a hacking forum. The data was provided to HIBP by dehashed.com.

Breach record from Have I Been Pwned, CC BY 4.0. Risk analysis by Nullivo.

What was exposed, and why it matters

Not all breaches carry the same risk — what matters is which fields leaked. Here is what the Dunzo breach exposed and what each item actually enables:

Phone numbers
weight 7 / 10
Enables SIM-swap attacks (hijacking your number to intercept SMS codes), smishing, and voice scams that appear to come from your bank.
Location data
weight 6 / 10
Reveals where you live, work or travel, which supports both targeted scams and physical-safety risks.
Names and usernames
weight 4 / 10
Links this leak to your other accounts — a reused username lets anyone build a profile of you across platforms.
Email addresses
weight 3 / 10
Puts you on spam and phishing lists, and confirms to attackers that you hold an account with this service — which makes impersonation emails more believable.
IP addresses
weight 3 / 10
Reveals your approximate location and internet provider, which adds credibility to targeted scams.

Also listed in this breach: Device information, Email addresses, Geographic locations, IP addresses, Names, Phone numbers.

What to do if you were affected

These steps are ordered for this specific breach — the most urgent action given what leaked comes first.

  1. Phone numbers
    Move two-factor authentication off SMS to an authenticator app or passkey, and add a port-out PIN with your mobile provider.
  2. Location data
    Review location sharing on the accounts you still hold with this service.
  3. Names and usernames
    Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts.
  4. Email addresses
    Treat any message referencing this service with suspicion, and never act on links in unexpected emails.
  5. IP addresses
    No direct action needed, but be wary of anyone quoting your location as “proof” of identity.
  6. Confirm you were actually in it
    Run a free scan before you spend time on the steps above.

How urgent is this now?

This breach is over 6 years old. Old credentials still cause harm — leaked passwords from a decade ago are still tried against new accounts every day.

Remember: a breach can’t be “un-leaked” — once a database is out, it exists in countless copies. The goal is to make the leaked data useless: change what can be changed, lock down what can’t, and remove what has been republished.

Frequently asked questions

What data was exposed in the Dunzo breach?

The Dunzo breach exposed phone numbers, location data, names and usernames, email addresses, ip addresses. Enables SIM-swap attacks (hijacking your number to intercept SMS codes), smishing, and voice scams that appear to come from your bank.

How many people were affected by the Dunzo breach?

Around 3,465,259 accounts were exposed, making it a large breach.

What should I do if I had a Dunzo account?

Move two-factor authentication off SMS to an authenticator app or passkey, and add a port-out PIN with your mobile provider. You can check whether your own email appears in this breach with a free Nullivo scan — no password required.

Breaches that exposed similar data

If the Dunzo breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.

Was your data in the ai.type breach?2017 · 20,580,060 accounts
Was your data in the Wongnai breach?2020 · 3,924,454 accounts
Was your data in the Drizly breach?2020 · 2,479,044 accounts
Was your data in the Home Chef breach?2020 · 8,815,692 accounts
Was your data in the IIMJobs breach?2018 · 4,216,063 accounts

See all breaches we cover →