DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed10 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

Lincare Holdings Inc. — September 2021 breach

Clustered 10 filings across 7 jurisdictions · filing window Feb 9, 2022 → Jan 9, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

7

Affected · reported

not comparable

First → last filing

Feb 9, 2022 → Jan 9, 2023

Merge confidence

100%

incident inc_459975c4d48c46fe · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 10 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; 4 later filings were flagged late. Data reported: Government ID, PII, Identity (basic), and 3 more. Notifications rolled out on a 334-day schedule across 10 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
334days

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 dueSouth Carolina✓ SC CRA notice 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
Jan 9, 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. FEB 9MT AGMT AG noticefirst filing · 6,657 MT residentsday 0
  2. FEB 15MA AGMA AG notice22,313 MA residents+6d
  3. FEB 23NH AGNH AG notice5 NH residents+14d
  4. MAR 25WA AGWA AG notice37,050 WA residents+44d
  5. APR 11OR AGOR AG noticeno count stated+61d
  6. JUN 6CA AGCA AG noticeno count stated+117d
  7. JUN 6OR AGOR AG noticeno count stated+117d
  8. JUN 13NH AGNH AG notice5,591 NH residents+124d
  9. JUL 18SC AGSC AG notice53,358 SC residents+159d
  10. JAN 9NH AGNH AG noticemost recent · 3,822 NH residents+334d
  11. 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 + NH AG + WA AG +3
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + CA AG + SC AG +3
Attack vector
Unauthorized Access
MT AG

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

Affected residents by state

per-state reported counts

SC53,358
WA37,050
MA22,313
MT6,657
NH5,591

State AGs report only their own residents; teal bars show each state's reported slice.

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 filing10 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 Oct 24, 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

334 days

Cadence

~1 / 37.1d

vs. multi-state median

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