DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRSEC 8-KState AGConfirmed8 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedthegentlemenhigh sensitivity
Merged incident · 8 filings

Veradigm LLC — December 2025 breach

Clustered 8 filings across 8 jurisdictions · filing window Sep 22, 2025 → Sep 8, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

2,672,036

First → last filing

Sep 22, 2025 → Sep 8, 2026

Merge confidence

100%

incident inc_cef4d1dcdb3048c8 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion Dec 15, 2025. 2,672,036 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 3 more. Notifications rolled out on a 351-day schedule across 7 filings beginning Sep 22, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Leak precedence
Noneclaim trailed by 347d

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

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delay — needs two dated filings.

Regulatory clocksSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 15, 2025breach begins
Sep 22, 2025first filing
Sep 8, 2026most recent filing

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.

Member cascade — every filing about this breach

  1. SEP 22CA AGCA AG noticefirst filing · no count statedday 0
  2. SEP 22SC AGSC AG notice23,491 SC residentsday 0
  3. SEP 22MA AGMA AG notice362 MA residentsday 0
  4. SEP 22VT AGVT AG noticeno count statedday 0
  5. SEP 22HHS OCRHHS OCR noticestates nationwide total 2,672,036day 0
  6. SEP 22MT AGMT AG notice3,946 MT residentsday 0
  7. SEP 4Leak sitethegentlemen postattacker claim · unverified+347d
  8. SEP 8SEC 8-KSEC 8-K noticemost recent · no count stated+352d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 15, 2025
CA AG
Discovered
—
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
CA AG + SC AG + VT AG +4
Attack vector
Unauthorized Access
CA 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)

2,672,036

Sum of filed state slices

27,799· 1.0% of stated

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

US2,672,036
SC23,491
MT3,946
MA362

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 filing6 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Sep 14, 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

351 days

Cadence

~1 / 50.1d

vs. multi-state median

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