DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed6 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedransomhousehigh sensitivity
Merged incident · 6 filings

Webber International University — February 2024 breach

Clustered 6 filings across 6 jurisdictions · filing window Jan 20, 2024 → May 24, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

5

Affected · reported

5,251

First → last filing

Jan 20, 2024 → May 24, 2024

Merge confidence

100%

incident inc_119d7ea4c31e4c12 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Feb 28, 2024, discovered Feb 28, 2024 — the first regulatory filing landed 86 days later (flagged late). 5,251 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Notifications rolled out on a 125-day schedule across 5 filings beginning Jan 20, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
86days

Discovered → first regulatory filing

Discovery variance
49days

Range of discovered_at dates across filings

Leak precedence
125days before filing

Days between the first leak-site claim and the first regulatory filing. 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
125days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap⏱ Leak >90dMaine⏱ ME AG >30d · 37dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 28, 2024breach begins
Feb 28, 2024discovered · members disagree
notification delay · 86 days
May 24, 2024first filing
—watching for filings

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

Member cascade — every filing about this breach

  1. JAN 20Leak siteransomhouse postfirst filing · attacker claim · unverifiedday 0
  2. MAY 24MT AGMT AG notice7 MT residents+125d
  3. MAY 24IN AGIN AG noticestates nationwide total 5,251+125d
  4. MAY 24MA AGMA AG notice40 MA residents+125d
  5. MAY 24ME AGME AG noticestates nationwide total 5,251+125d
  6. MAY 24VT AGVT AG noticemost recent · no count stated+125d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 28, 2024
IN AG
Discovered
Feb 28, 2024MT AG + VT AGApr 17, 2024ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
MT AG + VT AG + MA AG +1
Attack vector
Unauthorized Access
MT 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)

5,251

Sum of filed state slices

82· 1.6% of stated

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

US5,251
MA40
IN30
MT7
ME5

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

125 days

Cadence

~1 / 25d

vs. multi-state median

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