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

Panorama Eyecare — May 2023 breach

Clustered 9 filings across 8 jurisdictions · filing window Jun 3, 2023 → Jun 10, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

377,911

First → last filing

Jun 3, 2023 → Jun 10, 2024

Merge confidence

100%

incident inc_999a6815e7b143ec · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion May 22, 2023–Jun 4, 2023, discovered May 22, 2023 — the first regulatory filing landed 376 days later (flagged late). 377,911 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 373-day schedule across 7 filings beginning Jun 3, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
376days

Discovered → first regulatory filing

Discovery variance
353days

Range of discovered_at dates across filings

Leak precedence
364days 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
373days

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 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 22, 2023breach begins
May 22, 2023discovered · members disagree
notification delay · 376 days
Jun 1, 2024first filing
Jun 10, 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. JUN 3Leak sitelockbit_3 postfirst filing · attacker claim · unverifiedday 0
  2. JUL 11Leak sitelockbit_3 postattacker claim · unverified+38d
  3. JUN 1IL AGIL AG noticeno count stated+364d
  4. JUN 5HHS OCRHHS OCR noticestates nationwide total 377,911+368d
  5. JUN 5ME AGME AG noticestates nationwide total 377,911+368d
  6. JUN 5MA AGMA AG notice79 MA residents+368d
  7. JUN 5MT AGMT AG notice187 MT residents+368d
  8. JUN 5VT AGVT AG noticeno count stated+368d
  9. JUN 10NH AGNH AG noticemost recent · 37 NH residents+373d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 22, 2023 – Jun 4, 2023
ME AG
Discovered
May 22, 2023IL AGJun 3, 2023MT AG + VT AG + NH AGMay 9, 2024ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + MA AG + VT AG +3
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)

377,911

Sum of filed state slices

337· 0.1% of stated

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

US377,911
MT187
MA79
NH37
ME34

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 filing7 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 25, 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

373 days

Cadence

~1 / 46.6d

vs. multi-state median

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