DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed11 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0phigh sensitivity
Merged incident · 11 filings

Nuance Communications, Inc — May 2023 breach

Clustered 11 filings across 10 jurisdictions · filing window Jan 1, 2023 → Sep 19, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

9

Affected · reported

1,225,054

First → last filing

Jan 1, 2023 → Sep 19, 2023

Merge confidence

100%

incident inc_a4d5887cab7a4863 · merged by human · confidence 100%

Part of the Progress Software Corporation supply-chain incident (2023) — at least 97 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion May 28, 2023–May 29, 2023, discovered May 28, 2023. 1,225,054 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 261-day schedule across 10 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
43days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 166d

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

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 >180dCalifornia✗ CA 60-day late · 62dOregon✗ OR AG >45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 28, 2023breach begins
May 28, 2023discovered · members disagree
Jan 1, 2023first filing
Sep 19, 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. JUN 16Leak sitecl0p postattacker claim · unverified+166d
  4. SEP 15MT AGMT AG notice547 MT residents+257d
  5. SEP 15CA AGCA AG noticeno count stated+257d
  6. SEP 15HHS OCRHHS OCR noticestates nationwide total 1,225,054+257d
  7. SEP 15WA AGWA AG notice7,993 WA residents+257d
  8. SEP 15ME AGME AG notice1 ME residents+257d
  9. SEP 15NH AGNH AG notice1,259 NH residents+257d
  10. SEP 18DE AGDE AG noticeno count stated+260d
  11. SEP 19OR AGOR AG noticemost recent · states nationwide total 1,225,054+261d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 28, 2023 – May 29, 2023
MT AG
Discovered
May 28, 2023IL AGMay 31, 2023MT AG + CA AG + WA AG +2Jul 10, 2023ME AG + OR AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + CA AG + HHS OCR +4
Attack vector
Third-Party / Supply Chain
MT 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,225,054

Sum of filed state slices

9,800· 0.8% of stated

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

US1,225,054
WA7,993
NH1,259
MT547
ME1

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 filing10 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 25, 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

261 days

Cadence

~1 / 26.1d

vs. multi-state median

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