Goshen Medical Center — February 2025 breach
Clustered 11 records across 10 jurisdictions: 10 filings and 1 leak-site claim · filing window Sep 17, 2025 → Sep 18, 2025 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_fb6266fb754e433b · merged by deterministic · confidence 100%
Litigation Timing
SupplementalDiscovered → first regulatory filing
Range of discovered_at dates across filings
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.
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Sensitive data
identity_governmentIncident timeline
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
- FEB 15Leak sitebianlian postfirst record · attacker claim · unverifiedoperator-confirmedday 0
- SEP 17VT AGVT AG noticeno count statedoperator-confirmed+214d
- SEP 17NE AGNE AG noticefiling day not on record · 20 NE residentsoperator-confirmed—
- SEP 17IN AGIN AG noticestates nationwide total 456,385operator-confirmed+214d
- SEP 17HHS OCRHHS OCR noticestates nationwide total 456,385operator-confirmed+214d
- SEP 17MT AGMT AG notice6 MT residents+214d
- SEP 17NH AGNH AG notice30 NH residentsoperator-confirmed+214d
- SEP 17ME AGME AG noticestates nationwide total 456,385operator-confirmed+214d
- SEP 18SC AGSC AG notice5,234 SC residentsauto-linked+215d
- SEP 18TX AGTX AG noticestates nationwide total 456,385operator-confirmed+215d
- SEP 18MA AGMA AG noticemost recent · 119 MA residentsoperator-confirmed+215d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Feb 15, 2025 VT AG
- Discovered
- Mar 4, 2025VT AG + NE AG + MT AG +2Sep 12, 2025ME AG + TX AGfilings disagree on discovery
- Data types
- Health (basic) · Identity (basic) · Government ID · PHI VT AG + NE AG + HHS OCR +6
- 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)
456,385
Sum of filed state slices
5,889· 1.3% of stated
99% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
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
Attacker assertion only. Establishes: claim date, group, alleged victim.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
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 22, 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
1 days
Cadence
~1 / 0.1d
vs. multi-state median
6.0× faster
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.