Threat reportData BreachTL-2026-0922
Xsolis, Inc. Healthcare Technology Data Breach via Targeted Phishing (CVE-less; 1,396,519 individuals)
Xsolis, a healthcare technology business associate providing AI-powered utilization and case management software to 600+ hospitals and health plans, disclosed a data breach affecting 1,396,519 individuals after a targeted phishing attack against an employee on January 20, 2026 yielded unauthorized access to a limited portion of its environment.
Key facts
| Identifiers | TL-2026-0922 |
|---|---|
| Also known as | Xsolis Data Breach, Xsolis, Inc. Data Breach (2026) |
| Severity | HIGH |
| Affected products | Xsolis, Inc. Xsolis AI-powered utilization / case management platform; VHC Health Downstream covered entity (patients affected); Rochester Regional Health Downstream covered entity (patients affected) |
| Weaknesses (CWE) | CWE-1216, CWE-522, CWE-307, CWE-200 |
| MITRE ATT&CK techniques | T1056 Input Capture, T1078 Valid Accounts, T1083 File and Directory Discovery, T1087 Account Discovery, T1204 User Execution, T1213 Data from Information Repositories, T1530 Data from Cloud Storage, T1566 Phishing, T1567 Exfiltration Over Web Service, T1583 Acquire Infrastructure, T1598 Phishing for Information |
| Motivation | UNKNOWN |
| Target sectors | healthcare, health insurance, hospitals, healthcare technology |
| Target regions | North America, United States |
| Detection rules | 9 (1 shown free) |
| Sources | 8 cited sources |
Detection coverage
As of 2026-06-23, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-0922 across Splunk SPL, Microsoft KQL and Sigma, covering 19 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: Bulk PHI Repository Read with Outbound Web-Service Exfiltration — C2 / Exfiltration
Detects the collection-to-exfiltration stage (T1213 / T1530 data from repositories, T1083 file discovery, T1567 exfiltration over web service): a single account performs atypical bulk read of records containing SSN/DOB/medical-treatment fields, then a large outbound POST to a non-corporate web service follows. Correlates application/DB access volume with proxy egress to flag staged-and-uploaded PHI as in the Xsolis breach.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1213, T1530, T1083, T1567
- Data sources: application_phi_access_logs, proxy, cloud_app_events, edr_network
- Severity: high
- Confidence: medium
Splunk SPL
index=app sourcetype="phi:access" action=read
| eval user=lower(src_user)
| bin _time span=15m
| stats sum(records_returned) as records_read dc(record_id) as distinct_records values(fields_accessed) as fields by user _time
| where records_read > 500 AND (like(fields,"%ssn%") OR like(fields,"%dob%") OR like(fields,"%treatment%"))
| join type=inner user
[ search index=proxy sourcetype="proxy:web" cs_method=POST earliest=-30m
| eval user=lower(src_user)
| where sc_bytes > 1000000 AND NOT cidrmatch("10.0.0.0/8",dest_ip)
| stats sum(sc_bytes) as exfil_bytes values(url) as exfil_url by user ]
| eval exfil_mb=round(exfil_bytes/1024/1024,2)
| table _time user records_read distinct_records fields exfil_url exfil_mb
| sort - records_readMicrosoft KQL
let bulkRead = CloudAppEvents | where Timestamp > ago(24h) | where ActionType in ("FileAccessed","RecordExported","SearchQueryPerformed") | where RawEventData has_any ("ssn","dob","treatment","phi") | summarize recordsRead=count() by user=tolower(AccountId), bin(Timestamp, 15m) | where recordsRead > 500;
let exfil = DeviceNetworkEvents | where Timestamp > ago(24h) | where ActionType == "ConnectionSuccess" | where RemoteIPType == "Public" | summarize sentBytes=sum(tolong(coalesce(column_ifexists("SentBytes",0),0))), urls=make_set(RemoteUrl) by user=tolower(InitiatingProcessAccountUpn), bin(Timestamp, 15m) | where sentBytes > 1000000;
bulkRead | join kind=inner exfil on user | project Timestamp, user, recordsRead, sentBytes, urls | order by recordsRead descSigma
title: Bulk PHI Read and Outbound Web-Service Exfiltration (TL-2026-0922 Exfiltration)
id: a1f3c0e2-0922-4b11-9a01-5e7c1d8f0003
status: experimental
description: Detects a large outbound POST to a non-corporate web service following bulk access to PHI records, matching the Xsolis collection-and-exfiltration stage.
references:
- https://securityaffairs.com/194067/cyber-crime/xsolis-data-breach-impacts-1-4-million-people.html
author: Threadlinqs Team
date: 2026/06/23
tags:
- attack.collection
- attack.t1213
- attack.t1530
- attack.exfiltration
- attack.t1567
logsource:
category: proxy
detection:
selection:
cs-method: 'POST'
sc-bytes|gte: 1000000
filter_corp:
c-uri|contains:
- '.xsolis.com'
- 'sharepoint.com'
condition: selection and not filter_corp
fields:
- src_user
- c-uri
- sc-bytes
falsepositives:
- Legitimate large file uploads to sanctioned SaaS (backups, data syncs)
level: mediumKnown false positives:
- Authorized bulk data exports or reporting jobs run by analysts
- Sanctioned large uploads to approved SaaS/backup services
Tuning notes: Baseline normal per-user PHI read volumes and set the records_read threshold (default 500/15m) above the 95th percentile for each role. Allowlist sanctioned upload destinations by domain, and prioritize alerts where the same account triggered an anomalous-logon detection within the prior hour.
- Risky Sign-In from Unmanaged Device After Phishing — Exploitation · unlock with TL Creds
- Account/Directory Discovery and Repository Enumeration by Compromised User — Post-Exploitation · unlock with TL Creds
- Large Outbound Upload to Non-Corporate Web Service After Data Staging — C2 / Exfiltration · unlock with TL Creds
- Spearphishing Information-Gathering Email to Employee — Exploitation · unlock with TL Creds
- MFA Fatigue / Phishable-MFA Bypass with Successful Valid-Account Logon — Post-Exploitation · unlock with TL Creds
- Atypical Bulk Read of Sensitive PHI Records by Single Account — Collection · unlock with TL Creds
- Phishing Link Click Followed by Authentication for Same User — Exploitation · unlock with TL Creds
- Anomalous Valid-Account Logon from New Geo/Device — Post-Exploitation · unlock with TL Creds
Indicators of compromise
As of 2026-06-23, Threadlinqs Intelligence tracks 19 indicators of compromise for TL-2026-0922.
Technical analysis
Exposed protected health information (PHI) and PII included names, addresses, dates of birth, Social Security numbers, health insurance information, and medical treatment details.
Xsolis, Inc. is a Nashville-based healthcare technology firm and HIPAA business associate whose AI-powered platform supports case management, utilization management, and reimbursement/medical-necessity decisioning for more than 600 hospitals and health insurers. On January 20, 2026, a targeted phishing attack against an Xsolis employee compromised credentials and gave attackers unauthorized access to a 'limited portion' of the Xsolis environment. Xsolis identified the unauthorized activity on January 22, 2026, immediately contained the activity, terminated the unauthorized access, and launched an investigation with external cybersecurity experts and law enforcement.
The forensic investigation determined that protected health information and personally identifiable information was accessible during the intrusion window. Exposed data elements included full names, postal addresses, dates of birth, Social Security numbers, health insurance information, and medical treatment information. Because Xsolis operates as a business associate, the exposed records belong to patients of its covered-entity clients; confirmed downstream-affected organizations include VHC Health (Northern Virginia / Washington D.C. metro area) and Rochester Regional Health (New York). Xsolis reported the incident to the U.S. Department of Health and Human Services Office for Civil Rights (HHS OCR), whose breach portal lists 1,396,519 individuals affected.
Xsolis stated it found no evidence of unauthorized access after January 22, 2026 and no evidence that exposed data has been misused. As remediation, Xsolis reset passwords for all users and key accounts, increased system monitoring, rolled out updated security measures, accelerated employee security-awareness training, and strengthened credential-management mechanisms. Affected individuals are being offered 12 months of complimentary identity monitoring, credit monitoring, fraud consultation, and identity-theft restoration services through Kroll. Multiple plaintiff law firms (including Edelson Lechtzin LLP and Emery Reddy) announced investigations into potential class-action claims.
This incident is a credential-phishing-led supply-chain compromise of a healthcare vendor. No CVE, exploit/PoC, malware family, or named threat actor was disclosed. The defensive value is in phishing and identity/credential-abuse detection, business-associate/third-party risk monitoring, and HIPAA breach-response readiness rather than in patch-level vulnerability management.
MITRE ATT&CK techniques by tactic:
Credential Access
Initial Access
T1078 Valid Accounts; T1566 Phishing
Persistence
Defense Evasion
Discovery
T1083 File and Directory Discovery; T1087 Account Discovery
Execution
Collection
T1213 Data from Information Repositories; T1530 Data from Cloud Storage
Exfiltration
T1567 Exfiltration Over Web Service
Resource Development
Reconnaissance
Remediation
Immediate actions
- Reset passwords for all users and key accounts
- Terminate and contain unauthorized access; preserve forensic evidence
- Notify affected individuals and offer Kroll identity/credit monitoring (12 months)
- Report the breach to HHS OCR and law enforcement
Workarounds
- Apply conditional-access and impossible-travel policies to flag anomalous logins from compromised credentials
- Restrict and monitor access to PHI repositories on a least-privilege basis
Longer-term hardening
- Enforce phishing-resistant MFA (FIDO2/WebAuthn) on all employee and remote-access accounts
- Increase system monitoring and centralized logging across identity and email systems
- Accelerate and sustain employee security-awareness and phishing-simulation training
- Strengthen credential-management mechanisms (password hygiene, secrets vaulting, conditional access)
- Implement third-party / business-associate risk monitoring for downstream covered entities
Affected and fixed versions
- Xsolis, Inc. — Xsolis AI-powered utilization / case management platform
Vulnerable versions: N/A - data breach, not a software vulnerability - VHC Health — Downstream covered entity (patients affected)
Vulnerable versions: N/A - Rochester Regional Health — Downstream covered entity (patients affected)
Vulnerable versions: N/A
Timeline
- Targeted phishing attack against an Xsolis employee compromises credentials, granting attackers unauthorized access to a limited portion of the Xsolis environment.
- Xsolis launches an investigation with external cybersecurity experts and notifies law enforcement.
- Unauthorized access is terminated; no evidence of unauthorized access has been found since this date.
- Xsolis identifies the unauthorized activity in its environment and immediately contains it.
- Xsolis resets passwords for all users and key accounts, increases monitoring, accelerates employee security training, and strengthens credential-management mechanisms (period approximate, post-containment).
- Plaintiff law firms including Edelson Lechtzin LLP and Emery Reddy announce investigations into potential class-action claims.
- Xsolis begins notifying affected individuals and offers 12 months of Kroll identity/credit monitoring and identity-theft restoration.
- Xsolis publicly discloses the breach and reports 1,396,519 individuals affected to HHS OCR; media coverage (BleepingComputer, HIPAA Journal, TechRadar, SecurityAffairs) begins.
Sources cited
- Xsolis, Inc. Data Breach (Emery Reddy) emeryreddy.com · Blog · 2026-06-23
- Healthtech firm Xolis suffers data breach impacting 1.4 million people BleepingComputer · News · 2026-06-23
- Xsolis Data Breach Affects 1.4M Individuals hipaajournal.com · News · 2026-06-23
- US healthcare AI platform Xsolis confirms data breach that affects 1.4 million individuals techradar.com · News · 2026-06-23
- Xsolis Data Breach Impacts 1.4 Million People securityaffairs.com · News · 2026-06-23
- Xsolis breach exposes personal and health data of 1.4 million people scworld.com · News · 2026-06-23
- Xsolis Data Breach Hits 1.4 Million People As Healthcare Vendor Reports Patient Data Exposure nchstats.com · News · 2026-06-23
- Xsolis, Inc. Data Breach: Edelson Lechtzin LLP Launches Investigation Into Exposure of Personal Information prnewswire.com · News · 2026-06-23
Previous and next in data breach
- Dark Web Identity-Theft Ecosystem: $0.95 Fullz, STORM Infostealer-as-a-Service, and Scam-as-a-Service Marketplaces Previous report
- World Leaks Ransomware Group Breaches Tata Electronics — 630GB / 200,000+ Files Including Apple 'com.apple.factorydata' and Tesla Project Highland Design Data Next report
Drafted by the Threadlinqs research pipeline from 8 sources; published ; last updated —.