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.
When did it happen?
The breach date in the public record is May 21, 2012. The record was added to the catalogue on June 28, 2016 and last updated there on June 28, 2016.
What information was reported as exposed?
- Email addresses
- Email messages
- Employers
- IP addresses
- Names
- Partial credit card data
- Passwords
- Payment histories
- Physical addresses
- Website activity
These are incident-level categories. The record does not prove that every category was exposed for every affected person.
Who may be affected?
This record may be relevant to people who had an account or other relationship with WHMCS or used whmcs.com around May 21, 2012. A catalogue entry does not establish that every customer was affected or that every listed data category applied to each person. Compare the record with an official notice addressed to you.
What should you do?
Compare the organization, dates, and information categories with any notice you received. Use contact details you independently confirm.
Change exposed or reused passwords, begin with your email account, and turn on multi-factor authentication where available.
Review your credit reports and consider a free credit freeze if identity information could support new-account fraud.
Check statements for unfamiliar activity and contact the card issuer or financial institution through an independently verified channel.
Choose actions that match the information involved. If you find signs that someone is using your identity, the Federal Trade Commission provides a personal recovery plan at IdentityTheft.gov.
Sources and review information
- Have I Been Pwned breach catalogue record ↗
- Federal Trade Commission: What To Do After a Data Breach ↗
- Federal Trade Commission: Credit Freezes and Fraud Alerts ↗
Page reviewed September 14, 2026 by the Data Breach Help Editorial Team. Catalogue details reflect the provider record and may change.