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

FIRST AMERICAN FINANCIAL CORPORATION — December 2023 breach

Clustered 11 filings across 11 jurisdictions · filing window May 28, 2024 → Jun 11, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

45,031

First → last filing

May 28, 2024 → Jun 11, 2024

Merge confidence

100%

incident inc_416b618e9ec248bb · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Dec 18, 2023–Jan 2, 2024, discovered Dec 18, 2023 — the first regulatory filing landed 162 days later (flagged late). 45,031 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 4 more. Notifications rolled out on a 14-day schedule across 11 filings beginning May 28, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
162days

Discovered → first regulatory filing

Discovery variance
366days

Range of discovered_at dates across filings

SEC filing delay
7days

Materiality determination to SEC 8-K filing

Filing span
14days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta — no leak-site claim in this cluster.

Regulatory clocksOregon✗ OR AG >45dWashington✗ WA AG >90dMaine✗ ME AG >90d · 175dVermont✗ VT AG >45 bdayMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 18, 2023breach begins
Dec 18, 2023discovered · members disagree
notification delay · 162 days
May 28, 2024first filing
Jun 11, 2024most 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. MAY 28SEC 8-KSEC 8-K noticefirst filing · 44,000 affectedday 0
  2. JUN 1IL AGIL AG noticeno count stated+4d
  3. JUN 10MT AGMT AG notice72 MT residents+13d
  4. JUN 10OR AGOR AG noticestates nationwide total 41,638+13d
  5. JUN 10WA AGWA AG notice706 WA residents+13d
  6. JUN 10ME AGME AG noticestates nationwide total 41,638+13d
  7. JUN 10VT AGVT AG noticeno count stated+13d
  8. JUN 10IN AGIN AG noticestates nationwide total 41,683+13d
  9. JUN 10CA AGCA AG noticeno count stated+13d
  10. JUN 11NH AGNH AG notice30 NH residents+14d
  11. JUN 11MA AGMA AG noticemost recent · 223 MA residents+14d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 18, 2023 – Jan 2, 2024
OR AG
Discovered
Dec 18, 2023MT AG + OR AG + WA AG +3Dec 18, 2024IL AGfilings disagree on discovery
Data types
Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
SEC 8-K + NH AG + MT AG +5
Attack vector
Unauthorized Access
SEC 8-K

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)

41,683

Sum of filed state slices

4,012· 9.6% of stated

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

US41,683
IN2,926
WA706
MA223
MT72
ME55
NH30

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

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 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

14 days

Cadence

~1 / 1.4d

vs. multi-state median

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