DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed13 filings · 12 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedalphvcritical sensitivity
Merged incident · 13 filings

ZOLL Medical — January 2023 breach

Clustered 13 filings across 12 jurisdictions · filing window Jan 1, 2023 → Mar 13, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

12

Affected · reported

1,004,443

First → last filing

Jan 1, 2023 → Mar 13, 2023

Merge confidence

100%

incident inc_7aa35f2b3bec4270 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings. The filings describe unauthorized access. Intrusion Jan 28, 2023–Feb 2, 2023, discovered Jan 28, 2023. 1,004,443 individuals reported across the linked filings. Data reported: Government ID, Minor, Identity (basic), and 5 more. Notifications rolled out on a 71-day schedule across 13 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
5days

Range of discovered_at dates across filings

Filing span
71days

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 >14 bdayWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 41dSouth Carolina✓ SC CRA notice dueCalifornia✓ CA 60-day OK · 41dMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Jan 28, 2023breach begins
Jan 28, 2023discovered · members disagree
Jan 1, 2023first filing
Mar 13, 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. JAN 1IL AGIL AG noticeno count statedday 0
  3. MAR 10VT AGVT AG noticestates nationwide total 107,074+68d
  4. MAR 10IN AGIN AG noticestates nationwide total 1,004,443+68d
  5. MAR 10WA AGWA AG notice6,176 WA residents+68d
  6. MAR 10SC AGSC AG notice7,052 SC residents+68d
  7. MAR 10MT AGMT AG notice773 MT residents+68d
  8. MAR 10CA AGCA AG noticeno count stated+68d
  9. MAR 10DE AGDE AG notice105,306 DE residents+68d
  10. MAR 10ME AGME AG noticestates nationwide total 1,004,443+68d
  11. MAR 10MA AGMA AG notice3,126 MA residents+68d
  12. MAR 10OR AGOR AG noticestates nationwide total 1,004,443+68d
  13. MAR 13NH AGNH AG noticemost recent · states nationwide total 106,759+71d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 2, 2023
VT AG
Discovered
Jan 28, 2023IL AG + VT AG + WA AG +7Feb 2, 2023IL AGfilings disagree on discovery
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PHI · PII
VT AG + WA AG + SC AG +6
Attack vector
Unauthorized Access
VT 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)

1,004,443

Sum of filed state slices

130,795· 13.0% of stated

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

US1,004,443
DE105,306
SC7,052
IN6,922
WA6,176
MA3,126
MT773
ME760
NH680

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

71 days

Cadence

~1 / 5.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.