DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed8 records · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0phigh sensitivity
Merged incident · 8 records

University of Rochester — May 2023 breach

Clustered 8 records across 7 jurisdictions: 7 filings and 1 leak-site claim · filing window Jul 28, 2023 → Aug 1, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 records

States

7

Affected · reported

88,025

First → last filing

Jul 28, 2023 → Aug 1, 2023

Merge confidence

100%

incident inc_b28026c3c3d94783 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion May 27, 2023–Jul 19, 2023, discovered May 31, 2023 — the first regulatory filing landed 58 days later. 88,025 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
58days

Discovered → first regulatory filing

Discovery variance
49days

Range of discovered_at dates across filings

Leak precedence
14days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
4days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine✓ ME AG ≤30d · 9dCalifornia✓ CA 60-day OK · 58dDate basis✓ Clock withheld · confirmation dateMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 27, 2023breach begins
May 31, 2023discovered · members disagree
notification delay · 58 days
Jul 28, 2023first filing
Aug 1, 2023most recent filing

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

Member cascade — every filing and leak-site claim in this incident

  1. JUL 14Leak sitecl0p postfirst record · attacker claim · unverifiedday 0
  2. JUL 28ME AGME AG noticestates nationwide total 88,025+13d
  3. JUL 28MT AGMT AG notice12 MT residents+13d
  4. JUL 28IN AGIN AG noticestates nationwide total 88,025+13d
  5. JUL 28CA AGCA AG noticeno count stated+13d
  6. JUL 28VT AGVT AG noticeno count stated+13d
  7. JUL 28MA AGMA AG notice962 MA residents+13d
  8. AUG 1NH AGNH AG noticemost recent · 138 NH residents+17d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 27, 2023
ME AG
Discovered
May 31, 2023CA AG + NH AGJul 19, 2023ME AG + MT AG + VT AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
ME AG + CA AG + MA AG +3
Attack vector
Third-Party / Supply Chain
ME 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)

88,025

Sum of filed state slices

1,289· 1.5% of stated

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

US88,025
MA962
NH138
ME91
IN86
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 22, 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

4 days

Cadence

~1 / 0.7d

vs. multi-state median

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