DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SitePressState AGConfirmed7 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedalphvhigh sensitivity
Merged incident · 7 records

SAINT XAVIER UNIVERSITY — June 2023 breach

Clustered 7 records across 5 jurisdictions: 5 filings, 1 press report and 1 leak-site claim · filing window Oct 23, 2024 → Oct 31, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 records

States

5

Affected · reported

212,267

First → last dated filing

Oct 23, 2024 → Oct 31, 2024

Merge confidence

100%

incident inc_5592f6b3d6174af4 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings, 1 press report and 1 unverified claim. The filings describe unauthorized access. Intrusion Jun 29, 2023–Jul 18, 2023, discovered Jun 29, 2023. 212,267 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 8-day schedule across 4 dated filings beginning Oct 23, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
22days

Range of discovered_at dates across filings

Filing span
8days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 29, 2023breach begins
Jun 29, 2023discovered · members disagree
Oct 23, 2024first dated filing
Oct 31, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

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

  1. AUG 14Leak sitealphv postfirst record · attacker claim · unverifiedday 0
  2. OCT 1IL AGIL AG noticefiling day not on record · no count stated—
  3. OCT 23VT AGVT AG noticeno count stated+436d
  4. OCT 30IN AGIN AG noticestates nationwide total 212,267+443d
  5. OCT 30ME AGME AG noticestates nationwide total 212,267+443d
  6. OCT 31MA AGMA AG noticemost recent · 116 MA residents+444d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 29, 2023 – Jul 18, 2023
VT AG
Discovered
Jun 29, 2023IL AGJul 1, 2023VT AGJul 21, 2023ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID
VT AG + ME AG + MA AG
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)

212,267

Sum of filed state slices

5,009· 2.4% of stated

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

US212,267
IN4,871
MA116
ME22

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

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing5 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 May 24, 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

8 days

Cadence

~1 / 2.7d

vs. multi-state median

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