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

HOME POINT FINANCIAL CORPORATION — November 2016 breach

Clustered 9 filings across 7 jurisdictions · filing window Jun 20, 2017 → Sep 12, 2017. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

32,642

First → last filing

Jun 20, 2017 → Sep 12, 2017

Merge confidence

100%

incident inc_1bb563b2b89c489f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe a phishing attack. Intrusion Nov 1, 2016–Mar 30, 2017, discovered Mar 30, 2017 — the first regulatory filing landed 82 days later (flagged late). 32,642 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 84-day schedule across 9 filings beginning Jun 20, 2017. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
82days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
84days

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 >45dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentialsidentity_government

Incident timeline

Nov 1, 2016breach begins
Mar 30, 2017discovered
notification delay · 82 days
Jun 20, 2017first filing
Sep 12, 2017most 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. JUN 20MT AGMT AG noticefirst filing · 45 MT residentsday 0
  2. JUN 20OR AGOR AG noticestates nationwide total 32,642day 0
  3. JUN 20CA AGCA AG noticeno count statedday 0
  4. JUN 20MA AGMA AG notice6,020 MA residentsday 0
  5. JUN 20WA AGWA AG notice815 WA residentsday 0
  6. JUN 20NH AGNH AG notice280 NH residentsday 0
  7. SEP 8CA AGCA AG noticeno count stated+80d
  8. SEP 8NH AGNH AG notice1,047 NH residents+80d
  9. SEP 12SC AGSC AG noticemost recent · 1,241 SC residents+84d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 1, 2016
MT AG
Discovered
Mar 30, 2017· 149d undetected
MT AG + OR AG + WA AG +2
Data types
Authentication · Financial account · Financial credentials · Identity (basic) · Government ID · PCI
MT AG + WA AG + NH AG +2
Attack vector
Phishing
MT 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)

32,642

Sum of filed state slices

9,168· 28.1% of stated

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

US32,642
MA6,020
SC1,241
NH1,047
WA815
MT45

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

84 days

Cadence

~1 / 10.5d

vs. multi-state median

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