All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed6 filings · 5 statesUnverified claimConfirmedEnforcedqilinhigh sensitivity

Merged incident · 6 filings

Lawyers’ Mutual Insurance Company of California — May 2025 breach

Clustered 6 filings across 6 jurisdictions · filing window Jun 6, 2025 → Nov 14, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

Affected · reported

6,747

First → last filing

Jun 6, 2025 → Nov 14, 2025

Merge confidence

100%

incident inc_c752a3d6208e471e · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion May 20, 2025–May 20, 2025, discovered Oct 9, 2025 — the first regulatory filing landed 36 days later. 6,747 individuals reported across the linked filings. Data reported: Government ID, Financial account, and Identity (basic). Notifications rolled out on a 161-day schedule across 5 filings beginning Jun 6, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

36days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Leak precedence

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

161days

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 >90dMaine⏱ ME AG >30d · 36dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 20, 2025breach begins

Oct 9, 2025discovered

notification delay · 36 days

Nov 14, 2025first filing

—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

JUN 6Leak siteqilin postfirst filing · attacker claim · unverifiedoperator-confirmedday 0
NOV 14MA AGMA AG notice4 MA residentsauto-linked+161d
NOV 14IN AGIN AG noticestates nationwide total 6,747+161d
NOV 14ME AGME AG noticestates nationwide total 6,747auto-linked+161d
NOV 14CA AGCA AG noticeno count statedauto-linked+161d
NOV 14NH AGNH AG noticemost recent · 1 NH residentsauto-linked+161d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: May 20, 2025
Discovered: Oct 9, 2025· 142d undetected
Data types: Financial account · Identity (basic) · Government ID
Attack vector: Unauthorized Access

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

Sum of filed state slices

8· 0.1% of stated

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

US6,747

MA4

IN2

ME1

NH1

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

161 days

Cadence

~1 / 32.2d

vs. multi-state median

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