keepcalculator

06 Numbers and Powers

GoDaddy Data Breach: 1.2 Million Customers Exposed?

Card No. 06·73168 · Updated · Standard formula, shown below

Yes, GoDaddy experienced a data breach that exposed the data of approximately 1.2 million customers. The breach, disclosed in November 2021, involved unauthorized access to a legacy WordPress hosting environment, exposing email addresses, customer numbers, and, in some cases, SSL private keys and WordPress admin passwords. This article explains what happened, what data was taken, how GoDaddy responded, and what affected users should do.

What Actually Happened in the GoDaddy Breach

In September 2021, GoDaddy discovered a security incident that had been ongoing for about two months. The attacker had gained access to a legacy WordPress hosting environment using a compromised password. GoDaddy reset the affected WordPress admin passwords and revoked SSL private keys, but the damage was already done. The company disclosed the breach in November 2021, stating that 1.2 million customers had their data exposed.

The exposed data included:

  • Email addresses and customer numbers
  • Default WordPress admin passwords (set at the time of provisioning)
  • SSL private keys for some customers
  • SFTP and database usernames and passwords (for a smaller subset)

GoDaddy stated that the attacker used the compromised password to access the system, but did not specify how the password was obtained. The company also noted that it had already reset the passwords and was working with law enforcement.

How Did the Attack Happen?

The breach was not a sophisticated zero-day exploit. It was a credential-based attack. An attacker obtained a valid password for a GoDaddy employee account or a service account that had access to the legacy WordPress hosting environment. Once inside, the attacker was able to move laterally and access customer data.

This highlights a common vulnerability: weak or reused passwords, even for internal systems, can lead to massive data exposure. GoDaddy has since implemented multi-factor authentication (MFA) for its employees and added additional monitoring, but the incident underscores the importance of robust access controls.

What Data Was Exposed and Who Was Affected?

The 1.2 million affected customers were those using GoDaddy’s managed WordPress hosting. The exposed data varied by customer:

  • All affected: email address and customer number.
  • Some affected: default WordPress admin password (set when the account was created, not the current password).
  • Fewer affected: SFTP and database credentials.
  • Subset: SSL private keys.

SSL private keys are particularly sensitive because they allow an attacker to decrypt encrypted traffic if they can intercept it. GoDaddy revoked and reissued the affected SSL certificates, so the stolen keys became useless. The default WordPress admin passwords were also reset, but if a customer had changed their password to something similar, they were advised to change it again.

How GoDaddy Responded

GoDaddy took several steps after discovering the breach:

  1. Reset all affected WordPress admin passwords.
  2. Revoked and reissued SSL private keys.
  3. Reset SFTP and database passwords for the affected subset.
  4. Notified affected customers via email.
  5. Engaged a cybersecurity firm to investigate.
  6. Reported the incident to law enforcement and regulatory bodies.

The company also advised customers to review their accounts for suspicious activity and to change any passwords that were similar to the ones exposed. GoDaddy offered no credit monitoring, which drew criticism from some security experts, but the company maintained that the risk was low for most customers.

What Should Affected Customers Do?

If you were part of the 1.2 million affected, here are the steps you should take:

  • Change your WordPress admin password immediately, even if GoDaddy already reset it.
  • Enable two-factor authentication (2FA) on your GoDaddy account and your WordPress admin panel.
  • Rotate any SFTP and database passwords if you have not done so already.
  • Check your email for phishing attempts that may use your exposed email address.
  • Monitor your website files for unexpected changes or added malicious code.
  • If you used the same password elsewhere, change it on those sites too.

Even if you were not directly affected, it is good practice to enable MFA and use unique, strong passwords for your hosting accounts.

Comparing This Breach to Others

The GoDaddy breach is not the largest in history, but it is significant because it affected a hosting provider, meaning the exposed data could be used to compromise websites. For comparison, the 2019 Canva breach exposed 139 million users’ data, and the 2020 Marriott breach affected 5.2 million guests. However, those were consumer-facing platforms. A hosting breach can have a cascading effect: if an attacker gains access to a website’s backend, they can inject malware, steal customer data from the site, or deface the site.

GoDaddy’s breach was also notable because it happened in a legacy environment. This is a common theme in many breaches – old systems that are not as well-protected as newer ones. Companies often focus security efforts on new infrastructure, leaving legacy systems vulnerable.

Frequently Asked Questions

How do I know if my GoDaddy account was affected?

GoDaddy sent email notifications to all affected customers in November 2021. If you did not receive an email, you can also log into your GoDaddy account and check for any security alerts. If you are unsure, contact GoDaddy support directly.

What should I do if my SSL private key was exposed?

GoDaddy revoked and reissued the affected SSL certificates, so the stolen keys are no longer valid. You do not need to do anything, but you can verify that your SSL certificate is still active by checking your website’s security padlock icon.

Can I sue GoDaddy for the data breach?

There have been class-action lawsuits filed against GoDaddy following the breach. Whether you can join a lawsuit depends on your jurisdiction and the specifics of your case. Consult a legal professional if you believe you have suffered damages.

Was my credit card information exposed?

No. GoDaddy stated that the breach did not include payment card data, bank account numbers, or other financial information. The exposed data was limited to email addresses, customer numbers, and in some cases, passwords and SSL keys.

Is my website still safe to use?

Yes, GoDaddy reset the affected passwords and revoked the SSL keys, so the immediate risk is low. However, you should still change your passwords and enable 2FA to protect against any future attacks. Also, scan your website for malware if you notice anything unusual.

Did GoDaddy offer credit monitoring?

No, GoDaddy did not offer free credit monitoring because the breach did not expose financial information. Credit monitoring is typically offered when Social Security numbers or credit card numbers are stolen, which was not the case here.

Final Thoughts

The GoDaddy breach is a reminder that no company is immune to cyberattacks, especially when legacy systems are involved. While the exposure was limited, it could have been worse if the attacker had used the stolen credentials to access more sensitive data. GoDaddy’s response was relatively swift, but the incident highlights the importance of using unique passwords, enabling MFA, and staying vigilant about security alerts. If you were affected, take the steps outlined above to protect your website and your personal information.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →