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

Gaston College — February 2023 breach

Clustered 9 filings across 8 jurisdictions · filing window Mar 9, 2023 → Aug 29, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

191,324

First → last filing

Mar 9, 2023 → Aug 29, 2023

Merge confidence

100%

incident inc_1444f304966e444e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Feb 21, 2023–Feb 22, 2023, discovered Feb 22, 2023 — the first regulatory filing landed 184 days later (flagged late). 191,324 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 172-day schedule across 7 filings beginning Mar 9, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
184days

Discovered → first regulatory filing

Discovery variance
139days

Range of discovered_at dates across filings

Leak precedence
168days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
172days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap⏱ Leak >90dMaine⏱ ME AG >30d · 49dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 21, 2023breach begins
Feb 22, 2023discovered · members disagree
notification delay · 184 days
Aug 25, 2023first filing
Aug 29, 2023most 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. MAR 9Leak sitenokoyawa postfirst filing · attacker claim · unverifiedday 0
  2. APR 2Leak sitesnatch postattacker claim · unverified+24d
  3. AUG 25IN AGIN AG noticestates nationwide total 191,324+169d
  4. AUG 25VT AGVT AG noticeno count stated+169d
  5. AUG 28MT AGMT AG notice7 MT residents+172d
  6. AUG 29MA AGMA AG notice56 MA residents+173d
  7. AUG 29NH AGNH AG notice20 NH residents+173d
  8. AUG 29SC AGSC AG notice5,496 SC residents+173d
  9. AUG 29ME AGME AG noticemost recent · states nationwide total 191,324+173d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 21, 2023
IN AG
Discovered
Feb 22, 2023VT AG + MT AG + NH AG +1Jul 11, 2023ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
VT AG + MT AG + NH AG +3
Attack vector
Unauthorized Access
VT 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)

191,324

Sum of filed state slices

5,661· 3.0% of stated

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

US191,324
SC5,496
IN57
MA56
ME25
NH20
MT7

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 claim2 members

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing7 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 Aug 23, 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

172 days

Cadence

~1 / 21.5d

vs. multi-state median

21.5× 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.