DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed4 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblackbytehigh sensitivity
Merged incident · 4 filings

TOWNE MORTGAGE COMPANY — June 2025 breach

Clustered 4 filings across 4 jurisdictions · filing window Jul 30, 2025 → Feb 6, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

3

Affected · reported

474

First → last filing

Jul 30, 2025 → Feb 6, 2026

Merge confidence

100%

incident inc_d4595ff3ee794a5f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings and 1 unverified claim. The filing describes unauthorized access. Intrusion Jun 7, 2025, discovered Oct 14, 2025 — the first regulatory filing landed 30 days later. 474 individuals reported across the linked filings. Data reported: Government ID, Financial account, and Identity (basic). Notifications rolled out on a 190-day schedule across 3 filings beginning Jul 30, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
30days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
105days 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
190days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >90dDate basis✓ Clock withheld · confirmation dateFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 7, 2025breach begins
Oct 14, 2025discovered
notification delay · 30 days
Nov 13, 2025first filing
Feb 6, 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. JUL 30Leak siteblackbyte postfirst filing · attacker claim · unverifiedday 0
  2. NOV 13MA AGMA AG notice474 MA residents+106d
  3. NOV 13NE AGNE AG noticeno count stated+106d
  4. FEB 6CA AGCA AG noticemost recent · no count stated+191d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 7, 2025
NE AG
Discovered
Oct 14, 2025· 129d undetected
NE AG + CA AG
Data types
Financial account · Identity (basic) · Government ID
MA AG + CA AG + NE AG
Attack vector
Unauthorized Access
NE AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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

190 days

Cadence

~1 / 63.3d

vs. multi-state median

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