DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed9 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 9 filings

INDEPENDENT LIVING SYSTEMS, LLC. — May 2023 breach

Clustered 9 filings across 7 jurisdictions · filing window Dec 8, 2023 → Dec 18, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

19,419

First → last filing

Dec 8, 2023 → Dec 18, 2023

Merge confidence

100%

incident inc_15358409a24a4faf · merged by deterministic · confidence 100%

Part of the Progress Software Corporation supply-chain incident (2023) — at least 97 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe hacking. Intrusion May 31, 2023, discovered May 31, 2023 — the first regulatory filing landed 191 days later (flagged late). 19,419 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 10-day schedule across 9 filings beginning Dec 8, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
191days

Discovered → first regulatory filing

Discovery variance
149days

Range of discovered_at dates across filings

Filing span
10days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 48dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 31, 2023breach begins
May 31, 2023discovered · members disagree
notification delay · 191 days
Dec 8, 2023first filing
Dec 18, 2023most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. DEC 8VT AGVT AG noticefirst filing · no count statedday 0
  2. DEC 8VT AGVT AG noticeno count statedday 0
  3. DEC 8MT AGMT AG notice2 MT residentsday 0
  4. DEC 8HHS OCRHHS OCR noticestates nationwide total 19,303day 0
  5. DEC 9MA AGMA AG notice39 MA residents+1d
  6. DEC 14ME AGME AG noticestates nationwide total 19,419+6d
  7. DEC 14NH AGNH AG notice1 NH residents+6d
  8. DEC 15NH AGNH AG notice18 NH residents+7d
  9. DEC 18CA AGCA AG noticemost recent · no count stated+10d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 31, 2023
ME AG
Discovered
May 31, 2023VT AG + MT AGOct 27, 2023ME AG + NH AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
VT AG + MT AG + HHS OCR +4
Attack vector
Third-Party / Supply Chain
VT AG

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)

19,419

Sum of filed state slices

68· 0.4% of stated

100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US19,419
MA39
NH18
ME9
MT2

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

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

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 9, 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

10 days

Cadence

~1 / 1.3d

vs. multi-state median

1.3× 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.