Was your data in the eThekwini Municipality breach?

2016 · eservices.durban.gov.za81,830 accountsSeverity 10 / 10 — critical, because government identifiers and passwords 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.

eThekwini Municipality (eservices.durban.gov.za) suffered a data breach in 2016 that exposed around 81,830 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 September 2016, the new eThekwini eServices website in South Africa was launched with a number of security holes that lead to the leak of over 98k residents' personal information and utility bills across 82k unique email addresses. Emails were sent prior to launch containing passwords in plain text and the site allowed anyone to download utility bills without sufficient authentication. Various methods of customer data enumeration was possible and phishing attacks began appearing the day after launch.

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 eThekwini Municipality breach exposed and what each item actually enables:

Government identifiers
weight 10 / 10
The strongest identity-theft material there is — enough to open credit accounts or file fraudulent claims in your name.
Passwords
weight 10 / 10
Attackers replay leaked passwords across other sites (“credential stuffing”). Because most people reuse passwords, one leak often unlocks email, shopping and banking accounts elsewhere.
Home addresses
weight 8 / 10
Home addresses feed people-search and data-broker sites, which republish them publicly. They also make phishing far more convincing and, in the worst cases, enable real-world harassment.
Dates of birth
weight 7 / 10
Date of birth is a permanent identifier used to verify identity by phone. Combined with a name and address it is often enough to impersonate you.
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.
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.

Also listed in this breach: Dates of birth, Deceased date, Email addresses, Genders, Government issued IDs, Names, Passport numbers, Passwords, Phone numbers, Physical addresses, Utility bills.

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. Government identifiers
    Consider a credit freeze or fraud alert with the credit reference agencies, and watch for accounts you did not open.
  2. Passwords
    Change this password everywhere you have reused it, starting with your email account — whoever controls your email can reset everything else.
  3. Home addresses
    Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating.
  4. Dates of birth
    Never confirm your date of birth to an inbound caller — hang up and dial the organisation back on a published number.
  5. Phone numbers
    Move two-factor authentication off SMS to an authenticator app or passkey, and add a port-out PIN with your mobile provider.
  6. Confirm you were actually in it
    Run a free scan before you spend time on the steps above.

This breach put your details on data-broker sites

Because eThekwini Municipality exposed home addresses, this is one of the breaches that feeds people-search and data-broker sites. Those sites scrape leaked databases, combine them with public records, and republish the result as a searchable profile — which is how a single breach turns into a permanent public listing. Removal works, but brokers typically re-list within about four months, so it has to be repeated.

See our broker-by-broker removal guides →

How urgent is this now?

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

Passwords are the reason breach age matters less than people expect. Leaked credentials are compiled into wordlists that get tried against new services for years afterwards, so a password exposed here is unsafe to use anywhere, ever again.

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 eThekwini Municipality breach?

The eThekwini Municipality breach exposed government identifiers, passwords, home addresses, dates of birth, phone numbers, names and usernames, email addresses. The strongest identity-theft material there is — enough to open credit accounts or file fraudulent claims in your name.

How many people were affected by the eThekwini Municipality breach?

Around 81,830 accounts were exposed, making it a smaller, more targeted breach.

What should I do if I had a eThekwini Municipality account?

Consider a credit freeze or fraud alert with the credit reference agencies, and watch for accounts you did not open. 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 eThekwini Municipality breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.

Was your data in the JobStreet breach?2012 · 3,883,455 accounts
Was your data in the RentoMojo breach?2023 · 2,185,697 accounts
Was your data in the Odido breach?2026 · 6,077,025 accounts

See all breaches we cover →