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

1ST FRANKLIN FINANCIAL CORPORATION — November 2022 breach

Clustered 8 filings across 8 jurisdictions · filing window Jan 10, 2023 → Mar 23, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

147,908

First → last filing

Jan 10, 2023 → Mar 23, 2023

Merge confidence

100%

incident inc_b5101188e9924815 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. Intrusion Nov 17, 2022–Nov 18, 2022, discovered Nov 17, 2022 — the first regulatory filing landed 54 days later; 1 later filing was flagged late. 147,908 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 72-day schedule across 8 filings beginning Jan 10, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
54days

Discovered → first regulatory filing

Discovery variance
28days

Range of discovered_at dates across filings

Filing span
72days

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 · 89dMaine⏱ ME AG >30d · 34dSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 17, 2022breach begins
Nov 17, 2022discovered · members disagree
notification delay · 54 days
Jan 10, 2023first filing
Mar 23, 2023most 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. JAN 10IN AGIN AG noticefirst filing · 472 IN residentsday 0
  2. JAN 18ME AGME AG notice2 ME residents+8d
  3. FEB 22SC AGSC AG notice147,192 SC residents+43d
  4. MAR 2VT AGVT AG noticeno count stated+51d
  5. MAR 2MT AGMT AG notice57 MT residents+51d
  6. MAR 2NH AGNH AG notice49 NH residents+51d
  7. MAR 9MA AGMA AG notice136 MA residents+58d
  8. MAR 23CA AGCA AG noticemost recent · no count stated+72d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 17, 2022
IN AG
Discovered
Nov 17, 2022SC AG + MT AG + CA AGNov 18, 2022NH AGDec 15, 2022ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
ME AG + SC AG + VT AG +4
Attack vector
Unauthorized Access
ME AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

SC147,192
IN472
MA136
MT57
NH49
ME2

State AGs report only their own residents; teal bars show each state's reported slice.

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

72 days

Cadence

~1 / 10.3d

vs. multi-state median

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