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

Benworth Capital Partners — May 2025 breach

Clustered 10 filings across 8 jurisdictions · filing window Jul 23, 2025 → Nov 4, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

8

Affected · reported

275,000

First → last filing

Jul 23, 2025 → Nov 4, 2025

Merge confidence

100%

incident inc_c365f2daa6d44614 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe a third-party compromise. Intrusion May 16, 2025–Jun 23, 2025, discovered May 18, 2025 — the first regulatory filing landed 66 days later (flagged late). 275,000 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 104-day schedule across 10 filings beginning Jul 23, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
66days

Discovered → first regulatory filing

Discovery variance
36days

Range of discovered_at dates across filings

Filing span
104days

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 clocksOregon✗ OR AG >45dCalifornia✗ CA 60-day late · 116dTexas✗ TX AG >30dWashington⏱ WA AG >30dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 16, 2025breach begins
May 18, 2025discovered · members disagree
notification delay · 66 days
Jul 23, 2025first filing
Nov 4, 2025most 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 23WA AGWA AG noticefirst filing · 1,932 WA residentsday 0
  2. SEP 1IL AGIL AG noticeno count stated+40d
  3. SEP 16MA AGMA AG notice1,266 MA residents+55d
  4. SEP 16MT AGMT AG notice108 MT residents+55d
  5. SEP 16OR AGOR AG noticestates nationwide total 943+55d
  6. SEP 16NE AGNE AG noticeno count stated+55d
  7. SEP 16CA AGCA AG noticeno count stated+55d
  8. OCT 31CA AGCA AG noticeno count stated+100d
  9. NOV 4TX AGTX AG noticestates nationwide total 275,000+104d
  10. NOV 4OR AGOR AG noticemost recent · states nationwide total 943+104d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 18, 2025
WA AG
Discovered
May 18, 2025OR AGMay 23, 2025WA AG + MT AG + NE AG +1Jun 23, 2025IL AG + TX AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
WA AG + MT AG + NE AG +4
Attack vector
Third-Party / Supply Chain
WA 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)

275,000

Sum of filed state slices

26,201· 9.5% of stated

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

US275,000
TX22,895
WA1,932
MA1,266
MT108

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
Reviewed
operator-reviewed Jun 12, 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

104 days

Cadence

~1 / 11.6d

vs. multi-state median

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

Benworth Capital Partners data breach (2025) · DisclosureLens