All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed3 filings · 3 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 3 filings

University of Miami — June 2017 breach

Clustered 3 filings across 3 jurisdictions · filing window Dec 22, 2022 → Nov 17, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

973

First → last filing

Dec 22, 2022 → Nov 17, 2023

Merge confidence

100%

incident inc_7479351e81f74e92 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. Intrusion Jun 12, 2017, discovered Oct 18, 2023. 973 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 1 more. Notifications rolled out on a 330-day schedule across 3 filings beginning Dec 22, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Filing span

330days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 12, 2017breach begins

Oct 18, 2023discovered

Dec 22, 2022first filing

Nov 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

DEC 22HHS OCRHHS OCR noticefirst filing · states nationwide total 973operator-confirmedday 0
NOV 17MA AGMA AG notice4 MA residentsauto-linked+330d
NOV 17ME AGME AG noticemost recent · states nationwide total 153+330d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jun 12, 2017
Discovered: Oct 18, 2023· 2319d undetected
Data types: Health (basic) · Identity (basic) · Government ID · PII
Attack vector: Unauthorized Access

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)

973

Sum of filed state slices

5· 0.5% of stated

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

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 filing3 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: human
Confidence: 1.00 · above the 0.85 auto-merge floor
Reviewed: operator-reviewed Aug 26, 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

330 days

Cadence

~1 / 165d

vs. multi-state median

55.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.