DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed11 records · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoneymessagehigh sensitivity
Merged incident · 11 records

PharMerica Corporation — March 2023 breach

Clustered 11 records across 10 jurisdictions: 10 filings and 1 leak-site claim · filing window May 12, 2023 → Jun 19, 2023 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 records

States

10

Affected · reported

5,815,591

First → last dated filing

May 12, 2023 → Jun 19, 2023

Merge confidence

100%

incident inc_cb5abf40e5b64654 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 12, 2023–Mar 13, 2023, discovered Mar 13, 2023. 5,815,591 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 38-day schedule across 9 dated filings beginning May 12, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
8days

Range of discovered_at dates across filings

Filing span
38days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksOregon✗ OR AG >45dLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 80dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 12, 2023breach begins
Mar 13, 2023discovered · members disagree
May 12, 2023first dated filing
Jun 19, 2023most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. APR 8Leak sitemoneymessage postfirst record · attacker claim · unverifiedday 0
  3. MAY 12OR AGOR AG noticestates nationwide total 5,815,591+34d
  4. MAY 12HHS OCRHHS OCR noticestates nationwide total 5,815,591+34d
  5. JUN 8DE AGDE AG noticeno count stated+61d
  6. JUN 8MA AGMA AG notice384,938 MA residents+61d
  7. JUN 8NH AGNH AG notice17,451 NH residents+61d
  8. JUN 8MT AGMT AG notice10,567 MT residents+61d
  9. JUN 9SC AGSC AG notice42,064 SC residents+62d
  10. JUN 9ME AGME AG noticestates nationwide total 5,815,591+62d
  11. JUN 19CA AGCA AG noticemost recent · no count stated+72d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 12, 2023 – Mar 13, 2023
OR AG
Discovered
Mar 13, 2023IL AG + NH AGMar 14, 2023DE AG + MT AG + SC AG +1Mar 21, 2023OR AG + ME AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + DE AG + MT AG +5
Attack vector
Unauthorized Access
HHS OCR

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)

5,815,591

Sum of filed state slices

495,268· 8.5% of stated

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

US5,815,591
MA384,938
SC42,064
ME40,248
NH17,451
MT10,567

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 23, 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

38 days

Cadence

~1 / 4.8d

vs. multi-state median

6.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.