Evidence: well sourced. Imported from the supplied 65-Case Master Edition, dated September 19, 2026. Source links and classifications are retained as an attributed case account; import is not an independent source review.

Case at a glance

Case number
053
Date / range
2021 publication
Sector
Pathogen and research-data governance
Genetic asset
Archived and recovered partial pathogen sequence data
Security principle
Scientific Deletion Is Not Always Erasure

Event summary

A 2021 study recovered partial data from early Wuhan SARS-CoV-2 sequencing runs that had been removed from the NIH Sequence Read Archive but remained accessible through cloud infrastructure, highlighting deletion ambiguity and outbreak-data provenance.

Source: doi.org — Deleted Early SARS-CoV-2 Sequences source 1.

Source: ncbi.nlm.nih.gov — Deleted Early SARS-CoV-2 Sequences source 2.

The case in context

The recovery of sequence information after removal from an archive exposes the difference between deletion from a public interface and erasure of every underlying copy. Metadata, replicas, and withdrawal records can change what researchers are able to reconstruct later.

The case concerns data provenance and availability. Recovered partial sequences cannot, by themselves, decide the origin of a pathogen or prove why a contributor requested removal. Transparent withdrawal records can help preserve scientific context without assuming that every removal has the same explanation.

Acquisition and processing

sequence submission → public archive → withdrawal/removal → residual cloud copy → independent recovery → renewed scientific interpretation

The sequence of events

  1. sequence submission
  2. public archive
  3. withdrawal/removal
  4. residual cloud copy
  5. independent recovery
  6. renewed scientific interpretation

What became inferable or exposed

Archived and recovered partial pathogen sequence data

A 2021 study recovered partial data from early Wuhan SARS-CoV-2 sequencing runs that had been removed from the NIH Sequence Read Archive but remained accessible through cloud infrastructure, highlighting deletion ambiguity and outbreak-data provenance.

Security dimensions

Confidentiality

The confidentiality question concerns archived and recovered partial pathogen sequence data. Exposure and further inference must be distinguished from the fact of collection or availability.

Integrity

The integrity question is whether the described material, permissions, processing, or interpretation can be relied upon. Scientific Deletion Is Not Always Erasure identifies the particular boundary examined here.

Availability

Access and continuity are assessed for the described event; potential effects are not presented as confirmed outages or losses.

Provenance

The relevant chain follows archived and recovered partial pathogen sequence data through the stages shown below. Missing public detail is not proof that internal records did not exist.

GeneticSecurity.org analysis

Genetic Exposure Radius

Not assessed

No single level is assigned where the supplied dossier gives a range, conditional outcome, or broad institutional consequence. The affected parties and proposed assessment are shown separately.

Confidence: not assigned. Classification: GeneticSecurity.org analysis.

Genetic Persistence Risk

Not assessed

Persistence depends on the specific biological material or information retained. A potential effect is not treated as an observed genomic disclosure.

Confidence: not assigned. Classification: GeneticSecurity.org analysis.

Genetic Provenance Integrity

Not assessed

A numeric provenance level is not inferred from the existence of a source or court record. It requires evidence of the relevant custody and processing controls.

Confidence: not assigned. Classification: GeneticSecurity.org analysis.

Proposed classification and its limits

Suggested GER: GER-5 for global research consequences. Suggested GPI: GPI-2/3 because custody and version history became disputed.

These are proposed classifications from the supplied case dossier. Conditional scores describe an assumed exposure; they are not evidence that it occurred. A single numeric value is left unassigned when the asset or outcome is not sufficiently bounded.

What this case does not prove

Recovered partial sequences do not alone determine the origin of SARS-CoV-2 or prove misconduct.

Mitigations and lessons

  • Transparent withdrawal reasons
  • Tombstone metadata
  • Versioned archives
  • Independent preservation
  • Contributor agreements
  • Reproducible pipelines
  • Clear distinctions between deletion
  • De-indexing
  • Inaccessible copies

Primary sources

Secondary sources

No additional source listed. See the evidence notes for limitations.

Policy and standards

Genetic Security Policy and Standards

Review and correction history

Source edition: September 19, 2026. Imported case account; no substantive corrections recorded.

Correction policy and log

Cite this case

GS-CASE-053. The Deleted Sequences: Recovery from a Cloud Archive. GeneticSecurity.org. https://geneticsecurity.org/cases/053-deleted-sars-cov-2-sequences-recovered/