DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRState AGConfirmed22 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 22 filings

Welltok — May 2023 breach

Clustered 22 filings across 11 jurisdictions · filing window Sep 22, 2023 → May 24, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

22 filings

States

11

Affected · reported

14,782,887

First → last filing

Sep 22, 2023 → May 24, 2024

Merge confidence

100%

incident inc_167768cd2ca54fda · merged by deterministic · confidence 100%

Part of the Progress Software Corporation supply-chain incident (2023) — at least 96 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 22 regulatory filings. The filings describe hacking. Intrusion May 30, 2023–May 31, 2023, discovered Jul 26, 2023 — the first regulatory filing landed 58 days later (flagged late). 14,782,887 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 3 more. Notifications rolled out on a 245-day schedule across 22 filings beginning Sep 22, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
58days

Discovered → first regulatory filing

Discovery variance
89days

Range of discovered_at dates across filings

Filing span
245days

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 clocksCalifornia✗ CA 60-day late · 115dWashington✗ WA AG >90dMaine✗ ME AG >90d · 91dVermont✗ VT AG >45 bdayHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 30, 2023breach begins
Jul 26, 2023discovered · members disagree
notification delay · 58 days
Sep 22, 2023first filing
May 24, 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. SEP 22DE AGDE AG noticefirst filing · 10 DE residentsday 0
  2. NOV 6HHS OCRHHS OCR noticestates nationwide total 14,782,887+45d
  3. NOV 13MA AGMA AG notice227 MA residents+52d
  4. NOV 17MT AGMT AG notice14 MT residents+56d
  5. NOV 17CA AGCA AG noticeno count stated+56d
  6. NOV 18OR AGOR AG noticestates nationwide total 1,648,848+57d
  7. NOV 18WA AGWA AG notice1,606 WA residents+57d
  8. NOV 22NH AGNH AG notice363 NH residents+61d
  9. NOV 23ME AGME AG noticestates nationwide total 426,812+62d
  10. DEC 5ME AGME AG noticestates nationwide total 931,316+74d
  11. DEC 5NH AGNH AG notice116 NH residents+74d
  12. DEC 15CA AGCA AG noticeno count stated+84d
  13. DEC 15ME AGME AG noticestates nationwide total 495,331+84d
  14. DEC 15VT AGVT AG noticeno count stated+84d
  15. DEC 15NH AGNH AG notice21 NH residents+84d
  16. DEC 22NH AGNH AG notice642 NH residents+91d
  17. DEC 22ME AGME AG noticestates nationwide total 1,930,870+91d
  18. DEC 22VT AGVT AG noticeno count stated+91d
  19. DEC 22CA AGCA AG noticeno count stated+91d
  20. JAN 8CA AGCA AG noticeno count stated+108d
  21. FEB 28CA AGCA AG noticeno count stated+159d
  22. MAY 24SC AGSC AG noticemost recent · 135,359 SC residents+245d
  23. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 30, 2023
DE AG
Discovered
Jul 26, 2023DE AG + MT AG + CA AG +4Sep 22, 2023ME AGOct 13, 2023OR AGOct 23, 2023ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
DE AG + HHS OCR + MT AG +7
Attack vector
Unauthorized Access
DE 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)

14,782,887

Sum of filed state slices

138,254· 0.9% of stated

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

US14,782,887
SC135,359
WA1,606
NH642
ME396
MA227
MT14
DE10

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 filing22 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
Reviewed
operator-reviewed Aug 10, 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

245 days

Cadence

~1 / 11.7d

vs. multi-state median

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