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

Asheville Eye Associates, PLLC — November 2024 breach

Clustered 11 filings across 10 jurisdictions · filing window Nov 18, 2024 → Jun 13, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

9

Affected · reported

327,756

First → last filing

Nov 18, 2024 → Jun 13, 2025

Merge confidence

100%

incident inc_ebcfc3eef5214237 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Nov 14, 2024–Nov 18, 2024, discovered Nov 18, 2024 — the first regulatory filing landed 60 days later (flagged late). 327,756 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 207-day schedule across 9 filings beginning Nov 18, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
60days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
60days 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
207days

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 · 207dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 14, 2024breach begins
Nov 18, 2024discovered
notification delay · 60 days
Jan 17, 2025first filing
Jun 13, 2025most 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. NOV 18Leak sitedragonforce postfirst filing · attacker claim · unverifiedday 0
  2. DEC 28Leak sitedragonforce postattacker claim · unverified+40d
  3. JAN 17HHS OCRHHS OCR noticestates nationwide total 327,756+60d
  4. JUN 13VT AGVT AG noticeno count stated+207d
  5. JUN 13SC AGSC AG notice2,046 SC residents+207d
  6. JUN 13ME AGME AG noticestates nationwide total 147,116+207d
  7. JUN 13NE AGNE AG noticeno count stated+207d
  8. JUN 13MA AGMA AG notice54 MA residents+207d
  9. JUN 13NH AGNH AG notice21 NH residents+207d
  10. JUN 13MT AGMT AG notice29 MT residents+207d
  11. JUN 13IN AGIN AG noticemost recent · states nationwide total 147,116+207d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 18, 2024
ME AG
Discovered
Nov 18, 2024
VT AG + SC AG + ME AG +3
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + NH AG + VT AG +5
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)

327,756

Sum of filed state slices

2,279· 0.7% of stated

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

US327,756
SC2,046
IN94
MA54
ME35
MT29
NH21

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 claim2 members

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 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 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

207 days

Cadence

~1 / 20.7d

vs. multi-state median

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