DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed11 records · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedbianlianhigh sensitivity
Merged incident · 11 records

Affiliated Dermatologists and Dermatologic Surgeons PA — March 2024 breach

Clustered 11 records across 10 jurisdictions: 10 filings and 1 leak-site claim · filing window May 3, 2024 → May 28, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 records

States

10

Affected · reported

373,680

First → last filing

May 3, 2024 → May 28, 2024

Merge confidence

100%

incident inc_a78258387f07483a · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. Intrusion Mar 2, 2024–Mar 5, 2024, discovered Mar 5, 2024 — the first regulatory filing landed 59 days later; 1 later filing was flagged late. 373,680 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 5 more. Notifications rolled out on a 25-day schedule across 10 filings beginning May 3, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
59days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
38days before filing

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

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 79dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Mar 2, 2024breach begins
Mar 5, 2024discovered
notification delay · 59 days
May 3, 2024first filing
May 28, 2024most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

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

  1. MAR 26Leak sitebianlian postfirst record · attacker claim · unverifiedday 0
  2. MAY 3DE AGDE AG noticeno count stated+37d
  3. MAY 3HHS OCRHHS OCR noticestates nationwide total 373,680+37d
  4. MAY 23IN AGIN AG noticestates nationwide total 373,379+57d
  5. MAY 23MA AGMA AG notice703 MA residents+57d
  6. MAY 23SC AGSC AG notice1,199 SC residents+57d
  7. MAY 23VT AGVT AG noticeno count stated+57d
  8. MAY 23MT AGMT AG notice28 MT residents+57d
  9. MAY 23ME AGME AG noticestates nationwide total 373,379+57d
  10. MAY 23CA AGCA AG noticeno count stated+57d
  11. MAY 28NH AGNH AG noticemost recent · 200 NH residents+62d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 2, 2024 – Mar 5, 2024
DE AG
Discovered
Mar 5, 2024· 3d undetected
DE AG + SC AG + VT AG +4
Data types
Employment · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
DE AG + HHS OCR + CA AG +6
Attack vector
Ransomware
DE 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)

373,680

Sum of filed state slices

2,412· 0.6% of stated

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

US373,680
SC1,199
MA703
NH200
ME194
IN88
MT28

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 filing10 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

25 days

Cadence

~1 / 2.8d

vs. multi-state median

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