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

Trocaire College — March 2025 breach

Clustered 9 filings across 7 jurisdictions · filing window Mar 13, 2025 → Jan 28, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

6

Affected · reported

23,436

First → last filing

Mar 13, 2025 → Jan 28, 2026

Merge confidence

100%

incident inc_b57619f04dfd4bc9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Mar 12, 2025–Mar 14, 2025, discovered Mar 13, 2025 — the first regulatory filing landed 309 days later (flagged late). 23,436 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 321-day schedule across 7 filings beginning Mar 13, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
309days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
309days 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
321days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dMaine✗ ME AG >90d · 321dVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 12, 2025breach begins
Mar 13, 2025discovered
notification delay · 309 days
Jan 16, 2026first filing
Jan 28, 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 13Leak siteinc_ransom postfirst filing · attacker claim · unverifiedday 0
  2. APR 15Leak siteinc_ransom postattacker claim · unverified+33d
  3. JAN 16IN AGIN AG noticestates nationwide total 23,436+309d
  4. JAN 16IN AGIN AG noticestates nationwide total 23,436+309d
  5. JAN 16NE AGNE AG notice3 NE residents+309d
  6. JAN 28ME AGME AG noticestates nationwide total 23,436+321d
  7. JAN 28MA AGMA AG notice51 MA residents+321d
  8. JAN 28VT AGVT AG noticeno count stated+321d
  9. JAN 28NH AGNH AG noticemost recent · 5 NH residents+321d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 12, 2025
IN AG
Discovered
Mar 13, 2025· 1d undetected
NE AG + ME AG + VT AG +1
Data types
Financial account · Identity (basic) · Government ID
NE AG + ME AG + VT AG +2
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)

23,436

Sum of filed state slices

87· 0.4% of stated

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

US23,436
MA51
IN21
ME7
NH5
NE3

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 claim2 members

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing7 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

321 days

Cadence

~1 / 40.1d

vs. multi-state median

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