WHMCS
HIGH RISKData breach — May 2012
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.
search Check if you were affected — freeData exposed in this breach
What happened in the WHMCS data breach?
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.
The exposed data included 10 types of personal information. Because passwords were exposed, users who reused their password on other sites are at particular risk. Learn more about what a data breach means for you.
Quick answer — was WHMCS hacked?
Yes. WHMCS was breached in May 2012. The breach exposed 134,047 records including email addresses, email messages, employers. This breach has been independently verified. If your email was involved, your data may still be at risk today. Check if you were affected.
Why was the WHMCS breach so dangerous?
The WHMCS breach exposed 134,047 records — that is a large number of compromised accounts. The combination of email addresses, email messages, employers makes this a high-risk breach that requires immediate action.
Because passwords were exposed, attackers can use credential stuffing to automatically test your WHMCS password against hundreds of other websites. If you reused your password anywhere, those accounts are now at risk. Read more about what happens to your data after a breach.
Don't wait to find out — check if your email was exposed in this breach now.
What data was stolen in the WHMCS breach?
Email addresses — used for phishing attacks and credential stuffing against your other accounts
Email messages — used for phishing attacks and credential stuffing against your other accounts
Employers — may be combined with other breach data to build a profile for targeted attacks
IP addresses — combined with other data, used for identity theft and physical fraud
Names — used to build profiles and target you with personalised scams
Partial credit card data — can be used for direct financial fraud and unauthorised transactions
Passwords — can be used to access your accounts directly or cracked to reveal your actual password
Payment histories — may be combined with other breach data to build a profile for targeted attacks
Physical addresses — combined with other data, used for identity theft and physical fraud
Website activity — may be combined with other breach data to build a profile for targeted attacks
Is the WHMCS breach still dangerous in 2026?
Yes. Stolen data from the WHMCS breach remains dangerous years after the incident. Research shows that over 65% of stolen credentials from older breaches have never been changed by the account holders. Attackers routinely compile data from multiple breaches to build complete profiles, and credentials from 2012 are still actively used in credential stuffing attacks today.
Personal information like email addresses, phone numbers, and dates of birth never expire. Even if you changed your WHMCS password, the other exposed data can be combined with information from other breaches to target you. Learn more about how long stolen data stays dangerous.
Frequently asked about the WHMCS breach
Approximately 134,047 user records were exposed in the WHMCS breach in May 2012.
Yes. Leaked credentials are actively used in credential stuffing attacks years after a breach. If you reused your WHMCS password elsewhere and haven't changed it, those accounts remain at risk today.
Enter your email in the free checker on EmailLeaked. We scan 12 billion+ breach records including the full WHMCS dataset and tell you instantly whether your email was exposed and what data was taken.
Change your WHMCS password immediately, change any other account where you used the same password, enable two-factor authentication on all important accounts, and monitor for phishing emails over the next 90 days.
Who was affected by the WHMCS breach?
The WHMCS data breach affected approximately 134,047 users who had accounts with the service. While not the largest breach on record, it still represents a significant number of compromised accounts in our database of 970+ known breaches.
If you ever created an account with WHMCS or used their services, your data may have been included in this breach. Check your email now to find out. You can also read our guide on what to do immediately after a data breach.
If your email was in the WHMCS breach
Change your WHMCS password immediately
Go to WHMCS and change your password right now. Use a strong, unique password that you have never used anywhere else.
Change any account sharing that password
If you used the same password on other sites, change it on every one of them. Attackers test stolen credentials on hundreds of popular sites within hours.
Enable two-factor authentication
Turn on 2FA on WHMCS and every important account. Even if your password is known, attackers cannot get in without the second factor.
Check your other accounts for this breach
Run a full email check to see every breach your email appears in — not just this one.
searchCheck all my breaches — freeOther major breaches
Was my email hacked?
Check if your email is compromised in seconds. Free, private, no signup. Scan 12 billion+ records across 970+ known breaches.
search Check my email now — it's freeNo signup required · Results in under 5 seconds · Your data is never stored