DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed8 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedavoslockerhigh sensitivity
Merged incident · 8 filings

Paul Smith’s College — July 2022 breach

Clustered 8 filings across 7 jurisdictions · filing window Dec 26, 2022 → Apr 17, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

6

Affected · reported

10,615

First → last filing

Dec 26, 2022 → Apr 17, 2023

Merge confidence

100%

incident inc_93ddfa1d4ff94eee · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jul 1, 2022–Aug 31, 2022, discovered Jan 26, 2023 — the first regulatory filing landed 21 days later. 10,615 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Notifications rolled out on a 112-day schedule across 7 filings beginning Dec 26, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
21days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
52days 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
112days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 1, 2022breach begins
Jan 26, 2023discovered
notification delay · 21 days
Feb 16, 2023first filing
Apr 17, 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. DEC 26Leak siteavoslocker postfirst filing · attacker claim · unverifiedday 0
  2. FEB 16MA AGMA AG notice259 MA residents+52d
  3. FEB 16MT AGMT AG notice12 MT residents+52d
  4. FEB 16ME AGME AG noticestates nationwide total 10,615+52d
  5. FEB 17IN AGIN AG notice25 IN residents+53d
  6. FEB 17VT AGVT AG noticeno count stated+53d
  7. FEB 21NH AGNH AG notice145 NH residents+57d
  8. APR 17MT AGMT AG noticemost recent · 12 MT residents+112d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 27, 2022
MT AG
Discovered
Jan 26, 2023· 152d undetected
MT AG + ME AG + VT AG +1
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PII
MA AG + ME AG + NH AG +2
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)

10,615

Sum of filed state slices

512· 4.8% of stated

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

US10,615
MA259
NH145
ME71
IN25
MT12

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 claim1 member

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

112 days

Cadence

~1 / 16d

vs. multi-state median

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