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

UNION HOME MORTGAGE CORP. — May 2025 breach

Clustered 10 filings across 9 jurisdictions · filing window Jul 25, 2025 → Jan 10, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

9

Affected · reported

425,538

First → last dated filing

Jul 25, 2025 → Jan 10, 2026

Merge confidence

100%

incident inc_3bbbd33384ae4366 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion May 27, 2025–Jun 29, 2025, discovered Jun 25, 2025 — the first regulatory filing landed 30 days later; 1 later filing was flagged late. 425,538 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 169-day schedule across 7 dated filings beginning Jul 25, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
30days

Discovered → first regulatory filing

Discovery variance
62days

Range of discovered_at dates across filings

Filing span
169days

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 clocksTexas✗ TX AG >30dWashington⏱ WA AG >30dMassachusetts✓ MA credit monitoring dueDate basis✓ Clock withheld · confirmation dateSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 27, 2025breach begins
Jun 25, 2025discovered · members disagree
notification delay · 30 days
Jul 25, 2025first dated filing
Jan 10, 2026most 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 about this breach

  1. JUL 25NE AGNE AG noticefiling day not on record · 3 NE residents—
  2. JUL 25MA AGMA AG noticefirst filing · 56 MA residentsday 0
  3. SEP 1IL AGIL AG noticefiling day not on record · no count stated—
  4. SEP 11NE AGNE AG noticefiling day not on record · 3 NE residents—
  5. SEP 11OR AGOR AG noticestates nationwide total 425,538+48d
  6. SEP 11WA AGWA AG notice1,650 WA residents+48d
  7. SEP 11MT AGMT AG notice208 MT residents+48d
  8. SEP 11SC AGSC AG notice7,272 SC residents+48d
  9. DEC 3TX AGTX AG noticestates nationwide total 425,538+131d
  10. JAN 10CA AGCA AG noticemost recent · no count stated+169d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 27, 2025 – Jun 29, 2025
OR AG
Discovered
Jun 25, 2025NE AG + IL AG + WA AG +3Aug 26, 2025OR AGfilings disagree on discovery
Data types
Financial · Financial account · Identity (basic) · Government ID · PII
NE AG + WA AG + MT 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)

425,538

Sum of filed state slices

33,349· 7.8% of stated

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

US425,538
TX24,160
SC7,272
WA1,650
MT208
MA56
NE3

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

169 days

Cadence

~1 / 28.2d

vs. multi-state median

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