Healthcare Services Group, Inc. — September 2024 breach
Clustered 16 filings across 16 jurisdictions · filing window Oct 16, 2024 → Sep 2, 2025. View entity profile → Other incidents for this victim →
incident inc_e031d6b995734135 · merged by deterministic · confidence 100%
Litigation Timing
SupplementalDiscovered → first regulatory filing
Range of discovered_at dates across filings
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.
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay
Sensitive data
authenticationbiometricidentity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- OCT 16SEC 8-KSEC 8-K noticefirst filing · no count statedoperator-confirmedday 0
- OCT 25Leak siteunderground postattacker claim · unverifiedoperator-confirmed+9d
- AUG 1IL AGIL AG noticeno count stated+289d
- AUG 25OR AGOR AG noticestates nationwide total 624,496auto-linked+313d
- AUG 25WA AGWA AG notice7,745 WA residentsauto-linked+313d
- AUG 25MT AGMT AG notice3,829 MT residentsauto-linked+313d
- AUG 25VT AGVT AG noticeno count statedauto-linked+313d
- AUG 25DE AGDE AG noticeno count statedauto-linked+313d
- AUG 25CA AGCA AG noticeno count statedauto-linked+313d
- AUG 25NH AGNH AG notice4,943 NH residentsauto-linked+313d
- AUG 25NE AGNE AG notice4,026 NE residentsauto-linked+313d
- AUG 25IN AGIN AG noticestates nationwide total 624,496auto-linked+313d
- AUG 25MA AGMA AG notice25,583 MA residentsauto-linked+313d
- AUG 26TX AGTX AG noticestates nationwide total 624,496auto-linked+314d
- AUG 26SC AGSC AG noticeno count statedauto-linked+314d
- SEP 2RI AGRI AG noticemost recent · 3,628 RI residentsauto-linked+321d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Sep 27, 2024 – Oct 3, 2024 OR AG
- Discovered
- Oct 7, 2024WA AG + MT AG + VT AG +6Oct 9, 2024SEC 8-KJun 3, 2025IL AG + OR AG + TX AGfilings disagree on discovery
- Data types
- Authentication · Biometric · Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII IL AG + WA AG + NE AG +9
- Attack vector
- Unauthorized Access SEC 8-K
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)
624,496
Sum of filed state slices
149,524· 23.9% of stated
76% 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.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
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 / 21.4d
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.