DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed11 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

FARMERS INSURANCE EXCHANGE — May 2025 breach

Clustered 11 filings across 10 jurisdictions · filing window Aug 1, 2025 → Dec 9, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

10

Affected · reported

1,071,300

First → last filing

Aug 1, 2025 → Dec 9, 2025

Merge confidence

100%

incident inc_ba33e8fe0f244258 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe a third-party compromise. Intrusion May 29, 2025–Jul 24, 2025, discovered May 30, 2025 — the first regulatory filing landed 63 days later (flagged late). 1,071,300 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 130-day schedule across 11 filings beginning Aug 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
63days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
130days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksOregon✗ OR AG >45dCalifornia✗ CA 60-day late · 84dTexas✗ TX AG >30dMaine⏱ ME AG >30d · 84dWashington⏱ WA AG >30dIowa✓ IA AG ≤5 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 29, 2025breach begins
May 30, 2025discovered
notification delay · 63 days
Aug 1, 2025first filing
Dec 9, 2025most 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. AUG 1IL AGIL AG noticefirst filing · no count statedday 0
  2. AUG 22ME AGME AG noticestates nationwide total 1,071,172+21d
  3. AUG 22NH AGNH AG notice185 NH residents+21d
  4. AUG 22NE AGNE AG noticeno count stated+21d
  5. AUG 22CA AGCA AG noticeno count stated+21d
  6. AUG 22IA AGIA AG notice4,750 IA residents+21d
  7. AUG 22MT AGMT AG notice8,252 MT residents+21d
  8. AUG 22WA AGWA AG notice45,354 WA residents+21d
  9. AUG 25OR AGOR AG noticestates nationwide total 33,729+24d
  10. DEC 3CA AGCA AG noticeno count stated+124d
  11. DEC 9TX AGTX AG noticemost recent · states nationwide total 1,071,300+130d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 29, 2025
ME AG
Discovered
May 30, 2025· 1d undetected
IL AG + ME AG + NH AG +7
Data types
Financial account · Identity (basic) · Government ID · PII
IL AG + ME AG + NH AG +6
Attack vector
Third-Party / Supply Chain
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)

1,071,300

Sum of filed state slices

236,995· 22.1% of stated

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

US1,071,300
TX178,153
WA45,354
MT8,252
IA4,750
ME301
NH185

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 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
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

130 days

Cadence

~1 / 13d

vs. multi-state median

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