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

LOANDEPOT.COM, LLC — January 2024 breach

Clustered 10 filings across 10 jurisdictions · filing window Feb 15, 2024 → Feb 23, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

16,924,071

First → last filing

Feb 15, 2024 → Feb 23, 2024

Merge confidence

100%

incident inc_867f01ff25254071 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Jan 3, 2024–Jan 5, 2024, discovered Jan 4, 2024 — the first regulatory filing landed 42 days later (flagged late). 16,924,071 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 8-day schedule across 10 filings beginning Feb 15, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
42days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
8days

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 · 50dCalifornia✓ CA 60-day OK · 50dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueHawaii✓ HI CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 3, 2024breach begins
Jan 4, 2024discovered
notification delay · 42 days
Feb 15, 2024first filing
Feb 23, 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. FEB 15WA AGWA AG noticefirst filing · 502,513 WA residentsday 0
  2. FEB 23OR AGOR AG noticestates nationwide total 16,924,071+8d
  3. FEB 23CA AGCA AG noticeno count stated+8d
  4. FEB 23MA AGMA AG notice406,849 MA residents+8d
  5. FEB 23ME AGME AG noticestates nationwide total 16,924,071+8d
  6. FEB 23SC AGSC AG notice284,791 SC residents+8d
  7. FEB 23MT AGMT AG notice49,134 MT residents+8d
  8. FEB 23HI AGHI AG notice82,677 HI residents+8d
  9. FEB 23DE AGDE AG noticeno count stated+8d
  10. FEB 23IN AGIN AG noticemost recent · states nationwide total 16,924,071+8d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 3, 2024 – Jan 5, 2024
WA AG
Discovered
Jan 4, 2024· 1d undetected
WA AG + OR AG + CA AG +5
Data types
Financial account · Identity (basic) · Government ID · PCI
WA AG + CA AG + ME AG +5
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)

16,924,071

Sum of filed state slices

1,701,855· 10.1% of stated

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

US16,924,071
WA502,513
MA406,849
IN302,021
SC284,791
HI82,677
ME73,870
MT49,134

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

8 days

Cadence

~1 / 0.9d

vs. multi-state median

1.0× faster

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.