DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
SEC 8-KState AGConfirmed9 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedalphvhigh sensitivity
Merged incident · 9 filings

HENRY SCHEIN, INC. — September 2023 breach

Clustered 9 filings across 9 jurisdictions · filing window Nov 16, 2023 → Jan 26, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

29,112

First → last filing

Nov 16, 2023 → Jan 26, 2024

Merge confidence

100%

incident inc_5f8b3f41666049e3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Sep 27, 2023–Dec 5, 2023, discovered Oct 14, 2023 — the first regulatory filing landed 33 days later (flagged late). 29,112 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 7 more. Notifications rolled out on a 71-day schedule across 9 filings beginning Nov 16, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
33days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Materiality delta
2days

Discovery to SEC materiality determination

SEC filing delay
31days

Materiality determination to SEC 8-K filing

Filing span
71days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksWashington✗ WA AG >90dVermont⏱ VT AG >14 bdayMaine⏱ ME AG >30d · 53dSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueCalifornia✓ CA 60-day OK · 34dFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentialsidentity_government

Incident timeline

Sep 27, 2023breach begins
Oct 14, 2023discovered
notification delay · 33 days
Nov 16, 2023first filing
Jan 26, 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. NOV 16SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. NOV 16NH AGNH AG notice104 NH residentsday 0
  3. NOV 17MT AGMT AG notice445 MT residents+1d
  4. NOV 17VT AGVT AG noticeno count stated+1d
  5. NOV 28SC AGSC AG notice2,921 SC residents+12d
  6. DEC 6MA AGMA AG notice408 MA residents+20d
  7. DEC 6ME AGME AG noticestates nationwide total 29,112+20d
  8. DEC 6CA AGCA AG noticeno count stated+20d
  9. JAN 26WA AGWA AG noticemost recent · 1,953 WA residents+71d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 14, 2023
SEC 8-K
Discovered
Oct 14, 2023
SEC 8-K + NH AG + MT AG +5
Data types
Authentication · Employment · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · Location · PCI · PHI
NH AG + MT AG + VT AG +5
Attack vector
Unauthorized Access
NH 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)

29,112

Sum of filed state slices

5,869· 20.2% of stated

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

US29,112
SC2,921
WA1,953
MT445
MA408
NH104
ME38

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

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

SEC 8-K / victim statement1 member

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

71 days

Cadence

~1 / 8.9d

vs. multi-state median

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