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

Institute of Culinary Education — April 2025 breach

Clustered 10 filings across 10 jurisdictions · filing window May 28, 2025 → Oct 7, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

9

Affected · reported

33,342

First → last filing

May 28, 2025 → Oct 7, 2025

Merge confidence

100%

incident inc_2647ea70af134e08 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Apr 21, 2025–May 5, 2025, discovered May 5, 2025 — the first regulatory filing landed 154 days later. 33,342 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 132-day schedule across 9 filings beginning May 28, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
154days

Discovered → first regulatory filing

Discovery variance
113days

Range of discovered_at dates across filings

Leak precedence
131days 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
132days

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 >90dMaine⏱ ME AG >30d · 42dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 21, 2025breach begins
May 5, 2025discovered · members disagree
notification delay · 154 days
Oct 6, 2025first filing
Oct 7, 2025most 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. MAY 28Leak sitepayoutsking postfirst filing · attacker claim · unverifiedday 0
  2. OCT 6VT AGVT AG noticeno count stated+131d
  3. OCT 6MT AGMT AG notice22 MT residents+131d
  4. OCT 6IN AGIN AG noticestates nationwide total 33,342+131d
  5. OCT 6NE AGNE AG notice10 NE residents+131d
  6. OCT 6NH AGNH AG notice34 NH residents+131d
  7. OCT 7TX AGTX AG noticestates nationwide total 33,342+132d
  8. OCT 7CA AGCA AG noticeno count stated+132d
  9. OCT 7ME AGME AG noticestates nationwide total 33,342+132d
  10. OCT 7MA AGMA AG noticemost recent · 184 MA residents+132d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 5, 2025
VT AG
Discovered
May 5, 2025NE AGAug 26, 2025TX AG + ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID
VT AG + NE AG + NH AG +4
Attack vector
Unauthorized Access
VT 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)

33,342

Sum of filed state slices

805· 2.4% of stated

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

US33,342
TX432
MA184
IN77
ME46
NH34
MT22
NE10

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

132 days

Cadence

~1 / 14.7d

vs. multi-state median

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