DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed17 records · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedpearhigh sensitivity
Merged incident · 17 records

Monmouth University — February 2026 breach

Clustered 17 records across 9 jurisdictions: 16 filings and 1 leak-site claim · filing window Jun 30, 2026 → Oct 28, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

17 records

States

9

Affected · reported

461,480

First → last dated filing

Jun 30, 2026 → Oct 28, 2026

Merge confidence

100%

incident inc_3fe9f03f83d34b59 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 16 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); 3 later filings were also flagged late. 461,480 individuals reported across the linked filings. Data reported: Government ID, Credentials, Financial account, and 5 more. Notifications rolled out on a 120-day schedule across 15 dated filings beginning Jun 30, 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
96days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
120days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMassachusetts✗ MA AG >90dCalifornia✗ CA 30-day late · 119dLeak gap✗ Leak >180dTexas✗ TX AG >30dRhode Island✗ RI AG >45dFull 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 dated filing
Oct 28, 2026most 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. MAR 3Leak sitepear postfirst record · attacker claim · unverifiedday 0
  2. JUN 30MA AGMA AG notice843 MA residents+119d
  3. JUN 30CA AGCA AG noticeno count stated+119d
  4. JUN 30NE AGNE AG noticefiling day not on record · no count stated—
  5. JUN 30NH AGNH AG notice217 NH residents+119d
  6. JUN 30MA AGMA AG notice2,208 MA residents+119d
  7. JUN 30DE AGDE AG noticeno count stated+119d
  8. JUN 30VT AGVT AG notice116 VT residents+119d
  9. JUN 30IN AGIN AG noticestates nationwide total 164,041+119d
  10. JUL 1TX AGTX AG noticestates nationwide total 164,041+120d
  11. AUG 20VT AGVT AG notice299 VT residents+170d
  12. AUG 20NH AGNH AG notice586 NH residents+170d
  13. AUG 21TX AGTX AG noticestates nationwide total 399,600+171d
  14. OCT 23RI AGRI AG notice512 RI residents+234d
  15. OCT 23NH AGNH AG notice655 NH residents+234d
  16. OCT 26VT AGVT AG notice346 VT residents+237d
  17. OCT 28TX AGTX AG noticemost recent · states nationwide total 461,480+239d
  18. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

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

461,480

Sum of filed state slices

4,907· 1.1% of stated

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

US461,480
MA2,208
TX1,105
NH655
RI512
VT346
IN81

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

120 days

Cadence

~1 / 8.6d

vs. multi-state median

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