Doctor Alliance — October 2025 breach
Clustered 4 filings across 3 jurisdictions · filing window Nov 6, 2025 → Apr 3, 2026. View entity profile → Other incidents for this victim →
incident inc_e48a16c1b8494407 · merged by human · confidence 100%
Litigation Timing
SupplementalDiscovered → first regulatory filing
Range of discovered_at dates across filings
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.
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- NOV 6Leak sitekazu postfirst filing · attacker claim · unverifiedoperator-confirmedday 0
- MAR 12MA AGMA AG noticeno count stated+126d
- MAR 12ME AGME AG noticestates nationwide total 6,746auto-linked+126d
- APR 3MA AGMA AG noticemost recent · no count statedoperator-confirmed+148d
- 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 AGMar 2, 2026ME AGfilings disagree on discovery
- Data types
- Identity (basic) · Government ID · Health (basic) MA AG + ME AG
- Attack vector
- Unauthorized Access ME AG
- Response
- Initiated an investigation of the matter · Engaged cybersecurity experts to assist with the process · Undertook a comprehensive review of those files MA 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)
6,746
Sum of filed state slices
7· 0.1% 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
Attacker assertion only. Establishes: claim date, group, alleged victim.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
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 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
148 days
Cadence
~1 / 49.3d
vs. multi-state median
29.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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.