Incident Score: Analysis & Impact (BLUCONPLARYU1782822739)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of Ryuk Labs'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 Ryuk Labs 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 Ryuk Labs breach identified under incident ID BLUCONPLARYU1782822739.
The analysis begins with a detailed overview of Ryuk Labs's information like the linkedin page: https://www.linkedin.com/company/ryuklabs, the number of followers: 112, the industry type: Software Development and the number of employees: 11 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 754 and after the incident was 639 with a difference of -115 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 Ryuk Labs and their customers.
A newly reported cybersecurity incident, "SystemBC Malware: A Persistent Proxy and RAT Tool in Ransomware Attacks", has drawn attention.
SystemBC, also known as Coroxy, is a long-standing Windows malware family first detected in exploit kits around 2018–2019.
The disruption is felt across the environment, affecting Windows.
Formal response steps have not been shared publicly yet.
The case underscores how teams are taking away lessons such as SystemBC is rarely the end goal but a force multiplier, enabling stealthy lateral movement and tool reuse across access-as-a-service chains. Its presence often signals broader compromise, including credential theft and further malware deployment, and recommending next steps like Monitor unusual outbound SOCKS/Tor connections, suspicious scheduled tasks, and in-memory execution techniques. Implement network segmentation and egress filtering to limit impact.
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 Drive-by Compromise (T1189) with moderate to high confidence (70%), supported by evidence indicating first detected in exploit kits around 2018–2019 and Phishing: Spearphishing Attachment (T1566.001) with moderate confidence (60%), supported by evidence indicating frequently deployed alongside loaders like Buer, QBot, and Emotet. Under the Execution tactic, the analysis identified Command and Scripting Interpreter: PowerShell (T1059.001) with moderate to high confidence (80%), supported by evidence indicating supports...PowerShell many executed in memory to avoid disk writes, Command and Scripting Interpreter: Windows Command Shell (T1059.003) with moderate to high confidence (80%), supported by evidence indicating supports...CMD...many executed in memory to avoid disk writes, Command and Scripting Interpreter: Visual Basic (T1059.005) with moderate to high confidence (70%), supported by evidence indicating supports...VBS...many executed in memory to avoid disk writes, and Scheduled Task/Job: Scheduled Task (T1053.005) with high confidence (90%), supported by evidence indicating establishes persistence via...scheduled task. Under the Persistence tactic, the analysis identified Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder (T1547.001) with high confidence (90%), supported by evidence indicating establishes persistence via a registry Run key and Scheduled Task/Job: Scheduled Task (T1053.005) with high confidence (90%), supported by evidence indicating establishes persistence via...scheduled task. Under the Defense Evasion tactic, the analysis identified Masquerading: Match Legitimate Name or Location (T1036.005) with moderate to high confidence (80%), supported by evidence indicating copies itself into a randomly named file under %ProgramData%, Process Injection (T1055) with moderate to high confidence (80%), supported by evidence indicating injecting them into processes or executing them from disk, Virtualization/Sandbox Evasion: System Checks (T1497.001) with moderate to high confidence (70%), supported by evidence indicating skipping installation if security software like Emsisoft’s a2guard.exe is detected, and Obfuscated Files or Information (T1027) with moderate to high confidence (80%), supported by evidence indicating rC4-encrypted host/user data for C2 communication. Under the Command and Control tactic, the analysis identified Proxy: External Proxy (T1090.002) with high confidence (90%), supported by evidence indicating sOCKS5 proxy capability...route C2 and exfiltration traffic through compromised hosts, Application Layer Protocol: Web Protocols (T1071.001) with moderate to high confidence (80%), supported by evidence indicating tor for anonymity, blending malicious traffic with legitimate enterprise flows, and Encrypted Channel: Symmetric Cryptography (T1573.001) with moderate to high confidence (80%), supported by evidence indicating rC4-encrypted host/user data for C2 communication. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating route C2 and exfiltration traffic through compromised hosts and Exfiltration Over Alternative Protocol: Exfiltration Over Unencrypted/Obfuscated Non-C2 Protocol (T1048.003) with moderate to high confidence (70%), supported by evidence indicating tor for anonymity, blending malicious traffic with legitimate enterprise flows. Under the Lateral Movement tactic, the analysis identified Remote Services: Remote Desktop Protocol (T1021.001) with moderate confidence (60%), supported by evidence indicating remote-access trojan (RAT)...enabling stealthy lateral movement and Proxy: External Proxy (T1090.002) with moderate to high confidence (70%), supported by evidence indicating sOCKS5 proxy capability...enabling stealthy lateral movement. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with high confidence (90%), supported by evidence indicating favored component in ransomware operations, including Ryuk, Conti, Egregor, BlackBasta, Play, and Rhysida. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.