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

Singing River Health System — August 2023 breach

Clustered 12 filings across 9 jurisdictions · filing window Sep 10, 2023 → May 13, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

8

Affected · reported

895,204

First → last filing

Sep 10, 2023 → May 13, 2024

Merge confidence

100%

incident inc_56c261561f2342e2 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings and 1 unverified claim. Intrusion Aug 16, 2023–Aug 19, 2023, discovered Aug 19, 2023 — the first regulatory filing landed 60 days later (flagged late). 895,204 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 246-day schedule across 11 filings beginning Sep 10, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
60days

Discovered → first regulatory filing

Discovery variance
121days

Range of discovered_at dates across filings

Leak precedence
38days 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
246days

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 >180dCalifornia✗ CA 60-day late · 146dVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 147dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 16, 2023breach begins
Aug 19, 2023discovered · members disagree
notification delay · 60 days
Oct 18, 2023first filing
May 13, 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

  1. SEP 10Leak siterhysida postfirst filing · attacker claim · unverifiedday 0
  2. OCT 18HHS OCRHHS OCR noticestates nationwide total 895,204+38d
  3. JAN 11IN AGIN AG noticestates nationwide total 252,890+123d
  4. JAN 12CA AGCA AG noticeno count stated+124d
  5. JAN 12MT AGMT AG notice35 MT residents+124d
  6. JAN 12ME AGME AG noticestates nationwide total 252,890+124d
  7. JAN 12VT AGVT AG noticeno count stated+124d
  8. JAN 12MA AGMA AG notice181 MA residents+124d
  9. MAY 13ME AGME AG noticestates nationwide total 895,204+246d
  10. MAY 13VT AGVT AG noticeno count stated+246d
  11. MAY 13NH AGNH AG notice19 NH residents+246d
  12. MAY 13CA AGCA AG noticemost recent · no count stated+246d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 19, 2023
IN AG
Discovered
Aug 19, 2023CA AG + MT AG + VT AG +1Dec 18, 2023ME AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + CA AG + MT AG +4
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)

895,204

Sum of filed state slices

633· 0.1% of stated

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

US895,204
IN360
MA181
ME38
MT35
NH19

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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 23, 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

246 days

Cadence

~1 / 22.4d

vs. multi-state median

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