PLAZA HOME MORTGAGE, INC. — February 2026 breach
Clustered 13 records across 11 jurisdictions: 11 filings, 1 press report and 1 leak-site claim · filing window May 29, 2026 → Jun 17, 2026 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_66a78dde84324fa5 · merged by deterministic · confidence 100%
Litigation Timing
SupplementalDiscovered → first regulatory filing
Range of discovered_at dates across filings
Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Sensitive data
authenticationidentity_governmentIncident timeline
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
- FEB 27Leak sitesilentransomgroup postfirst record · attacker claim · unverifiedday 0
- MAY 29NE AGNE AG noticefiling day not on record · no count statedoperator-confirmed—
- MAY 29IN AGIN AG noticestates nationwide total 137,976operator-confirmed+90d
- JUN 1IL AGIL AG noticefiling day not on record · no count statedauto-linked—
- JUN 5WA AGWA AG notice9,598 WA residents+97d
- JUN 5CA AGCA AG noticeno count statedoperator-confirmed+97d
- JUN 5OR AGOR AG noticestates nationwide total 137,976operator-confirmed+97d
- JUN 5ME AGME AG noticestates nationwide total 137,976+97d
- JUN 8MT AGMT AG notice227 MT residentsauto-linked+100d
- JUN 9TX AGTX AG noticestates nationwide total 137,976operator-confirmed+101d
- JUN 11NH AGNH AG notice1,090 NH residentsoperator-confirmed+103d
- JUN 17MA AGMA AG noticemost recent · 4,033 MA residentsauto-linked+109d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Feb 17, 2026 NE AG
- Discovered
- Feb 17, 2026NE AG + WA AG + MT AG +1Mar 3, 2026IL AG + OR AG + ME AG +1filings disagree on discovery
- Data types
- Authentication · Credentials · Financial · Financial account · Identity (basic) · Government ID · PII NE AG + WA AG + CA AG +6
- Attack vector
- Unauthorized Access NE 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)
137,976
Sum of filed state slices
29,803· 21.6% of stated
78% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
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
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Aug 22, 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
19 days
Cadence
~1 / 2.4d
vs. multi-state median
3.2× 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.