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

American First Finance — May 2024 breach

Clustered 10 filings across 10 jurisdictions · filing window Jul 29, 2025 → Sep 15, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

689,000

First → last filing

Jul 29, 2025 → Sep 15, 2025

Merge confidence

100%

incident inc_4e465becff3d430b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe an insider incident. Intrusion May 31, 2024–Jun 3, 2024, discovered Jun 4, 2024 — the first regulatory filing landed 420 days later (flagged late). 689,000 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 48-day schedule across 10 filings beginning Jul 29, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
420days

Discovered → first regulatory filing

Discovery variance
379days

Range of discovered_at dates across filings

Filing span
48days

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 clocksWashington✗ WA AG >90dOregon✗ OR AG >45dTexas✗ TX AG >30dMaine⏱ ME AG >30d · 86dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 31, 2024breach begins
Jun 4, 2024discovered · members disagree
notification delay · 420 days
Jul 29, 2025first filing
Sep 15, 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. JUL 29IN AGIN AG noticefirst filing · states nationwide total 689,000day 0
  2. JUL 29NE AGNE AG noticeno count statedday 0
  3. JUL 29DE AGDE AG noticeno count statedday 0
  4. SEP 1IL AGIL AG noticeno count stated+34d
  5. SEP 12WA AGWA AG notice4,333 WA residents+45d
  6. SEP 12MA AGMA AG notice242 MA residents+45d
  7. SEP 12ME AGME AG noticestates nationwide total 689,000+45d
  8. SEP 12CA AGCA AG noticeno count stated+45d
  9. SEP 12OR AGOR AG noticestates nationwide total 689,000+45d
  10. SEP 15TX AGTX AG noticemost recent · states nationwide total 689,000+48d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 31, 2025
IN AG
Discovered
Jun 4, 2024WA AGJun 18, 2025IL AG + ME AG + OR AG +1filings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
NE AG + DE AG + WA AG +5
Attack vector
Insider
NE 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)

689,000

Sum of filed state slices

136,121· 19.8% of stated

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

US689,000
TX108,069
IN23,269
WA4,333
MA242
ME208

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

48 days

Cadence

~1 / 5.3d

vs. multi-state median

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