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

Monmouth College — December 2022 breach

Clustered 5 filings across 5 jurisdictions · filing window Jan 4, 2023 → Mar 20, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

4

Affected · reported

44,737

First → last filing

Jan 4, 2023 → Mar 20, 2024

Merge confidence

100%

incident inc_6c58ef29dc9c4b16 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. Intrusion Dec 6, 2022–Dec 14, 2022, discovered Dec 14, 2022 — the first regulatory filing landed 21 days later (flagged late). 44,737 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 4 more. Notifications rolled out on a 441-day schedule across 4 filings beginning Jan 4, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
21days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 17d

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
441days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksWashington✗ WA AG >90dMaine✗ ME AG >90d · 462dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 6, 2022breach begins
Dec 14, 2022discovered
notification delay · 21 days
Jan 4, 2023first filing
Mar 20, 2024most recent filing

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

Member cascade — every filing about this breach

  1. JAN 4IN AGIN AG noticefirst filing · states nationwide total 44,737day 0
  2. JAN 20Leak sitevicesociety postattacker claim · unverified+16d
  3. MAR 20CA AGCA AG noticeno count stated+441d
  4. MAR 20WA AGWA AG notice677 WA residents+441d
  5. MAR 20ME AGME AG noticemost recent · states nationwide total 44,737+441d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 6, 2022
IN AG
Discovered
Dec 14, 2022· 8d undetected
CA AG + WA AG + ME AG
Data types
Education · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
CA AG + WA AG + ME AG
Attack vector
Ransomware
CA 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,737

Sum of filed state slices

1,518· 3.4% of stated

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

US44,737
IN817
WA677
ME24

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 filing4 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 9, 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

441 days

Cadence

~1 / 110.3d

vs. multi-state median

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