All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed13 filings · 11 statesUnverified claimConfirmedEnforcedlockbit_3high sensitivity

Merged incident · 13 filings

LIVANOVA USA, INC. — October 2023 breach

Clustered 13 filings across 12 jurisdictions · filing window Dec 8, 2023 → Jul 30, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

Affected · reported

129,219

First → last filing

Dec 8, 2023 → Jul 30, 2024

Merge confidence

100%

incident inc_7dfe7b20e3f54182 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. Intrusion Oct 24, 2023–Nov 23, 2023, discovered Nov 19, 2023 — the first regulatory filing landed 159 days later (flagged late). 129,219 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 6 more. Notifications rolled out on a 235-day schedule across 12 filings beginning Dec 8, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

159days

Discovered → first regulatory filing

Discovery variance

183days

Range of discovered_at dates across filings

Leak precedence

140days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span

235days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 215dCalifornia✗ CA 60-day late · 254dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 24, 2023breach begins

Nov 19, 2023discovered · members disagree

notification delay · 159 days

Apr 26, 2024first filing

Jul 30, 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

DEC 8Leak sitelockbit_3 postfirst filing · attacker claim · unverifiedauto-linkedday 0
APR 26HHS OCRHHS OCR noticestates nationwide total 129,031+140d
MAY 1IL AGIL AG noticeno count statedauto-linked+145d
MAY 23MT AGMT AG notice1 MT residentsauto-linked+167d
MAY 24MA AGMA AG notice1,375 MA residentsauto-linked+168d
MAY 31IN AGIN AG noticestates nationwide total 188auto-linked+175d
MAY 31VT AGVT AG noticeno count statedauto-linked+175d
JUN 21ME AGME AG noticestates nationwide total 129,219auto-linked+196d
JUN 21CA AGCA AG noticeno count statedauto-linked+196d
JUN 21OR AGOR AG noticestates nationwide total 129,219auto-linked+196d
JUN 21WA AGWA AG notice2,116 WA residentsauto-linked+196d
JUN 24SC AGSC AG notice1,695 SC residentsauto-linked+199d
JUL 30CA AGCA AG noticemost recent · no count statedauto-linked+235d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Oct 26, 2023
Discovered: Nov 19, 2023IL AG + MT AG + VT AG +4May 20, 2024OR AGfilings disagree on discovery
Data types: Credentials · Employment · Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
Attack vector: Unauthorized Access

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)

129,219

Sum of filed state slices

5,680· 4.4% of stated

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

US129,219

WA2,116

SC1,695

MA1,375

ME490

IN3

MT1

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

235 days

Cadence

~1 / 19.6d

vs. multi-state median

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