DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed6 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 6 filings

Lincare Holdings Inc. — September 2021 breach

Clustered 6 filings across 5 jurisdictions · filing window Feb 9, 2022 → Jun 6, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

5

Affected · reported

59,363

First → last filing

Feb 9, 2022 → Jun 6, 2022

Merge confidence

100%

incident inc_459975c4d48c46fe · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe unauthorized access. Intrusion Sep 10, 2021–Sep 29, 2021, discovered Sep 26, 2021 — the first regulatory filing landed 136 days later (flagged late). 59,363 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 3 more. Notifications rolled out on a 117-day schedule across 6 filings beginning Feb 9, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
136days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
117days

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 clocksWashington✗ WA AG >90dOregon✗ OR AG >45dCalifornia✗ CA 60-day late · 206dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 10, 2021breach begins
Sep 26, 2021discovered
notification delay · 136 days
Feb 9, 2022first filing
Jun 6, 2022most 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. FEB 9MT AGMT AG noticefirst filing · no count statedday 0
  2. FEB 15MA AGMA AG notice22,313 MA residents+6d
  3. MAR 25WA AGWA AG notice37,050 WA residents+44d
  4. APR 11OR AGOR AG noticeno count stated+61d
  5. JUN 6OR AGOR AG noticeno count stated+117d
  6. JUN 6CA AGCA AG noticemost recent · no count stated+117d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 10, 2021 – Sep 29, 2021
MT AG
Discovered
Sep 26, 2021· 16d undetected
MT AG + WA AG + OR AG +1
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + CA AG + WA AG +1
Attack vector
Unauthorized Access
MT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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 filing6 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 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

117 days

Cadence

~1 / 23.4d

vs. multi-state median

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