---
title: "GoDaddy multi-year compromise"
description: "What the retained public evidence establishes about the GoDaddy incident, its attack path, impact, and response."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-09-19"
canonical_url: "https://www.ally.security/incidents/godaddy-multi-year-compromise-2020"
markdown_url: "https://www.ally.security/incidents/godaddy-multi-year-compromise-2020.md"
stix_url: "https://www.ally.security/incidents/godaddy-multi-year-compromise-2020/stix.json"
---

# GoDaddy multi-year compromise

Same threat actor over 3 years; SSH keys, source code, customer credentials. Multiple linked intrusions treated as one long-running compromise.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** Web hosting
- **Operational impact:** Multiple linked intrusions treated as one long-running compromise
- **Financial impact:** No financial figure is established by the reviewed source evidence

## What happened

In 2020–2023 (disclosed as one connected campaign in 2023), GoDaddy experienced an incident in its web hosting environment. The retained source describes the attack path as follows: Same threat actor over 3 years; SSH keys, source code, customer credentials. [1](#source-1)

The documented consequence was: Multiple linked intrusions treated as one long-running compromise. [1](#source-1)

## Impact

- Documented impact: Multiple linked intrusions treated as one long-running compromise. [1](#source-1)
- No financial loss, ransom amount, recovery cost, or regulatory penalty is established by the reviewed source evidence.

## Threat Group & Attack Vector

The retained source describes the attack path as follows: Same threat actor over 3 years; SSH keys, source code, customer credentials. The canonical record does not add intrusion steps beyond those supported by the source. [1](#source-1)

### Actors

- No threat actor group has been identified in the reviewed public evidence.

### TTPs

- [T1213 — Data from Information Repositories](https://attack.mitre.org/techniques/T1213/) — mapped from the cited behavior. [1](#source-1)

## Response

The retained source describes containment action intended to limit further access or disruption. [1](#source-1)
The retained source describes a forensic or specialist investigation of the incident. [1](#source-1)

This account is bounded to [GoDaddy Form 10-K](https://www.sec.gov/Archives/edgar/data/1609711/000160971124000022/gddy-20231231.htm). Details absent from that evidence are left unresolved rather than inferred. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/godaddy-multi-year-compromise-2020/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### GoDaddy Form 10-K

regulatory · U.S. Securities and Exchange Commission

<https://www.sec.gov/Archives/edgar/data/1609711/000160971124000022/gddy-20231231.htm>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   GoDaddy multi-year compromise: The reviewed source documents the godaddy multi-year compromise involving GoDaddy.
2. **Resulted In · 85% confidence · current**  
   GoDaddy multi-year compromise: Multiple linked intrusions treated as one long-running compromise.
3. **Affected Organization · 100% confidence · current**  
   GoDaddy multi-year compromise: GoDaddy
4. **Resulted In · 90% confidence · current**  
   GoDaddy multi-year compromise: The retained source describes a forensic or specialist investigation of the incident.
5. **Resulted In · 90% confidence · current**  
   GoDaddy multi-year compromise: The retained source describes containment action intended to limit further access or disruption.
6. **Used Attack Technique · 90% confidence · current**  
   GoDaddy multi-year compromise: https://attack.mitre.org/techniques/T1213/
7. **Resulted In · 84% confidence · current**  
   GoDaddy multi-year compromise: Same threat actor over 3 years; SSH keys, source code, customer credentials.

</details>