Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Xsolis » XSOMCB1788870784

Incident Score: Analysis & Impact (XSOMCB1788870784)

The details regarding individual company incidents & reports gives you full view from every side.

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-219
Company Score Before Incident762 / 1000
Company Score After Incident543 / 1000
INCIDENT NUMBERXSOMCB1788870784
Type of Cyber IncidentRansomware
ATTACK VECTORPhishing, Extortion
DATA EXPOSEDProtected Health Information (PHI), Social...
INCIDENT DATE31/12/2020
STATUSpublished

Key Highlights From The Incident Analysis

  • Timeline of Xsolis's Ransomware and lateral movement inside company's environment.
  • Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
  • How Rankiteo’s incident engine converts technical details into a normalized incident score.
  • How this cyber incident impacts Xsolis Rankiteo cyber scoring and cyber rating.
  • Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.

Full Incident Analysis Transcript

In this Rankiteo incident briefing, we review the Xsolis breach identified under incident ID XSOMCB1788870784.

The analysis begins with a detailed overview of Xsolis's information like the linkedin page: https://www.linkedin.com/company/xsolis, the number of followers: 7739, the industry type: Hospitals and Health Care and the number of employees: 243 employees

After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 762 and after the incident was 543 with a difference of -219 which is could be a good indicator of the severity and impact of the incident.

In the next step of the video, we will analyze in more details the incident and the impact it had on Xsolis and their customers.

Xsolis recently reported "Healthcare Data Breaches Surge as Third-Party Vendors Become Prime Targets", a noteworthy cybersecurity incident.

In the first half of 2026, third-party vendors known as business associates were involved in 43% of all large healthcare data breaches reported to U.S.

The disruption is felt across the environment, and exposing Protected Health Information (PHI), Social Security numbers, medical histories, insurance details, with nearly ['1.4 million (Xsolis)', '1.25 million (MCBS)', '10,023 (Spencer Gifts LLC)'] records at risk, plus an estimated financial loss of $450,000 (HIPAA fine for Spencer Gifts LLC).

Formal response steps have not been shared publicly yet.

The case underscores how teams are taking away lessons such as Vendor-side incidents now dominate healthcare data exposure, and covered entities remain liable for vendor breaches under HIPAA. Continuous vendor security assessments are critical, not just one-time compliance checks, and recommending next steps like Employers with group health plans must ensure HIPAA compliance, conduct risk analyses, and implement security policies. Enhanced monitoring and network segmentation are recommended for third-party vendors.

Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.

The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.

MITRE ATT&CK® Correlation Analysis

Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Phishing (T1566) with high confidence (90%), supported by evidence indicating xsolis suffered a phishing attack in January. Under the Persistence tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (80%), supported by evidence indicating attackers granted four days of network access. Under the Credential Access tactic, the analysis identified Unsecured Credentials (T1552) with moderate to high confidence (70%), supported by evidence indicating lack of risk analysis or HIPAA-compliant policies. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating social Security numbers, medical histories, insurance details compromised and Data from Information Repositories (T1213) with moderate to high confidence (80%), supported by evidence indicating pHI of 4.5 million individuals exposed. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), supported by evidence indicating pEAR extortion group stole files and Transfer Data to Cloud Account (T1537) with moderate confidence (60%), supported by evidence indicating data breach impacting 2.6 million people. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with moderate confidence (50%), supported by evidence indicating type such as Ransomware and Defacement (T1491) with lower confidence (40%), supported by evidence indicating extortion group involvement. Under the Defense Evasion tactic, the analysis identified Disabling Security Tools (T1089) with moderate confidence (60%), supported by evidence indicating lack of HIPAA-compliant policies and Impair Defenses: Disable or Modify Tools (T1562.001) with moderate confidence (50%), supported by evidence indicating no risk analysis in place. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Phishing (90%)
Persistence
Valid Accounts (80%)
Credential Access
Unsecured Credentials (70%)
Collection
Data from Local System (90%)
Data from Information Repositories (80%)
Exfiltration
Exfiltration Over C2 Channel (80%)
Transfer Data to Cloud Account (60%)
Impact
Data Encrypted for Impact (50%)
Defacement (40%)
Defense Evasion
Disabling Security Tools (60%)
Impair Defenses: Disable or Modify Tools (50%)