People search GEDmatch data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 GEDmatch-linked incident, with headline counts up to 1.4M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why GEDmatch breach history matters
GEDmatch operates in Software (Unknown). Across indexed rows, recurring themes include mixed intrusion and disclosure events. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2020 — — GEDmatch: Hacking, 1,400,000 records
Cataloged incident. DNA data on up to 1.4m users of this genealogy site may have been hacked. Exposed categories include Personal and demographic data. BreachHistory cites approximately 1.4M+ affected records in this row. See the gedmatch2020-iib and canonical BreachHistory entry.
Patterns and analysis
- Mixed intrusion and disclosure events — appears across multiple GEDmatch catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Bookmark the GEDmatch company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/gedmatch · Latest: gedmatch2020-iib.
Sources: BreachHistory catalog (1 row for GEDmatch), company and regulator disclosures cited in individual breach records.