Incident Score: Analysis & Impact (MER1775377932)
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 Merck's Cyber Attack 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 Merck 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 Merck breach identified under incident ID MER1775377932.
The analysis begins with a detailed overview of Merck's information like the linkedin page: https://www.linkedin.com/company/merck, the number of followers: 2635829, the industry type: Pharmaceutical Manufacturing and the number of employees: 44762 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 835 and after the incident was 825 with a difference of -10 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 Merck and their customers.
A newly reported cybersecurity incident, "The Hidden Costs of Industrial Cybersecurity: OT Breaches and Risk Reshaping", has drawn attention.
The economics of industrial cybersecurity are undergoing a fundamental shift, moving beyond preventive spending to account for the cascading financial and operational impacts of cyber incidents.
The disruption is felt across the environment, affecting Operational Technology (OT) Systems, Industrial Control Systems (ICS) and Critical Infrastructure (Energy, Water, Transportation), plus an estimated financial loss of $4.56 million (average OT breach cost).
Formal response steps have not been shared publicly yet.
The case underscores how teams are taking away lessons such as OT security must be treated as a core business function, not a discretionary expense. The financial and operational consequences of inaction are now central to risk calculations. Cybersecurity is shifting from compliance to strategic risk management, with a focus on operational resilience, consequence-based risk assessments, and alignment with business metrics, and recommending next steps like Translate risk into financial terms to secure board/CFO buy-in, Align OT security with operational metrics (e.g., production availability, mean time to recovery) and Prioritize high-consequence events (HCEs) where failure would trigger safety incidents or sustained production losses.
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 attacks on operational technology (OT) systems rising and External Remote Services (T1133) with moderate confidence (60%), supported by evidence indicating volt Typhoon pre-positioned in IT networks to disrupt OT systems. Under the Persistence tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating bRICKSTORM maintained access for an average of 393 days and BITS Jobs (T1197) with lower confidence (40%), supported by evidence indicating state-sponsored actors with long dwell times. Under the Lateral Movement tactic, the analysis identified Exploitation of Remote Services (T1210) with moderate confidence (60%), supported by evidence indicating adversaries targeting IT networks to disrupt OT systems and Lateral Tool Transfer (T1570) with moderate confidence (50%), supported by evidence indicating iran-backed groups demonstrated destructive OT capabilities. Under the Impact tactic, the analysis identified Loss of Productivity and Revenue (T0883) with high confidence (90%), supported by evidence indicating 800 hours of production time lost annually, $50B downtime cost, Loss of Safety (T0829) with moderate to high confidence (80%), supported by evidence indicating safety failures, environmental disasters, or loss of life risks, and Loss of Control (T0880) with moderate to high confidence (70%), supported by evidence indicating disruption at an auto plant or pipeline shutdown. Under the Defense Evasion tactic, the analysis identified Valid Accounts: Domain Accounts (T1078.002) with moderate confidence (60%), supported by evidence indicating bRICKSTORM maintained access for 393 days before detection and Hide Artifacts: Hidden Files and Directories (T1564.001) with moderate confidence (50%), supported by evidence indicating state-sponsored actors with long dwell times. Under the Command and Control tactic, the analysis identified Application Layer Protocol: Web Protocols (T1071.001) with moderate confidence (50%), supported by evidence indicating volt Typhoon pre-positioned in IT networks. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with lower confidence (40%), supported by evidence indicating nation-state espionage motivations. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Merck Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/merck/incident/MER1775377932
- Merck CyberSecurity Rating page: https://www.rankiteo.com/company/merck
- Merck Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/mer1775377932-merck-cyber-attack-june-2025/
- Merck CyberSecurity Score History: https://www.rankiteo.com/company/merck/history
- Merck CyberSecurity Incident Source: https://industrialcyber.co/features/rising-breach-costs-and-operational-downtime-redefine-economics-of-ot-cybersecurity-making-it-boardroom-priority/
- 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