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

CTS Journey Holdings, LLC — December 2025 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

37,682

First → last dated filing

Aug 3, 2026 → Aug 10, 2026

Merge confidence

100%

incident inc_974e881bf23a4251 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Dec 3, 2025–Dec 11, 2025, discovered Dec 11, 2025. 37,682 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 7-day schedule across 7 dated filings beginning Aug 3, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
203days

Range of discovered_at dates across filings

Filing span
7days

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 >45dWashington⏱ WA AG >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 3, 2025breach begins
Dec 11, 2025discovered · members disagree
Aug 3, 2026first dated filing
Aug 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. AUG 1MA AGMA AG noticefiling day not on record · no count stated—
  2. AUG 3NE AGNE AG noticefiling day not on record · no count stated—
  3. AUG 3WA AGWA AG noticefirst filing · 2,226 WA residentsday 0
  4. AUG 3CA AGCA AG noticeno count statedday 0
  5. AUG 3OR AGOR AG noticestates nationwide total 37,682day 0
  6. AUG 3IN AGIN AG noticestates nationwide total 37,682day 0
  7. AUG 4TX AGTX AG noticestates nationwide total 37,682+1d
  8. AUG 4VT AGVT AG notice37 VT residents+1d
  9. AUG 10NH AGNH AG noticemost recent · 8 NH residents+7d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 3, 2025 – Dec 11, 2025
NE AG
Discovered
Dec 11, 2025OR AGJul 2, 2026MA AG + NE AG + WA AG +3filings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
MA AG + NE AG + WA AG +4
Attack vector
Unauthorized Access
MA 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)

37,682

Sum of filed state slices

3,039· 8.1% of stated

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

US37,682
WA2,226
TX564
IN204
VT37
NH8

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

7 days

Cadence

~1 / 1.2d

vs. multi-state median

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