Confirmed breach. Intrusion Feb 17, 2026, discovered Feb 17, 2026 — the first regulatory filing landed 101 days later. 137,976 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksLeak gap⏱ Leak >90dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
137,976
Data types
—
Jurisdictions
2
IN NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 17, 2026
When the intrusion reportedly occurred, per the linked filings
Plaza Home Mortgage Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2026-02-17 and was reported on 2026-05-29. 1,490 Indiana residents were affected. 137,976 individuals affected in total.
Affected (this filing): 137,976
Leak >90d
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 95%
Plaza Home Mortgage, Inc. reported a security incident to the New Hampshire Attorney General involving unauthorized access to an employee's computer on or around February 17, 2026. The breach potentially affected 1,090 New Hampshire residents, exposing personal information including names, addresses, Social Security numbers, birth dates, driver's license numbers, and mortgage loan application data. Notices were sent to affected individuals on May 29, 2026, offering 12 months of credit monitoring and identity theft protection.
Affected (this filing): 1,090
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.