DisclosureLens
Leak SitePressState AGConfirmed12 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedsilentransomgrouphigh sensitivity
Merged incident · 12 filings

PLAZA HOME MORTGAGE, INC. — February 2026 breach

Clustered 12 filings across 11 jurisdictions · filing window Feb 27, 2026 Jun 17, 2026. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

12 filings

States

10

Affected · reported

137,976

First → last filing

Feb 27, 2026 Jun 17, 2026

Merge confidence

100%

incident inc_66a78dde84324fa5 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings, 1 press report and 1 unverified claim. Intrusion Feb 17, 2026, discovered Feb 17, 2026 — the first regulatory filing landed 101 days later (flagged late). 137,976 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 120-day schedule across 10 filings beginning Feb 27, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
101days

Discovered → first regulatory filing

Discovery variance
14days

Range of discovered_at dates across filings

Leak precedence
90days before filing

Days between the first leak-site claim and the first regulatory filing. 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.

Filing span
120days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksWashington WA AG >90dOregon OR AG >45dMaine ME AG >90d · 94dTexas TX AG >30dMassachusetts MA AG >90dLeak gap Leak >90dFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Feb 17, 2026breach begins
Feb 17, 2026discovered · members disagree
notification delay · 101 days
May 29, 2026first filing
Jun 17, 2026most 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 27Leak sitesilentransomgroup postfirst filing · attacker claim · unverifiedday 0
  2. MAY 29NE AGNE AG noticeno count stated+90d
  3. MAY 29IN AGIN AG noticestates nationwide total 137,976+90d
  4. JUN 1IL AGIL AG noticeno count stated+93d
  5. JUN 5WA AGWA AG notice9,598 WA residents+97d
  6. JUN 5CA AGCA AG noticeno count stated+97d
  7. JUN 5OR AGOR AG noticestates nationwide total 137,976+97d
  8. JUN 5ME AGME AG noticestates nationwide total 137,976+97d
  9. JUN 9TX AGTX AG noticestates nationwide total 137,976+101d
  10. JUN 11NH AGNH AG notice1,090 NH residents+103d
  11. JUN 17MA AGMA AG noticemost recent · 4,033 MA residents+109d
  12. 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 + MA AGMar 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 +5
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,576· 21.4% of stated

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

US137,976
TX12,610
WA9,598
MA4,033
IN1,490
NH1,090
ME755

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

Unlocks: incident narrative, operational impact. Still no compliance clock.

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

120 days

Cadence

~1 / 10.9d

vs. multi-state median

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