Was your data in the WHMCS breach?

WHMCS (whmcs.com) suffered a data breach in 2012 that exposed around 134,047 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 May 2012, the web hosting, billing and automation company WHMCS suffered a data breach that exposed 134k email addresses. The breach included extensive information about customers and payment histories including partial credit card numbers.

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

Also listed in this breach: Email addresses, Email messages, Employers, IP addresses, Names, Partial credit card data, Passwords, Payment histories, Physical addresses, Website activity.

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. 01Payment or bank details
   Contact your bank, ask them to monitor or reissue the card, and check statements for small “test” transactions.
2. 02Passwords
   Change this password everywhere you have reused it, starting with your email account — whoever controls your email can reset everything else.
3. 03Private messages
   Consider what was discussed on this service and whether anything needs changing (shared passwords, personal disclosures).
4. 04Home addresses
   Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating.
5. 05Names and usernames
   Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts.
6. 06Confirm 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 WHMCS 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 14 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

Breaches that exposed similar data

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

See all breaches we cover →