Exposed in this breach? Do this now
Change the password
On the breached site and everywhere else you reused it. Make every password unique.
Enable 2FA
A second factor keeps a leaked password from becoming a hijacked account.
Set up monitoring
and get notified the moment your data appears in a new leak.
WHMCS.com breach: questions and answers
When did the WHMCS.com data breach happen?
The WHMCS.com breach dates to May 2012.
How many records were leaked in the WHMCS.com breach?
LeakCheck has indexed 125,920 records from the WHMCS.com breach.
What data was exposed in the WHMCS.com breach?
The leaked records include email addresses, passwords, names, phone numbers, physical addresses, geographic locations and employers.
Were passwords exposed in the WHMCS.com breach?
Yes. The indexed WHMCS.com records include passwords, in plain text or hashed. If you had an account, change that password and every other password you reused.
How do I check if my data was in the WHMCS.com breach?
Enter your email address, username or phone number in the search form on this page. The free check shows whether your data appears in the WHMCS.com breach — and in any of the other 1,468 sources LeakCheck indexes.
What should I do if my data was in the WHMCS.com breach?
Change the password you used on WHMCS.com and everywhere you reused it, turn on two-factor authentication, and watch for phishing that quotes details from the leak. To hear about the next breach first, set up breach monitoring.