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

Evolve Mortgage Services — September 2025 breach

Clustered 10 filings across 7 jurisdictions · filing window Oct 30, 2025 → Mar 25, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

6

Affected · reported

13,501

First → last filing

Oct 30, 2025 → Mar 25, 2026

Merge confidence

100%

incident inc_eb15817953fd4ace · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Sep 17, 2025–Sep 24, 2025, discovered Sep 24, 2025 — the first regulatory filing landed 75 days later (flagged late). 13,501 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 145-day schedule across 9 filings beginning Oct 30, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
75days

Discovered → first regulatory filing

Discovery variance
170days

Range of discovered_at dates across filings

Leak precedence
38days 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
145days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksCalifornia✗ CA 60-day late · 132dLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 17, 2025breach begins
Sep 24, 2025discovered · members disagree
notification delay · 75 days
Dec 8, 2025first filing
Mar 25, 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. OCT 30Leak siteinc_ransom postfirst filing · attacker claim · unverifiedday 0
  2. DEC 8SC AGSC AG notice175 SC residents+39d
  3. FEB 3NE AGNE AG noticeno count stated+96d
  4. FEB 3NE AGNE AG noticeno count stated+96d
  5. FEB 4CA AGCA AG noticeno count stated+97d
  6. FEB 4NH AGNH AG notice10 NH residents+97d
  7. FEB 4MA AGMA AG notice202 MA residents+97d
  8. MAR 9ME AGME AG noticestates nationwide total 4,309+130d
  9. MAR 20NH AGNH AG notice10 NH residents+141d
  10. MAR 25ME AGME AG noticemost recent · states nationwide total 13,501+146d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 17, 2025 – Sep 24, 2025
SC AG
Discovered
Sep 24, 2025SC AG + NE AG + CA AG +1Jan 23, 2026ME AGMar 13, 2026ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
SC AG + NE AG + CA AG +3
Attack vector
Unauthorized Access
SC 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)

13,501

Sum of filed state slices

412· 3.1% of stated

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

US13,501
MA202
SC175
ME25
NH10

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 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 Aug 14, 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

145 days

Cadence

~1 / 16.1d

vs. multi-state median

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