DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed12 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedpearhigh sensitivity
Merged incident · 12 filings

Monmouth University — February 2026 breach

Clustered 12 filings across 8 jurisdictions · filing window Mar 3, 2026 → Aug 21, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

7

Affected · reported

164,041

First → last filing

Mar 3, 2026 → Aug 21, 2026

Merge confidence

100%

incident inc_8b1c2dc113a04093 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Feb 5, 2026–Feb 13, 2026, discovered Mar 3, 2026 — the first regulatory filing landed 119 days later (flagged late). 164,041 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 5 more. Notifications rolled out on a 171-day schedule across 11 filings beginning Mar 3, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
119days

Discovered → first regulatory filing

Discovery variance
87days

Range of discovered_at dates across filings

Leak precedence
119days 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
171days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksCalifornia✗ CA 30-day late · 119dMassachusetts✗ MA AG >90dTexas✗ TX AG >30dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Feb 5, 2026breach begins
Mar 3, 2026discovered · members disagree
notification delay · 119 days
Jun 30, 2026first filing
Aug 21, 2026most 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. MAR 3Leak sitepear postfirst filing · attacker claim · unverifiedday 0
  2. JUN 30CA AGCA AG noticeno count stated+119d
  3. JUN 30MA AGMA AG notice843 MA residents+119d
  4. JUN 30VT AGVT AG notice116 VT residents+119d
  5. JUN 30NH AGNH AG notice217 NH residents+119d
  6. JUN 30MA AGMA AG notice843 MA residents+119d
  7. JUN 30NE AGNE AG noticeno count stated+119d
  8. JUN 30DE AGDE AG noticeno count stated+119d
  9. JUL 1TX AGTX AG noticestates nationwide total 164,041+120d
  10. AUG 20NH AGNH AG notice586 NH residents+170d
  11. AUG 20VT AGVT AG notice299 VT residents+170d
  12. AUG 21TX AGTX AG noticemost recent · 767 affected+171d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 5, 2026 – Feb 13, 2026
CA AG
Discovered
Mar 3, 2026CA AG + MA AG + NH AG +2May 29, 2026TX AGfilings disagree on discovery
Data types
Credentials · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PHI
CA AG + MA AG + NH AG +4
Attack vector
Unauthorized Access
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)

164,041

Sum of filed state slices

2,495· 1.5% of stated

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

US164,041
MA843
TX767
NH586
VT299

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

171 days

Cadence

~1 / 15.5d

vs. multi-state median

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