People search Xsolis data breach timeline because regulated data and trust are existential—one incident triggers class actions and regulator exams. BreachHistory indexes 1 Xsolis-linked incident (1 company-confirmed), with headline counts up to 1.4M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Xsolis breach history matters
Xsolis operates in Healthcare (United States). Across indexed rows, recurring themes include credential theft and social engineering. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — targeted phishing attack; 1,396,519 patients across provider clients (HHS filing)
Verified breach. Franklin, Tennessee healthcare utilization and case-management vendor Xsolis, Inc. disclosed a targeted phishing incident discovered January 22, 2026 after unauthorized activity on its network. Xsolis interrupted access, reported no known misuse, and is offering 12 months of Kroll identity monitoring via xsolisdataincident.com. On June 5, 2026 Xsolis issued a press release, posted its incident site, and reported the breach to HHS as affecting 1,396,519 patients across its provider clients; California AG posted an e Exposed categories include Names, addresses, dates of birth, health insurance information, Social Security numbers, and medical treatment information (varies by individual); downstream clients include Roches. BreachHistory cites approximately 1.4M+ affected records in this row. See the xsolis-phishing 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Credential theft and social engineering — appears across multiple Xsolis catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Watch for medical-ID theft and billing fraud after health-data incidents.
- Step 5: Bookmark the Xsolis company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/xsolis · Latest: xsolis-phishing2026.
Sources: BreachHistory catalog (1 row for Xsolis), company and regulator disclosures cited in individual breach records.