Community Care Alliance — June 2024 breach
Clustered 11 records across 7 jurisdictions: 9 filings, 1 press report and 1 leak-site claim · filing window Mar 1, 2025 → Mar 10, 2025. View entity profile → Other incidents for this victim →
incident inc_41c1d847682a437f · 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.
Member cascade — every filing and leak-site claim in this incident
- JUL 6Leak siterhysida postfirst record · attacker claim · unverifiedoperator-confirmedday 0
- MAR 1HHS OCRHHS OCR noticestates nationwide total 114,975operator-confirmed+238d
- MAR 1HHS OCRHHS OCR noticestates nationwide total 111,804auto-linked+238d
- MAR 7IN AGIN AG noticestates nationwide total 114,945operator-confirmed+244d
- MAR 7MT AGMT AG notice7 MT residentsoperator-confirmed+244d
- MAR 7ME AGME AG noticestates nationwide total 114,945operator-confirmed+244d
- MAR 7VT AGVT AG noticeno count statedoperator-confirmed+244d
- MAR 7MD AGMD AG notice14 MD residentsoperator-confirmed+244d
- MAR 8MA AGMA AG notice1,675 MA residentsoperator-confirmed+245d
- MAR 10RI AGRI AG noticemost recent · 95,052 RI residentsauto-linked+247d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Jun 20, 2024 IN AG
- Discovered
- Jul 6, 2024HHS OCR + MT AG + MD AG +1Jan 8, 2025ME AG + VT AGfilings disagree on discovery
- Data types
- Financial account · Health (basic) · Identity (basic) · Government ID · PHI HHS OCR + MT AG + ME AG +4
- 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)
114,975
Sum of filed state slices
96,802· 84.2% of stated
16% 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.
Unlocks: incident narrative, operational impact. Still no compliance clock.
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
9 days
Cadence
~1 / 1.1d
vs. multi-state median
1.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.