DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
SEC 8-KState AGConfirmed12 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 12 filings

CENCORA, INC. — February 2024 breach

Clustered 12 filings across 5 jurisdictions · filing window Feb 27, 2024 → Jul 31, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

12 filings

States

4

Affected · reported

249,033

First → last filing

Feb 27, 2024 → Jul 31, 2024

Merge confidence

100%

incident inc_e2abec8f049a4cd1 · merged by deterministic · confidence 100%

Part of the CENCORA, INC. supply-chain incident (2024) — at least 7 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe unauthorized access. Intrusion Feb 21, 2024, discovered Feb 21, 2024 — the first regulatory filing landed 6 days later; 6 later filings were flagged late. 249,033 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Notifications rolled out on a 155-day schedule across 12 filings beginning Feb 27, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
6days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Materiality delta
0days

Discovery to SEC materiality determination

SEC filing delay
6days

Materiality determination to SEC 8-K filing

Filing span
155days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence — no leak-site claim in this cluster.

Regulatory clocksSEC✗ SEC 4-day late · 161dVermont✗ VT AG >45 bdaySouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 21, 2024breach begins
Feb 21, 2024discovered
notification delay · 6 days
Feb 27, 2024first filing
Jul 31, 2024most 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 27SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. MAY 15VT AGVT AG noticeno count stated+78d
  3. MAY 15CA AGCA AG noticeno count stated+78d
  4. MAY 21VT AGVT AG noticeno count stated+84d
  5. MAY 21DE AGDE AG noticeno count stated+84d
  6. MAY 21VT AGVT AG noticeno count stated+84d
  7. MAY 24SC AGSC AG notice249,033 SC residents+87d
  8. MAY 28DE AGDE AG noticeno count stated+91d
  9. MAY 28VT AGVT AG noticeno count stated+91d
  10. MAY 28CA AGCA AG noticeno count stated+91d
  11. JUN 7VT AGVT AG noticeno count stated+101d
  12. JUL 31SEC 8-KSEC 8-K noticemost recent · no count stated+155d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 21, 2024
CA AG
Discovered
Feb 21, 2024
SEC 8-K + VT AG + CA AG +2
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
SEC 8-K + VT AG + SC AG +2
Attack vector
Unauthorized Access
SEC 8-K

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 filing10 members

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

SEC 8-K / victim statement2 members

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

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

155 days

Cadence

~1 / 14.1d

vs. multi-state median

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