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

Westcor Land Title Insurance Company — January 2020 breach

Clustered 10 filings across 10 jurisdictions · filing window Aug 25, 2020 → Sep 1, 2020 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

76,067

First → last dated filing

Aug 25, 2020 → Sep 1, 2020

Merge confidence

100%

incident inc_8e31cca13e164faa · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filing describes a ransomware attack. Intrusion Jan 10, 2020–Jan 14, 2020, discovered Jan 12, 2020. 76,067 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 2 more. Notifications rolled out on a 7-day schedule across 9 dated filings beginning Aug 25, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
7days

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 clocksCalifornia✗ CA 60-day late · 226dOregon✗ OR AG >45dWashington✗ WA AG >90dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Jan 10, 2020breach begins
Jan 12, 2020discovered
Aug 25, 2020first dated filing
Sep 1, 2020most 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 about this breach

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. AUG 25MA AGMA AG noticefirst filing · 565 MA residentsday 0
  3. AUG 25IN AGIN AG noticestates nationwide total 76,067day 0
  4. AUG 25CA AGCA AG noticeno count statedday 0
  5. AUG 25OR AGOR AG noticestates nationwide total 76,067day 0
  6. AUG 25DE AGDE AG notice1,114 DE residentsday 0
  7. AUG 25WA AGWA AG notice979 WA residentsday 0
  8. AUG 25MT AGMT AG notice6 MT residentsday 0
  9. AUG 31NH AGNH AG notice151 NH residents+6d
  10. SEP 1SC AGSC AG noticemost recent · 1,030 SC residents+7d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 10, 2020
IN AG
Discovered
Jan 12, 2020· 2d undetected
IL AG + CA AG + OR AG +5
Data types
Authentication · Credentials · Identity (basic) · Government ID · PII
MA AG + DE AG + WA AG +4
Attack vector
Ransomware
DE 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)

76,067

Sum of filed state slices

4,635· 6.1% of stated

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

US76,067
DE1,114
SC1,030
WA979
IN790
MA565
NH151
MT6

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

7 days

Cadence

~1 / 0.9d

vs. multi-state median

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