DisclosureLens
Leak SiteState AGConfirmed15 records · 13 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmedusacritical sensitivity
Merged incident · 15 records

LEE UNIVERSITY — March 2024 breach

Clustered 15 records across 13 jurisdictions: 14 filings and 1 leak-site claim · filing window Mar 24, 2025 → Mar 31, 2025 (dated filings only). View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

15 records

States

13

Affected · reported

136,928

First → last dated filing

Mar 24, 2025 → Mar 31, 2025

Merge confidence

100%

incident inc_40bab3cff826416c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings and 1 unverified claim. Intrusion Mar 1, 2024–Mar 31, 2024, discovered Mar 1, 2024. 136,928 individuals reported across the linked filings. Data reported: Government ID, Biometric, Financial account, and 7 more. Notifications rolled out on a 7-day schedule across 11 dated filings beginning Mar 24, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
386days

Range of discovered_at dates across filings

Filing span
7days

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 clocksLeak gap✗ Leak >180dWashington✗ WA AG >90dFull clock table in Litigation Timeline

Sensitive data

biometricfinancial_credentialsidentity_government

Incident timeline

Mar 1, 2024breach begins
Mar 1, 2024discovered · members disagree
Mar 24, 2025first dated filing
Mar 31, 2025most 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. APR 17Leak sitemedusa postfirst record · attacker claim · unverifiedday 0
  2. MAR 1IL AGIL AG noticefiling day not on record · no count stated—
  3. MAR 24IN AGIN AG noticestates nationwide total 136,928+341d
  4. MAR 24NE AGNE AG noticefiling day not on record · no count stated—
  5. MAR 24VT AGVT AG noticeno count stated+341d
  6. MAR 25OR AGOR AG noticestates nationwide total 136,928+342d
  7. MAR 25NH AGNH AG notice139 NH residents+342d
  8. MAR 25MT AGMT AG notice112 MT residents+342d
  9. MAR 26CA AGCA AG noticeno count stated+343d
  10. MAR 26MA AGMA AG notice408 MA residents+343d
  11. MAR 26ME AGME AG noticestates nationwide total 136,928+343d
  12. MAR 26WA AGWA AG notice1,167 WA residents+343d
  13. MAR 26WA AGWA AG notice1,167 WA residents+343d
  14. MAR 31SC AGSC AG noticemost recent · 3,289 SC residents+348d
  15. APR 23MD AGMD AG noticefiling day not on record · 1,623 MD residents—
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 9, 2024
IN AG
Discovered
Mar 1, 2024NE AG + MT AG + SC AGMar 22, 2024NH AG + WA AG + MD AGMar 19, 2025OR AG + ME AGMar 22, 2025IL AGfilings disagree on discovery
Data types
Biometric · Education · Employment · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + VT AG + MA AG +8
Attack vector
Unauthorized Access
NE 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)

136,928

Sum of filed state slices

8,781· 6.4% of stated

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

US136,928
SC3,289
IN1,768
MD1,623
WA1,167
MA408
ME275
NH139
MT112

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

7 days

Cadence

~1 / 0.7d

vs. multi-state median

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