DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed6 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 6 filings

The Vitality Group — May 2023 breach

Clustered 6 filings across 4 jurisdictions · filing window Jun 30, 2023 → Jul 18, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

20,387

First → last filing

Jun 30, 2023 → Jul 18, 2023

Merge confidence

100%

incident inc_4fd2b19032c14798 · merged by deterministic · 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: 6 regulatory filings. The filings describe hacking. Intrusion May 30, 2023–May 30, 2023, discovered Jun 1, 2023 — the first regulatory filing landed 29 days later. 20,387 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 1 more. Notifications rolled out on a 18-day schedule across 6 filings beginning Jun 30, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
29days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
18days

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 clocksMaine⏱ ME AG >30d · 46dHIPAA✓ HHS report on timeFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 30, 2023breach begins
Jun 1, 2023discovered
notification delay · 29 days
Jun 30, 2023first filing
Jul 18, 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. JUN 30ME AGME AG noticefirst filing · states nationwide total 4,392day 0
  2. JUL 6MT AGMT AG notice4 MT residents+6d
  3. JUL 11HHS OCRHHS OCR noticestates nationwide total 20,387+11d
  4. JUL 17ME AGME AG noticestates nationwide total 2,071+17d
  5. JUL 17MT AGMT AG notice6 MT residents+17d
  6. JUL 18NH AGNH AG noticemost recent · 7 NH residents+18d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 30, 2023
ME AG
Discovered
Jun 1, 2023· 2d undetected
ME AG + MT AG + HHS OCR +1
Data types
Health (basic) · Identity (basic) · Government ID · PII
ME AG + MT AG + HHS OCR +1
Attack vector
Unauthorized Access
ME 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)

20,387

Sum of filed state slices

21· 0.1% of stated

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

US20,387
ME8
NH7
MT6

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 filing6 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 Jun 12, 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

18 days

Cadence

~1 / 3.6d

vs. multi-state median

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