DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed12 records · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforceddispossessorhigh sensitivity
Merged incident · 12 records

PLANET HOME LENDING, LLC — November 2023 breach

Clustered 12 records across 10 jurisdictions: 11 filings and 1 leak-site claim · filing window Jan 23, 2024 → Feb 15, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

12 records

States

10

Affected · reported

284,974

First → last dated filing

Jan 23, 2024 → Feb 15, 2024

Merge confidence

100%

incident inc_30693e2e717c4007 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings and 1 unverified claim. Intrusion Nov 15, 2023, discovered Nov 15, 2023. 284,974 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 23-day schedule across 10 dated filings beginning Jan 23, 2024. 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
23days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksCalifornia✗ CA 60-day late · 70dOregon✗ OR AG >45dWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 72dSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 15, 2023breach begins
Nov 15, 2023discovered
Jan 23, 2024first dated filing
Feb 15, 2024most 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 and leak-site claim in this incident

  1. NOV 17Leak sitelockbit_3 postfirst record · attacker claim · unverifiedday 0
  2. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JAN 23WA AGWA AG notice7,194 WA residents+67d
  4. JAN 24MT AGMT AG notice1,971 MT residents+68d
  5. JAN 25DE AGDE AG noticeno count stated+69d
  6. JAN 25IN AGIN AG noticestates nationwide total 284,974+69d
  7. JAN 26ME AGME AG noticestates nationwide total 199,873+70d
  8. FEB 9CA AGCA AG noticeno count stated+84d
  9. FEB 9ME AGME AG noticestates nationwide total 284,974+84d
  10. FEB 9SC AGSC AG notice3,846 SC residents+84d
  11. FEB 9OR AGOR AG noticestates nationwide total 284,974+84d
  12. FEB 15MA AGMA AG noticemost recent · 2,142 MA residents+90d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 15, 2023
WA AG
Discovered
Nov 15, 2023
IL AG + WA AG + MT AG +5
Data types
Financial account · Identity (basic) · Government ID · PCI
WA AG + MT AG + DE AG +4
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)

284,974

Sum of filed state slices

21,717· 7.6% of stated

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

US284,974
WA7,194
IN6,292
SC3,846
MA2,142
MT1,971
ME272

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

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 25, 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

23 days

Cadence

~1 / 2.6d

vs. multi-state median

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