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

Georgia Institute of Technology — December 2018 breach

Clustered 9 filings across 8 jurisdictions · filing window May 22, 2019 → Aug 19, 2019. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

1,265,883

First → last filing

May 22, 2019 → Aug 19, 2019

Merge confidence

100%

incident inc_66e4f34c9fc8432b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Dec 14, 2018–Mar 22, 2019, discovered Mar 1, 2019 — the first regulatory filing landed 82 days later. 1,265,883 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 89-day schedule across 9 filings beginning May 22, 2019. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
82days

Discovered → first regulatory filing

Discovery variance
30days

Range of discovered_at dates across filings

Filing span
89days

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 clocksCalifornia✓ CA 60-day OK · 52dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 14, 2018breach begins
Mar 1, 2019discovered · members disagree
notification delay · 82 days
May 22, 2019first filing
Aug 19, 2019most 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. MAY 22MT AGMT AG noticefirst filing · states nationwide total 1,265,000day 0
  2. MAY 22WA AGWA AG noticestates nationwide total 1,265,000day 0
  3. MAY 22CA AGCA AG noticeno count statedday 0
  4. MAY 22OR AGOR AG noticestates nationwide total 1,265,883day 0
  5. MAY 23MA AGMA AG notice23,231 MA residents+1d
  6. MAY 24NH AGNH AG noticestates nationwide total 1,265,000+2d
  7. JUN 11SC AGSC AG noticestates nationwide total 1,265,000+20d
  8. AUG 13DE AGDE AG noticeno count stated+83d
  9. AUG 19NH AGNH AG noticemost recent · 4,330 NH residents+89d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 14, 2018 – Mar 22, 2019
MT AG
Discovered
Mar 1, 2019MT AG + NH AG + SC AG +1Mar 25, 2019WA AGMar 31, 2019CA AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
MT AG + WA AG + CA AG +4
Attack vector
Unauthorized Access
MT 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,265,883

Sum of filed state slices

70,090· 5.5% of stated

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

US1,265,883
SC33,458
MA23,231
WA8,577
NH4,330
MT494

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

89 days

Cadence

~1 / 11.1d

vs. multi-state median

11.1× slower

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.