Data breaches → WHMCS
Was your data in the WHMCS breach?
2012 · whmcs.com · ~134,047 accounts exposedCritical severity · 10/10
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 details sourced from Have I Been Pwned, the industry-standard breach database. 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:
Direct financial fraud, plus convincing scam calls that quote your real card or account details to establish trust.
Attackers replay leaked passwords across other sites (“credential stuffing”). Because most people reuse passwords, one leak often unlocks email, shopping and banking accounts elsewhere.
Personal correspondence can be used for blackmail or social engineering, and often contains other sensitive details you have forgotten sharing.
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.
Links this leak to your other accounts — a reused username lets anyone build a profile of you across platforms.
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.
Reveals your approximate location and internet provider, which adds credibility to targeted scams.
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.
- Payment or bank details: Contact your bank, ask them to monitor or reissue the card, and check statements for small “test” transactions.
- Passwords: Change this password everywhere you have reused it, starting with your email account — whoever controls your email can reset everything else.
- Private messages: Consider what was discussed on this service and whether anything needs changing (shared passwords, personal disclosures).
- Home addresses: Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating.
- Names and usernames: Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts.
- Check whether your own email appears in this breach — run a free scan to confirm 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
What data was exposed in the WHMCS breach?
The WHMCS breach exposed payment or bank details, passwords, private messages, home addresses, names and usernames, email addresses, ip addresses. Direct financial fraud, plus convincing scam calls that quote your real card or account details to establish trust.
How many people were affected by the WHMCS breach?
Around 134,047 accounts were exposed, making it a mid-sized breach.
What should I do if I had a WHMCS account?
Contact your bank, ask them to monitor or reissue the card, and check statements for small “test” transactions. 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 WHMCS breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the ClixSense breach? (2016, ~2,424,784 accounts)
- Was your data in the Muslim Directory breach? (2014, ~37,784 accounts)
- Was your data in the PayAsUGym breach? (2016, ~400,260 accounts)
- Was your data in the gPotato breach? (2007, ~2,136,520 accounts)
- Was your data in the Ashley Madison breach? (2015, ~30,811,934 accounts)
- Was your data in the Bonobos breach? (2020, ~2,811,929 accounts)