Confirmed breach. Intrusion May 31, 2023, discovered Oct 27, 2023 — the first regulatory filing landed 42 days later. 19,419 individuals reported across the linked filings.
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.
Regulatory clocksMaine⏱ ME AG >30d · 48dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
19,419
Data types
2
Government ID · Identity (basic)
Jurisdictions
2
FL ME
Linked filings
2
HHS OCR · State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
May 31, 2023
When the intrusion reportedly occurred, per the linked filings
149 days
Breach discoveredAG web form
Oct 27, 2023
Reported by MAINE AG filing
42 days
🇺🇸FLHHS OCRFirst filinglinked via same-victim cross-source · 100%
Independent Living Systems, LLC reported to HHS on 2023-12-08 a Hacking/IT Incident affecting 19,303 individuals. Breached information located on Network Server. A software application exposed PHI including names, DOB, addresses, SSNs, diagnoses, and claims. The entity provided credit monitoring and implemented additional safeguards.
Independent Living Systems, LLC, a healthcare entity based in Florida, reported an external system breach (hacking) occurring on May 31, 2023, discovered on October 27, 2023. The incident affected 19,419 individuals, including 9 Maine residents. Acquired data included names and Social Security Numbers. The entity provided written notification and offered two years of credit monitoring services through TransUnion/Cyberscout.
Affected (this filing): 19,419
ME AG >30d · 48d
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.