Clustered 3 filings across 2 jurisdictions · filing window Mar 1, 2024 → Mar 18, 2024. View entity profile → Other incidents for this victim →
incident inc_d656bfb431ff4040 · merge_method llm · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
PHI · Health (basic)
IN ME
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 29, 2023
When the intrusion reportedly occurred, per the linked filings
Sep 21, 2023
Reported by MAINE AG filing
Sycamore Rehabilitation Services, Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2023-07-29 and was reported on 2024-03-01. 3,225 Indiana residents were affected. 3,414 individuals affected in total.
Affected (this filing): 3,414
Sycamore Rehabilitation Services, Inc. (Indiana) reported to HHS OCR on 2024-03-18 a Hacking/IT Incident affecting 3,414 individuals. Breached information was located on a Network Server. No business associate was present. No further details were provided in the web description.
Affected (this filing): 3,414
Sycamore Rehabilitation Services, Inc. reported a cybersecurity incident where an unauthorized third party may have accessed employee mailbox accounts. The breach occurred between July 29, 2023, and August 9, 2023, and was discovered on September 21, 2023. The investigation determined that sensitive information for 3,414 individuals may have been exposed, including names, Social Security numbers, driver's licenses, financial account information, and medical data. The company sent notification letters to affected individuals on March 1, 2024, and offered complimentary identity theft protection services.
Affected (this filing): 3,414
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.