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

Incident Score: Analysis & Impact (SUN1781814778)

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

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-101
Company Score Before Incident752 / 1000
Company Score After Incident651 / 1000
INCIDENT NUMBERSUN1781814778
Type of Cyber IncidentRansomware
ATTACK VECTORNetwork infiltration
DATA EXPOSED700 GB
INCIDENT DATE30/03/2026
STATUSOngoing

Key Highlights From The Incident Analysis

  • Timeline of SunSource'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 SunSource 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 SunSource breach identified under incident ID SUN1781814778.

The analysis begins with a detailed overview of SunSource's information like the linkedin page: https://www.linkedin.com/company/sunsource, the number of followers: 21764, the industry type: Industrial Machinery Manufacturing and the number of employees: 2050 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 752 and after the incident was 651 with a difference of -101 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 SunSource and their customers.

On 30 April 2026, SunSource Borrower LLC disclosed Data Breach, Ransomware issues under the banner "SunSource Borrower LLC Data Breach".

SunSource Borrower LLC, a North American distributor of fluid power and motion control technologies, confirmed a data breach after an unauthorized third party infiltrated a portion of its network, accessing files containing highly sensitive personal and health information.

The disruption is felt across the environment, and exposing 700 GB.

In response, and stakeholders are being briefed through Notifications to affected individuals, dedicated call center.

The case underscores how Ongoing, with advisories going out to stakeholders covering Notification letters sent to affected individuals starting June 16, 2026.

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 Exploit Public-Facing Application (T1190) with moderate confidence (50%), supported by evidence indicating unauthorized third party infiltrated a portion of its network and Valid Accounts (T1078) with moderate confidence (60%), supported by evidence indicating network infiltration suggests possible compromised credentials. Under the Credential Access tactic, the analysis identified OS Credential Dumping (T1003) with moderate to high confidence (70%), supported by evidence indicating accessed files containing SSNs, financial details, and health records and Unsecured Credentials: Credentials In Files (T1552.001) with moderate confidence (60%), supported by evidence indicating highly sensitive information including financial account details. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating accessed files containing names, SSNs, government IDs, health records and Data from Network Shared Drive (T1039) with moderate to high confidence (80%), supported by evidence indicating 700 GB of data exfiltrated from network infiltration. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating payouts King exfiltrated 700 GB of data via Tor network and Exfiltration Over Web Service (T1567) with moderate to high confidence (70%), supported by evidence indicating data exfiltration claimed via Tor network by ransomware group. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with moderate confidence (50%), supported by evidence indicating incident type labeled as Ransomware and Defacement (T1491) with lower confidence (30%), supported by evidence indicating payouts King claimed responsibility via Tor network. Under the Command and Control tactic, the analysis identified Application Layer Protocol: Web Protocols (T1071.001) with moderate to high confidence (70%), supported by evidence indicating payouts King used Tor network for data exfiltration claim. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Exploit Public-Facing Application (50%)
Valid Accounts (60%)
Credential Access
OS Credential Dumping (70%)
Unsecured Credentials: Credentials In Files (60%)
Collection
Data from Local System (90%)
Data from Network Shared Drive (80%)
Exfiltration
Exfiltration Over C2 Channel (90%)
Exfiltration Over Web Service (70%)
Impact
Data Encrypted for Impact (50%)
Defacement (30%)
Command and Control
Application Layer Protocol: Web Protocols (70%)

Sources & References