CTS Journey Holdings, LLC — December 2025 breach
Clustered 8 filings across 8 jurisdictions · filing window Aug 1, 2026 → Aug 10, 2026. View entity profile → Other incidents for this victim →
incident inc_974e881bf23a4251 · merged by deterministic · confidence 100%
What the filings say
TX AGCTS Journey Holdings, LLC, a Delaware limited liability company (DBA Corporate Travel Service) based in Northfield, Michigan, a other entity reported a data breach to the Texas Attorney General. The breach was discovered on 2026-07-02 and reported on 2026-08-04. 564 Texas residents were affected. 37,682 individuals affected in total. Types of information involved: Name of individual;Social Security Number Information;Driver’s License number;Government-issued ID number (e.g. passport, state ID card);Financial Information (e.g. account number, credit or debit card number);Medical Information. Consumers were notified via U.S. Mail.
AI-generated summary of the linked filing — not the filing's own words, and not independently verified.
Litigation Timing
SupplementalDiscovered → first regulatory filing
Range of discovered_at dates across filings
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.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- AUG 1MA AGMA AG noticefirst filing · no count statedauto-linkedday 0
- AUG 3NE AGNE AG noticeno count statedauto-linked+2d
- AUG 3WA AGWA AG notice2,226 WA residentsauto-linked+2d
- AUG 3CA AGCA AG noticeno count stated+2d
- AUG 3OR AGOR AG noticestates nationwide total 37,682auto-linked+2d
- AUG 4VT AGVT AG notice37 VT residentsauto-linked+3d
- AUG 4TX AGTX AG noticestates nationwide total 37,682auto-linked+3d
- AUG 10NH AGNH AG noticemost recent · 8 NH residentsauto-linked+9d
- 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
- Identity (basic) MA AG + NE AG + WA AG +4
- Attack vector
- Unauthorized Access MA AG
- Response
- Worked to contain the threat and secure its internal environment · Commenced a prompt and thorough investigation into the incident · Worked very closely with external cybersecurity professionals NH 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
2,835· 7.5% of stated
92% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
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
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
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
9 days
Cadence
~1 / 1.3d
vs. multi-state median
1.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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
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.