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

Doctor Alliance — October 2025 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 records

States

4

Affected · reported

17,000

First → last dated filing

Nov 16, 2025 → Apr 3, 2026

Merge confidence

100%

incident inc_e48a16c1b8494407 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Oct 31, 2025–Nov 17, 2025, discovered Nov 13, 2025 — the first regulatory filing landed 3 days later; 2 later filings were flagged late. 17,000 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 1 more. Notifications rolled out on a 138-day schedule across 4 dated filings beginning Nov 16, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
3days

Discovered → first regulatory filing

Discovery variance
109days

Range of discovered_at dates across filings

Leak precedence
5days 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
138days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMassachusetts✗ MA AG >90dLeak gap⏱ Leak >90dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 31, 2025breach begins
Nov 13, 2025discovered · members disagree
notification delay · 3 days
Nov 16, 2025first dated filing
Apr 3, 2026most recent dated filing

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 6Leak sitekazu postfirst record · attacker claim · unverifiedday 0
  2. NOV 16HHS OCRHHS OCR noticestates nationwide total 17,000+10d
  3. MAR 1IL AGIL AG noticefiling day not on record · no count stated—
  4. MAR 12MA AGMA AG notice6,565 MA residents+126d
  5. MAR 12ME AGME AG noticestates nationwide total 6,746+126d
  6. APR 3MA AGMA AG noticemost recent · 8,812 MA residents+148d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 31, 2025 – Nov 17, 2025
MA AG
Discovered
Nov 13, 2025MA AGNov 16, 2025MA AGFeb 23, 2026IL AGMar 2, 2026ME AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI
HHS OCR + IL AG + MA AG +1
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)

17,000

Sum of filed state slices

8,819· 51.9% of stated

48% 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Sep 28, 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

138 days

Cadence

~1 / 46d

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.