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

Hartwick College — October 2024 breach

Clustered 7 filings across 7 jurisdictions · filing window Nov 17, 2024 → Apr 11, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

4,803

First → last filing

Nov 17, 2024 → Apr 11, 2025

Merge confidence

100%

incident inc_4f33a602aaf9405d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Oct 22, 2024–Oct 25, 2024, discovered Oct 26, 2024 — the first regulatory filing landed 164 days later (flagged late). 4,803 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 144-day schedule across 6 filings beginning Nov 17, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
164days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
141days 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
144days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 167dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 22, 2024breach begins
Oct 26, 2024discovered
notification delay · 164 days
Apr 8, 2025first filing
Apr 11, 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. NOV 17Leak sitechort postfirst filing · attacker claim · unverifiedday 0
  2. APR 8NE AGNE AG notice2 NE residents+142d
  3. APR 8IN AGIN AG noticestates nationwide total 4,803+142d
  4. APR 9VT AGVT AG noticeno count stated+143d
  5. APR 10NH AGNH AG notice33 NH residents+144d
  6. APR 11ME AGME AG noticestates nationwide total 4,803+145d
  7. APR 11MA AGMA AG noticemost recent · 133 MA residents+145d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 22, 2024
IN AG
Discovered
Oct 26, 2024· 4d undetected
NE AG + VT AG + NH AG +1
Data types
Financial account · Identity (basic) · Government ID · PII
NE AG + VT AG + NH 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)

4,803

Sum of filed state slices

204· 4.2% of stated

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

US4,803
MA133
NH33
ME23
IN13
NE2

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

144 days

Cadence

~1 / 24d

vs. multi-state median

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