DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed9 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 9 filings

GAMESTOP CORP. — August 2016 breach

Clustered 9 filings across 7 jurisdictions · filing window Jun 5, 2017 → Jun 7, 2017. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

1,338,102

First → last filing

Jun 5, 2017 → Jun 7, 2017

Merge confidence

100%

incident inc_ddc8bd2c05f54a53 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Aug 10, 2016–Feb 9, 2017, discovered Apr 3, 2017 — the first regulatory filing landed 63 days later. 1,338,102 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
63days

Discovered → first regulatory filing

Discovery variance
15days

Range of discovered_at dates across filings

Filing span
2days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentialsidentity_government

Incident timeline

Aug 10, 2016breach begins
Apr 3, 2017discovered · members disagree
notification delay · 63 days
Jun 5, 2017first filing
Jun 7, 2017most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JUN 5CA AGCA AG noticefirst filing · no count statedday 0
  2. JUN 5NH AGNH AG notice7,141 NH residentsday 0
  3. JUN 5MA AGMA AG notice34,175 MA residentsday 0
  4. JUN 5WA AGWA AG notice27,956 WA residentsday 0
  5. JUN 5OR AGOR AG noticestates nationwide total 1,338,102day 0
  6. JUN 5MT AGMT AG notice3,075 MT residentsday 0
  7. JUN 6MA AGMA AG notice1 MA residents+1d
  8. JUN 6NH AGNH AG notice7,141 NH residents+1d
  9. JUN 7SC AGSC AG noticemost recent · 18,016 SC residents+2d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 10, 2016
CA AG
Discovered
Apr 3, 2017NH AG + WA AGApr 18, 2017SC AGfilings disagree on discovery
Data types
Authentication · Financial account · Financial credentials · Identity (basic) · Government ID · PCI · PII
NH AG + WA AG + SC AG +1
Attack vector
Unauthorized Access
NH AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

1,338,102

Sum of filed state slices

90,363· 6.8% of stated

93% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US1,338,102
MA34,175
WA27,956
SC18,016
NH7,141
MT3,075

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

2 days

Cadence

~1 / 0.3d

vs. multi-state median

4.0× faster

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.