HackingTechnologyInformationStolen CredentialsCustomer Data InvolvedCredentialsAuthenticationIdentity (basic)LowActive

GODADDY.COM, LLC

bd_dd928eec9ec08ec9 · schema v1 · pii pii-v1

Severity

Low

Discovered

Nov 17, 2021

Filed

Nov 22, 2021

To disclose

5 days

Affected

Not disclosed

Linked

6 filings

Confidence

66%

Full breach record for GODADDY.COM, LLC →5 incidents on file

GoDaddy.com, LLC disclosed a security incident affecting its Managed WordPress hosting service. An unauthorized third party gained access to authentication information (customer numbers, email addresses, and database/sFTP credentials) between September 6 and November 17, 2021. GoDaddy engaged forensic investigators, contacted law enforcement, blocked the actor, and rotated affected credentials. SSL certificates were also revoked and replaced. The incident impacts customers in multiple US states.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 72 days

discovery → filing · 5 days

Sep 6, 2021

Begins

Nov 17, 2021

Discovered

Nov 22, 2021

Filed

vs. sector median

18 wks faster

This filing is one of 6 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

Washington State AGbd_3e5542056436e29f2021-11-23 · +1dVerified
California State AGbd_456458c31f5bae592021-11-23 · +1dVerified
Maine State AGbd_a6095fa3a10ef9aa2021-11-23 · +1dVerified
Oregon State AGbd_a90e27d49b0061c62021-11-23 · +1dVerified

Show 1 more filing ↓up to 15d gap

Delaware State AGbd_ce4d3aa13640ac942021-11-07 · +15dCandidate

Name: GODADDY.COM, LLC
norm: godaddycom

Name: GODADDY.COM, LLC
norm: godaddycom
Industry: Technologyllm

Discovered: Nov 17, 2021
Breach occurred: Sep 6, 2021
Undetected for: 72 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: CredentialsPII
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External
Initial access: valid_credentials

During the incident: Began an investigation with the help of a third-party IT forensics firm
Contacted law enforcement
Blocked the unauthorized third party from our systems
Rotated your WordPress Admin login credentials, sFTP password and your database password
Installing a free DV SSL certificate on your website
Changes made: Adopt data security best practices, such as choosing a strong unique password
Regularly changing it
Enabling multi-factor authentication where available
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 5 days(5 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 5 states

View merged incident ↗

Delaware State AGNov 7 · first

Delaware State AG+15d · this page

Washington State AG+16d

California State AG+16d

Maine State AG+16d

Oregon State AG+16d

Pattern: first filing Nov 7 (DE), last Nov 23 (OR) — a 16-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://attorneygeneral.delaware.gov/wp-content/uploads/sites/50/2021/12/GoDaddy-Template-Customer-Email.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Nov 22, 2021
Raw hash: 832443874d614c748575fff4db90ebe7a9b422e075074f815ff8d3aaaa17bb90

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityGODADDY.COM, LLC

Victim entityGODADDY.COM, LLC

Incidentdiscovered Nov 17, 2021

Stated responseBegan an investigation with the help of a third-party IT forensics firm

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceattorneygeneral.delaware.gov