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

WellDyneRx — October 2021 breach

Clustered 13 filings across 8 jurisdictions · filing window May 24, 2022 → Sep 19, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

8

Affected · reported

49,964

First → last filing

May 24, 2022 → Sep 19, 2022

Merge confidence

100%

incident inc_5fd533be0c514baf · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings. Intrusion Oct 30, 2021–Nov 17, 2021, discovered Dec 2, 2021 — the first regulatory filing landed 173 days later (flagged late). 49,964 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 3 more. Notifications rolled out on a 118-day schedule across 13 filings beginning May 24, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
173days

Discovered → first regulatory filing

Discovery variance
99days

Range of discovered_at dates across filings

Filing span
118days

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 >90d · 113dWashington✗ WA AG >90dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 30, 2021breach begins
Dec 2, 2021discovered · members disagree
notification delay · 173 days
May 24, 2022first filing
Sep 19, 2022most 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. MAY 24IN AGIN AG noticefirst filing · states nationwide total 974day 0
  2. MAY 26ME AGME AG noticestates nationwide total 974+2d
  3. MAY 26MT AGMT AG notice556 MT residents+2d
  4. JUN 27NH AGNH AG notice1 NH residents+34d
  5. JUL 1HHS OCRHHS OCR noticestates nationwide total 49,964+38d
  6. JUL 1CA AGCA AG noticeno count stated+38d
  7. JUL 1MA AGMA AG notice129 MA residents+38d
  8. JUL 2ME AGME AG noticestates nationwide total 38,401+39d
  9. JUL 5NH AGNH AG notice41 NH residents+42d
  10. SEP 15ME AGME AG noticestates nationwide total 6,441+114d
  11. SEP 15WA AGWA AG notice585 WA residents+114d
  12. SEP 15CA AGCA AG noticeno count stated+114d
  13. SEP 19NH AGNH AG noticemost recent · 31 NH residents+118d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 30, 2021
IN AG
Discovered
Dec 2, 2021MT AG + NH AG + CA AG +1Mar 11, 2022ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
ME AG + MT AG + NH AG +4
Attack vector
Phishing
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)

49,964

Sum of filed state slices

1,677· 3.4% of stated

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

US49,964
WA585
MT556
IN336
MA129
NH41
ME30

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

118 days

Cadence

~1 / 9.8d

vs. multi-state median

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