DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed12 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedalphvcritical sensitivity
Merged incident · 12 filings

NORTON HEALTHCARE, INC. — May 2023 breach

Clustered 12 filings across 12 jurisdictions · filing window Jan 1, 2023 → Dec 13, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

11

Affected · reported

2,500,000

First → last filing

Jan 1, 2023 → Dec 13, 2023

Merge confidence

100%

incident inc_0005378551304861 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings and 1 unverified claim. Intrusion May 7, 2023–May 9, 2023, discovered May 7, 2023. 2,500,000 individuals reported across the linked filings. Data reported: Government ID, Minor, Health (basic), and 6 more. Notifications rolled out on a 346-day schedule across 11 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
2days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 144d

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
346days

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 >180dVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 213dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_governmentminor

Incident timeline

May 7, 2023breach begins
May 7, 2023discovered · members disagree
Jan 1, 2023first filing
Dec 13, 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAY 25Leak sitealphv postattacker claim · unverified+144d
  3. JUL 7HHS OCRHHS OCR noticestates nationwide total 2,500,000+187d
  4. DEC 8WA AGWA AG notice1,872 WA residents+341d
  5. DEC 8SC AGSC AG notice3,674 SC residents+341d
  6. DEC 8VT AGVT AG noticeno count stated+341d
  7. DEC 8MT AGMT AG notice310 MT residents+341d
  8. DEC 8CA AGCA AG noticeno count stated+341d
  9. DEC 8MA AGMA AG notice1,324 MA residents+341d
  10. DEC 8ME AGME AG noticestates nationwide total 2,500,000+341d
  11. DEC 11NH AGNH AG notice356 NH residents+344d
  12. DEC 13OR AGOR AG noticemost recent · states nationwide total 2,500,000+346d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 7, 2023 – May 9, 2023
WA AG
Discovered
May 7, 2023IL AGMay 9, 2023WA AG + SC AG + VT AG +4filings disagree on discovery
Data types
Authentication · Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PCI · PHI
HHS OCR + WA AG + SC AG +6
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)

2,500,000

Sum of filed state slices

7,921· 0.3% of stated

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

US2,500,000
SC3,674
WA1,872
MA1,324
ME385
NH356
MT310

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 filing11 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 9, 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

346 days

Cadence

~1 / 31.5d

vs. multi-state median

43.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.