Evidence: well sourced. Source-led synthesis; classifications are GeneticSecurity.org analysis, not findings by the source.
Case at a glance
- Case number
- 002
- Date / range
- 2018
- Sector
- Law enforcement
- Genetic asset
- Crime-scene genetic profile and genealogical relationships
- Security principle
- Kinship Leakage
Event summary
Investigators used crime-scene genetic information with genealogy matching, distant-relative relationships, family-tree research, demographic filtering, and later direct DNA comparison to identify Joseph James DeAngelo. The site's focus is not the crimes themselves; it is the architecture of relational genetic identification.
Source: NHGRI: Investigative genomics.
Source: Guerrini et al.: Police access to genetic genealogy databases.
Acquisition and processing
Genealogy comparison, family-tree research, candidate narrowing, and direct DNA confirmation
- Crime-scene DNA
- Genetic profile
- Genealogy comparison
- Relatives
- Family trees
- Candidate narrowing
- Candidate DNA
- Direct comparison
What became inferable or exposed
Crime-scene genetic profile and genealogical relationships
A person does not necessarily need to have personally uploaded DNA to a genealogy database for relatives' genetic data to help investigators narrow identity.
Affected parties and consent
- Direct parties
- Crime-scene source and database participants involved in matching
- Indirect parties
- Extended relatives used to narrow a family tree
- Direct count
- Unknown / not assigned
- Indirect count
- Unknown / not assigned
- Consent status
- Uploading relatives and the investigated individual have different consent relationships
Security dimensions
Confidentiality
Scope assessed from the specific asset and access described; no broader raw-genome disclosure inferred.
Integrity
No demonstrated data alteration established by the cited material.
Availability
No outage or destruction established in this case.
Provenance
Complete custody and processing evidence is unavailable; no numeric GPI rating assigned.
A relative match is the beginning of a lead
The security principle here is the path from one person's genetic information to a question about someone else. A genealogy comparison can point toward relationships that become useful when combined with other records. It should not be described as a database producing a complete identity from a single distant match.
This distinction matters for privacy and for the quality of an investigation. A lead can be useful while remaining uncertain. Confirmation has a different purpose: testing whether the candidate actually matches the relevant evidence. Readers should resist collapsing the entire chain into the phrase “DNA identified him,” which hides the intermediate reasoning.
Why the radius extends beyond the uploader
The proposed GER classification concerns the connected family network used to narrow possibilities. It does not mean that every member of the family was identified, investigated, or harmed. Those would be separate claims requiring evidence about the actual investigation.
Nor does the classification resolve whether a particular access was lawful or ethically justified. It describes the mechanism of relational exposure. The purpose of the investigation, the applicable rules, and the interests of people whose data contributed to a lead all deserve their own analysis.
What a careful account should preserve
When explaining a similar investigation, identify the comparison service, the type of profile, the role of family research, and the independent confirmation described by the sources. If the public record does not disclose a stage, leave the gap visible. A plausible reconstruction of a workflow should not be presented as an investigator's documented account.
That discipline makes the case transferable: it helps readers understand the relationship between matching and identification without teaching them to assume that every genealogy search follows exactly the same procedure.
GeneticSecurity.org analysis
Genetic Exposure Radius
Analysis: Extended relatives used to narrow a family tree. The rating describes possible scope, not harm or a count of affected people.
Confidence: moderate. Classification: GeneticSecurity.org analysis.
Genetic Persistence Risk
The described profile can remain useful for identification or comparison; retention and future linkability remain uncertain.
Confidence: low. Classification: GeneticSecurity.org analysis.
Genetic Provenance Integrity
Not assessed: the public sources do not establish enough of the complete biological and digital chain to score it. Unknown is not proof of missing controls.
Confidence: not assigned. Classification: GeneticSecurity.org analysis.
What this case does not prove
A distant cousin match does not automatically identify a person. Genealogical and investigative work plus confirmatory evidence are required.
Mitigations and lessons
Constrain database access; separate investigative leads from identification; require independent confirmation and documented authority.
Primary sources
- PRIMARY SOURCE NHGRI: Investigative genomics
- PRIMARY SOURCE Guerrini et al.: Police access to genetic genealogy databases
Secondary sources
No additional source listed. See the evidence notes for limitations.
Policy and standards
Genetic Security Policy and StandardsReview and correction history
Last reviewed: September 19, 2026. Initial source synthesis; no substantive corrections recorded.
Correction policy and logCite this case
GS-CASE-002. The Relative Who Never Consented: Genetic Genealogy and the Golden State Killer Investigation. GeneticSecurity.org. https://geneticsecurity.org/cases/002-golden-state-killer-genetic-genealogy/