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

NATIONS DIRECT MORTGAGE, LLC — December 2023 breach

Clustered 8 filings across 8 jurisdictions · filing window Mar 1, 2024 → Apr 29, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

83,108

First → last filing

Mar 1, 2024 → Apr 29, 2024

Merge confidence

100%

incident inc_1e861e448e5c4160 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. Intrusion Dec 30, 2023, discovered Dec 30, 2023 — the first regulatory filing landed 62 days later (flagged late). 83,108 individuals reported across the linked filings. Data reported: Government ID, Financial account, and Identity (basic). Notifications rolled out on a 59-day schedule across 8 filings beginning Mar 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
62days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
59days

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 >45dWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 75dCalifornia✓ CA 60-day OK · 60dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 30, 2023breach begins
Dec 30, 2023discovered
notification delay · 62 days
Mar 1, 2024first filing
Apr 29, 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. MAR 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAR 6IN AGIN AG noticestates nationwide total 83,108+5d
  3. MAR 7WA AGWA AG notice1,862 WA residents+6d
  4. MAR 14CA AGCA AG noticeno count stated+13d
  5. MAR 14ME AGME AG noticestates nationwide total 83,108+13d
  6. MAR 15MA AGMA AG notice257 MA residents+14d
  7. MAR 15SC AGSC AG notice1,371 SC residents+14d
  8. APR 29OR AGOR AG noticemost recent · states nationwide total 83,108+59d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 30, 2023
IN AG
Discovered
Dec 30, 2023
IL AG + WA AG + CA AG +3
Data types
Financial account · Identity (basic) · Government ID
WA AG + CA AG + ME AG +2
Attack vector
Ransomware
WA 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)

83,108

Sum of filed state slices

3,752· 4.5% of stated

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

US83,108
WA1,862
SC1,371
IN259
MA257
ME3

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

59 days

Cadence

~1 / 8.4d

vs. multi-state median

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