All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed5 filings · 3 statesUnverified claimConfirmedEnforcedlockbit_3high sensitivity

Merged incident · 5 filings

Valley Oaks Health — June 2023 breach

Clustered 5 filings across 4 jurisdictions · filing window Jun 20, 2023 → Mar 19, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

50,352

First → last filing

Jun 20, 2023 → Mar 19, 2024

Merge confidence

100%

incident inc_9fcda2fd22844edf · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jun 8, 2023, discovered Feb 2, 2024 — the first regulatory filing landed 45 days later (flagged late). 50,352 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 273-day schedule across 4 filings beginning Jun 20, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

45days

Discovered → first regulatory filing

Leak precedence

272days before filing

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

273days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 8, 2023breach begins

Feb 2, 2024discovered

notification delay · 45 days

Mar 18, 2024first filing

Mar 19, 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

JUN 20Leak sitelockbit_3 postfirst filing · attacker claim · unverifiedoperator-confirmedday 0
MAR 18HHS OCRHHS OCR noticestates nationwide total 50,034auto-linked+272d
MAR 18ME AGME AG noticestates nationwide total 50,352auto-linked+272d
MAR 18IN AGIN AG noticestates nationwide total 50,352auto-linked+272d
MAR 19MA AGMA AG noticemost recent · 7 MA residentsauto-linked+273d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jun 8, 2023
Discovered: Feb 2, 2024· 239d undetected
Data types: Financial account · Health (basic) · Identity (basic) · Government ID · PHI
Attack vector: Unauthorized Access

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)

50,352

Sum of filed state slices

14,975· 29.7% of stated

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

US50,352

IN14,966

MA7

ME2

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 filing4 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 22, 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

273 days

Cadence

~1 / 68.3d

vs. multi-state median

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