DisclosureLens
Leak SiteHHS OCRState AGConfirmed7 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedinc_ransomhigh sensitivity
Merged incident · 7 records

WellLife Network — August 2023 breach

Clustered 7 records across 5 jurisdictions: 5 filings and 2 leak-site claims · filing window Nov 6, 2023 → Aug 29, 2024 (dated filings only). View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

7 records

States

5

Affected · reported

52,150

First → last dated filing

Nov 6, 2023 → Aug 29, 2024

Merge confidence

100%

incident inc_5f5432fdcd3d444b · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Aug 26, 2023–Sep 7, 2023, discovered Aug 26, 2023 — the first regulatory filing landed 72 days later. 52,150 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 297-day schedule across 4 dated filings beginning Nov 6, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
72days

Discovered → first regulatory filing

Discovery variance
12days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 11d

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
297days

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 >180dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 26, 2023breach begins
Aug 26, 2023discovered · members disagree
notification delay · 72 days
Nov 6, 2023first dated filing
Aug 29, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. NOV 6HHS OCRHHS OCR noticefirst filing · states nationwide total 43,875day 0
  2. NOV 17Leak siteinc_ransom postattacker claim · unverified+12d
  3. APR 16Leak siteinc_ransom postattacker claim · unverified+162d
  4. AUG 1IL AGIL AG noticefiling day not on record · no count stated—
  5. AUG 29MA AGMA AG notice7 MA residents+297d
  6. AUG 29IN AGIN AG noticestates nationwide total 52,150+297d
  7. AUG 29NH AGNH AG noticemost recent · 1 NH residents+297d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 26, 2023
IN AG
Discovered
Aug 26, 2023IL AGSep 7, 2023NH AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + MA AG + NH AG
Attack vector
Unauthorized Access
HHS OCR

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)

52,150

Sum of filed state slices

9· 0.0% of stated

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

US52,150
MA7
IN1
NH1

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 claim2 members

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing5 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

297 days

Cadence

~1 / 99d

vs. multi-state median

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