Incident Score: Analysis & Impact (RES1767463312)
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 Resecurity's Breach 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 Resecurity 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 Resecurity breach identified under incident ID RES1767463312.
The analysis begins with a detailed overview of Resecurity's information like the linkedin page: https://www.linkedin.com/company/resecurity, the number of followers: 89527, the industry type: Defense and Space Manufacturing and the number of employees: 99 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 395 and after the incident was 329 with a difference of -66 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 Resecurity and their customers.
Resecurity recently reported "ShinyHunters Breach of Resecurity", a noteworthy cybersecurity incident.
The hacking group ShinyHunters claimed responsibility for breaching Resecurity, a US-based cybersecurity company.
The disruption is felt across the environment, affecting Internal dashboards, user management panels, token databases, employee communication channels (Mattermost), and exposing Internal chats, client lists, threat intelligence reports, employee information (names, email addresses, authentication tokens), API keys, access tokens.
Formal response steps have not been shared publicly yet.
The case underscores how Unverified.
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 Valid Accounts (T1078) with moderate to high confidence (70%), with evidence including exposed credentials in leaked screenshots, and active employee profiles with authentication tokens, Exploit Public-Facing Application (T1190) with moderate confidence (50%), supported by evidence indicating attack vector listed as likely exploitation of vulnerabilities, and Phishing (T1566) with moderate confidence (60%), supported by evidence indicating attack vector includes likely phishing. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Credentials In Files (T1552.001) with high confidence (90%), supported by evidence indicating aPI keys and access tokens exposed in screenshots and Unsecured Credentials: Cloud Instance Metadata API (T1552.005) with moderate to high confidence (70%), supported by evidence indicating firebase Cloud Messaging (FCM) user accounts exposed. Under the Collection tactic, the analysis identified Data from Information Repositories (T1213) with high confidence (90%), supported by evidence indicating internal dashboards, user management panels, token databases accessed and Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating mattermost chat logs and threat intelligence documents exfiltrated. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), supported by evidence indicating data exfiltration confirmed, screenshots publicly leaked and Exfiltration Over Web Service (T1567) with moderate to high confidence (70%), supported by evidence indicating telegram used to publicly share leaked data. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with lower confidence (30%), supported by evidence indicating collaboration with Devman ransomware group mentioned and Account Access Removal (T1531) with moderate confidence (50%), supported by evidence indicating potential compromise of cybersecurity operations. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Resecurity Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/resecurity/incident/RES1767463312
- Resecurity CyberSecurity Rating page: https://www.rankiteo.com/company/resecurity
- Resecurity Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/res1767463312-breach-january-2026/
- Resecurity CyberSecurity Score History: https://www.rankiteo.com/company/resecurity/history
- Resecurity CyberSecurity Incident Source: https://hackread.com/shinyhunters-breach-us-cybersecurity-resecurity-firm/
- 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