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

Xavier University of Louisiana — November 2022 breach

Clustered 8 records across 7 jurisdictions: 7 filings and 1 leak-site claim · filing window Feb 2, 2023 → Feb 20, 2023 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 records

States

7

Affected · reported

44,312

First → last dated filing

Feb 2, 2023 → Feb 20, 2023

Merge confidence

100%

incident inc_85eb7846344d4de1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Nov 22, 2022, discovered Nov 22, 2022. 44,312 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 18-day schedule across 6 dated filings beginning Feb 2, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
63days

Range of discovered_at dates across filings

Filing span
18days

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 clocksCalifornia✗ CA 60-day late · 72dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 22, 2022breach begins
Nov 22, 2022discovered · members disagree
Feb 2, 2023first dated filing
Feb 20, 2023most 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. DEC 20Leak sitevicesociety postfirst record · attacker claim · unverifiedday 0
  2. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  3. FEB 2IN AGIN AG noticestates nationwide total 44,312+44d
  4. FEB 12CA AGCA AG noticeno count stated+54d
  5. FEB 13ME AGME AG noticestates nationwide total 44,312+55d
  6. FEB 14MT AGMT AG notice2 MT residents+56d
  7. FEB 15NH AGNH AG notice9 NH residents+57d
  8. FEB 20MA AGMA AG noticemost recent · 104 MA residents+62d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 22, 2022
IN AG
Discovered
Nov 22, 2022IL AG + CA AG + MT AG +1Jan 24, 2023ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
CA AG + MT AG + NH AG +2
Attack vector
Unauthorized Access
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)

44,312

Sum of filed state slices

290· 0.7% of stated

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

US44,312
IN166
MA104
ME9
NH9
MT2

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 Jun 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

18 days

Cadence

~1 / 3.6d

vs. multi-state median

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