DisclosureLens
Leak SiteHHS OCRState AGConfirmed6 records · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 6 records

Southern Illinois Dermatology

Clustered 6 records across 4 jurisdictions: 5 filings and 1 leak-site claim · filed Apr 2, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 records

States

4

Affected · reported

160,312

First → last dated filing

Apr 2, 2026

Merge confidence

100%

incident inc_b8b564f913cd4b7a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Discovered Nov 28, 2025. 160,312 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Financial account, and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Filing span
0days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

? — ?breach window unknown
Nov 28, 2025discovered
Apr 2, 2026first dated filing
—watching for filings

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 28Leak siteinsomnia postfirst record · attacker claim · unverifiedday 0
  2. APR 1IL AGIL AG noticefiling day not on record · no count stated—
  3. APR 2MA AGMA AG notice8 MA residents+125d
  4. APR 2VT AGVT AG noticeno count stated+125d
  5. APR 2NE AGNE AG noticefiling day not on record · no count stated—
  6. APR 2HHS OCRHHS OCR noticemost recent · states nationwide total 160,312+125d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
—
Discovered
Nov 28, 2025
IL AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
IL AG + MA AG + HHS OCR +2
Attack vector
Unauthorized Access
VT 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)

160,312

Sum of filed state slices

8· 0.0% of stated

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

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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.0× faster

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.