Incident Score: Analysis & Impact (S-R1765994181)
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 S-RM'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 S-RM 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 S-RM breach identified under incident ID S-R1765994181.
The analysis begins with a detailed overview of S-RM's information like the linkedin page: https://www.linkedin.com/company/s-rm, the number of followers: 49118, the industry type: Security and Investigations and the number of employees: 375 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 668 and after the incident was 521 with a difference of -147 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 S-RM and their customers.
On 05 December 2024, a cybersecurity incident called "Weaxor Ransomware Attack via React2Shell Vulnerability" came to light.
A ransomware gang exploited the critical React2Shell vulnerability (CVE-2025-55182) to gain initial access to corporate networks and deployed the Weaxor ransomware strain within less than a minute.
The disruption is felt across the environment, affecting Public-facing servers, vulnerable endpoints.
Formal response steps have not been shared publicly yet.
The case underscores how Completed (by S-RM), teams are taking away lessons such as Patching alone is insufficient; monitoring for unusual process creation (e.g., cmd.exe/powershell.exe from node.exe) and disabled security solutions is critical. React2Shell is actively exploited by multiple threat actors, and recommending next steps like Review Windows event logs and EDR telemetry for evidence of React2Shell exploitation, Investigate unusual outbound connections, disabled security solutions, log clearing, and resource spikes and Monitor for process spawning of cmd.exe or powershell.exe from node.exe.
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 high confidence (95%), with evidence including initial access via React2Shell vulnerability (CVE-2025-55182), and insecure deserialization issue in React Server Components. Under the Execution tactic, the analysis identified Command and Scripting Interpreter: PowerShell (T1059.001) with high confidence (90%), supported by evidence indicating obfuscated PowerShell command deploying a Cobalt Strike beacon and Exploitation for Client Execution (T1203) with moderate to high confidence (85%), supported by evidence indicating react2Shell vulnerability (CVE-2025-55182) allows remote code execution. Under the Persistence tactic, the analysis identified Scheduled Task/Job: Scheduled Task (T1053.005) with moderate to high confidence (70%), supported by evidence indicating cobalt Strike beacon for command-and-control (C2). Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1562.001) with high confidence (95%), supported by evidence indicating disabled Windows Defender’s real-time protection, Indicator Removal: Clear Windows Event Logs (T1070.001) with high confidence (90%), supported by evidence indicating cleared event logs to hinder recovery and forensic analysis, and Obfuscated Files or Information (T1027) with moderate to high confidence (85%), supported by evidence indicating obfuscated PowerShell command. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with high confidence (95%), with evidence including encrypted files received the .WEAX extension, and ransom notes (RECOVERY INFORMATION.txt) left in directories and Inhibit System Recovery (T1490) with high confidence (90%), supported by evidence indicating wiped volume shadow copies to hinder recovery. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- S-RM Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/s-rm/incident/S-R1765994181
- S-RM CyberSecurity Rating page: https://www.rankiteo.com/company/s-rm
- S-RM Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/s-r1765994181-ransomware-december-2025/
- S-RM CyberSecurity Score History: https://www.rankiteo.com/company/s-rm/history
- S-RM CyberSecurity Incident Source: https://www.bleepingcomputer.com/news/security/critical-react2shell-flaw-exploited-in-ransomware-attacks/
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf