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

BrightSpring Health Services — March 2023 breach

Clustered 11 filings across 10 jurisdictions · filing window Jan 1, 2023 → Aug 11, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

10

Affected · reported

535,203

First → last filing

Jan 1, 2023 → Aug 11, 2023

Merge confidence

100%

incident inc_26daf57bc5944203 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Mar 12, 2023–Mar 13, 2023, discovered Mar 14, 2023. 535,203 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 222-day schedule across 11 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
67days

Range of discovered_at dates across filings

Filing span
222days

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 bdayOregon✗ OR AG >45dWashington✗ WA AG >90dMaine⏱ ME AG >30d · 83dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 12, 2023breach begins
Mar 14, 2023discovered · members disagree
Jan 1, 2023first filing
Aug 11, 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUN 21MA AGMA AG notice22 MA residents+171d
  3. JUN 21IN AGIN AG noticestates nationwide total 535,203+171d
  4. AUG 10MT AGMT AG notice2,207 MT residents+221d
  5. AUG 11VT AGVT AG noticeno count stated+222d
  6. AUG 11CA AGCA AG noticeno count stated+222d
  7. AUG 11NH AGNH AG noticeno count stated+222d
  8. AUG 11OR AGOR AG noticestates nationwide total 535,203+222d
  9. AUG 11ME AGME AG noticestates nationwide total 535,203+222d
  10. AUG 11WA AGWA AG notice28,194 WA residents+222d
  11. AUG 11MA AGMA AG noticemost recent · 2,382 MA residents+222d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 12, 2023
IN AG
Discovered
Mar 14, 2023IL AG + MT AG + VT AG +3May 20, 2023OR AG + ME AGfilings disagree on discovery
Data types
Employment · Identity (basic) · Government ID · PII
MA AG + MT AG + VT AG +4
Attack vector
Unauthorized Access
MT 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)

535,203

Sum of filed state slices

70,976· 13.3% of stated

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

US535,203
IN37,646
WA28,194
MA2,382
MT2,207
ME547

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 filing11 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
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

222 days

Cadence

~1 / 22.2d

vs. multi-state median

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

BrightSpring Health Services data breach (2023) · DisclosureLens