Healthcare AI Vendor Breach Highlights Ongoing Third-Party Security Risks

Image shows a warning sign with an exclamation point in the middle. The image also has the wording "third party risk" that refers to using third-party vendors as business associates.

 

Table of Contents

Xsolis AI Breach Affects 1.4 Million Patients: Lessons in Healthcare Vendor Cybersecurity

A recent data breach involving healthcare AI technology company Xsolis serves as another reminder that cybersecurity risks often extend beyond an organization’s network. 

According to Xsolis, the attack occurred on January 20, 2026, and was discovered two days later. The company says an unauthorized actor accessed part of its environment through a targeted phishing attack and obtained files containing patient information.  

On June 5, Xsolis notified the U.S. Department of Health and Human Services (HHS) that 1.4 million individuals were affected by the breach, a number the agency posted June 22, along with the impacted health systems. These include Mayo Clinic, UW Medicine, Legacy Health, Carle Health, Rochester Regional Health, VHC Health, and Augusta Health. 

While Xsolis uses AI and predictive analytics on its platform, the breach does not appear to involve a compromise of AI technology. Instead, it highlights a more common and persistent cybersecurity challenge: third-party vendor risk. 

The Growing Impact of Third-Party Breaches 

Healthcare organizations increasingly rely on external vendors to support operations ranging from electronic health records and billing to care coordination, analytics, and artificial intelligence solutions. Xsolis supports utilization management and care coordination for hundreds of healthcare organizations nationwide. 

As a result, a security incident affecting a single vendor can quickly impact multiple healthcare organizations and hundreds of thousands, or even millions, of patients. 

This incident reflects a growing trend of cyberattacks targeting healthcare vendors rather than healthcare providers directly. High-profile examples include the Change Healthcare ransomware attack, which disrupted claims processing and other critical services nationwide, as well as breaches involving cloud service providers, business associates, and technology partners that store or process healthcare data.

Phishing Remains One of the Biggest Threats 

Despite advances in cybersecurity technology, phishing remains one of the most successful attack methods used by cybercriminals. Attackers continue to exploit human behavior through fraudulent emails, links, and attachments that steal credentials or grant unauthorized access to systems. 

Read more about two other high-severity phishing threats against Microsoft users 

 

For healthcare, the Xsolis breach serves as an important reminder that cybersecurity is not solely a technical issue. Workforce awareness and training remain critical components of a comprehensive security program.  

Both the HIPAA Privacy and Security Rules have specific requirements regarding workforce training, security reminders, and periodic updates. Additionally, proposed updates to the HIPAA Security Rule would strengthen existing workforce training requirements by placing greater emphasis on ongoing cybersecurity education and accountability.

Organizations should regularly educate employees on: 

  • Recognizing phishing and social engineering attempts 
  • Verifying suspicious requests 
  • Reporting potential security incidents promptly 
  • Following established security policies and procedures 

 

Evaluating Vendor Risk in the Age of Healthcare AI 

As more AI-powered tools are adopted in healthcare, vendor risk assessment is increasingly important. Whether a vendor provides artificial intelligence, analytics, cloud services, or traditional software solutions, organizations should understand:

  • What data the vendor can access 
  • How the data is protected 
  • Where the data is stored 
  • Whether subcontractors have access to the data 
  • How security incidents are detected and reported 
  • What safeguards are in place to prevent unauthorized access

 

While the Xsolis breach should not be viewed as an AI failure, it is a reminder that healthcare organizations remain responsible for protecting patient information across their entire vendor ecosystem. It is imperative to strengthen vendor oversight, maintain robust workforce training, and regularly assess the security controls of any company entrusted with patient data. 

Evaluate Vendor Risk

Vendor risk assessments help ensure third parties that handle sensitive information maintain appropriate security and compliance safeguards. PrivaPlan’s experts can help you assess vendor risks and strengthen your organization’s compliance efforts. 

Vendor Cybersecurity Risk and HIPAA

Yes. Any vendor that creates, receives, maintains, or transmits PHI on your behalf, including AI platforms like Xsolis, qualifies as a business associate under HIPAA. A signed BAA is the contract that defines how that vendor protects your patients’ data and what happens if something goes wrong.

Both. Since the 2013 Omnibus Rule, business associates are directly liable for HIPAA violations, not just the covered entities that hire them. That said, liability for the vendor doesn’t remove the covered entities’ responsibility for vendor oversight. PrivaPlan recommends annual reviews of BAAs and performing regular security risk assessments (SRA) to ensure your HIPAA compliance efforts are in good standing.

A thorough vendor risk assessment, conducted before the partnership begins and revisited throughout it, turns potential blind spots into documented, defensible safeguards. Before any vendor touches patient data, your organization should confirm what they can access, where it’s stored, whether subcontractors are involved, and how incidents get reported. That groundwork is what lets you trust a vendor with PHI in the first place, and what can protect your organization if something ever goes wrong.

The Xsolis breach started with a single successful phishing email, not a technology failure. That’s true industry-wide: most healthcare breaches trace back to someone on staff clicking a link they shouldn’t have, whether that staff sits at the covered entity or at a vendor. Training your own team to recognize and report phishing attempts is one of the strongest, lowest-cost defenses available, regardless of how well your vendors are vetted. A well-trained workforce closes the gap that no contract or BAA can close on its own.

You can’t outsource responsibility for patient data, even when you outsource the technology. The penalty for a missing or non-compliant BAA alone can reach $1.9 million per violationper year, even without a breach. That’s why an annual security risk assessments (SRA), which are a HIPAA requirement, should always include a review of every vendor with access to PHI. Organizations that build this review into their ongoing practice maintain better vendor relationships and turn that diligence into a stronger position in the healthcare market. 

Access PrivaPlan Toolkit

Access CMA-PrivaPlan Toolkit

Stay Ahead of Privacy & Security Compliance

Sign Up for Our Newsletter!

Don’t miss the latest updates, tips, and best practices in privacy and security compliance! Join our email newsletter for:

  • Exclusive Insights: Gain access to vital news and expert insights from PrivaPlan experts.
  • Practical Tips: Learn actionable strategies to protect data privacy & enforce data security.

Sign up now and elevate your compliance game!

A Compliance First Guide focused on AI & the HIPAA Security Rule

Ensuring HIPAA Compliance in Generative AI Systems

Our new practical guide offers actionable strategies for establishing an AI system while focusing on the HIPAA Security Rule framework. It's built to help you:

Learn about Compliance!

Subscribe now for up-to-date information about privacy & security compliance! You’ll receive emails regarding news about compliance & alerts for new blog posts.