Jefferson County Health Center — April 2023 breach
Clustered 6 records across 5 jurisdictions: 5 filings and 1 leak-site claim · filing window Jan 13, 2023 → Aug 2, 2023 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_df3ad6a33374444a · merged by deterministic · confidence 100%
Litigation Timing
Range of discovered_at dates across filings
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · 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
- JAN 1IL AGIL AG noticefiling day not on record · no count statedauto-linked—
- JAN 13HHS OCRHHS OCR noticefirst filing · states nationwide total 115,940operator-confirmedday 0
- JUL 3Leak sitekarakurt postattacker claim · unverifiedoperator-confirmed+171d
- JUL 28HHS OCRHHS OCR noticestates nationwide total 53,827+196d
- AUG 2VT AGVT AG noticeno count statedoperator-confirmed+201d
- AUG 2MA AGMA AG noticemost recent · 26 MA residentsoperator-confirmed+201d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Apr 24, 2023 – May 30, 2023 VT AG
- Discovered
- Apr 24, 2023IL AGMay 30, 2023VT AGfilings disagree on discovery
- Data types
- Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII HHS OCR + VT AG
- Attack vector
- Unauthorized Access HHS OCR
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)
115,940
Sum of filed state slices
26· 0.0% of stated
100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
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
201 days
Cadence
~1 / 67d
vs. multi-state median
33.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.