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

Academic Urology & Urogynecology of Arizona — May 2025 breach

Clustered 8 filings across 8 jurisdictions · filing window Jun 17, 2025 → Mar 1, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

73,281

First → last filing

Jun 17, 2025 → Mar 1, 2026

Merge confidence

100%

incident inc_ca767ca820f14d31 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion May 18, 2025–May 22, 2025, discovered May 22, 2025 — the first regulatory filing landed 266 days later (flagged late). 73,281 individuals reported across the linked filings. Data reported: Government ID, PII, PHI, and 3 more. Notifications rolled out on a 257-day schedule across 7 filings beginning Jun 17, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
266days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
240days 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
257days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine✗ ME AG >90d · 266dLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayMassachusetts✗ MA AG >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 18, 2025breach begins
May 22, 2025discovered
notification delay · 266 days
Feb 12, 2026first filing
Mar 1, 2026most 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 17Leak siteinc_ransom postfirst filing · attacker claim · unverifiedday 0
  2. FEB 12ME AGME AG noticestates nationwide total 73,281+240d
  3. FEB 12NE AGNE AG noticeno count stated+240d
  4. FEB 12VT AGVT AG noticeno count stated+240d
  5. FEB 13NH AGNH AG notice2 NH residents+241d
  6. FEB 13MA AGMA AG noticeno count stated+241d
  7. FEB 13HHS OCRHHS OCR noticestates nationwide total 73,281+241d
  8. MAR 1IL AGIL AG noticemost recent · no count stated+257d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 18, 2025 – May 22, 2025
ME AG
Discovered
May 22, 2025· 4d undetected
ME AG + NE AG + VT AG +3
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
ME AG + NE AG + MA AG +4
Attack vector
Unauthorized Access
ME 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)

73,281

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

257 days

Cadence

~1 / 36.7d

vs. multi-state median

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