Ericsson Breach Incident Score: Analysis & Impact (JOHROLERI1772202424)
The Rankiteo video explains how the company Ericsson has been impacted by a Breach on the date February 23, 2026.
Incident Summary
If the player does not load, you can open the video directly.
Key Highlights From This Incident Analysis
- Timeline of Ericsson'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 Ericsson 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 Ericsson breach identified under incident ID JOHROLERI1772202424.
The analysis begins with a detailed overview of Ericsson's information like the linkedin page: https://www.linkedin.com/company/ericsson, the number of followers: 2260541, the industry type: Telecommunications and the number of employees: 107243 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 681 and after the incident was 618 with a difference of -63 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 Ericsson and their customers.
On 23 February 2026, Rolls-Royce disclosed Credential Stuffing issues under the banner "Credential Stuffing Campaign Exploits Stolen Employee Logins to Breach Corporate Networks".
A sophisticated credential stuffing campaign targeting corporate Single Sign-On (SSO) gateways, particularly F5 BIG-IP interfaces, leveraged stolen employee credentials harvested from infostealer malware infections to gain network access.
The disruption is felt across the environment, affecting ADFS, Security Token Services (STS) and OWA portals, and exposing Employee credentials, potential access to internal systems, with nearly 70 unique credentials records at risk.
Formal response steps have not been shared publicly yet.
The case underscores how Ongoing, teams are taking away lessons such as The incident underscores the critical importance of multi-factor authentication (MFA) and the risks posed by infostealer malware in enabling credential stuffing attacks. Identity is now the new perimeter, and stolen credentials can bypass traditional security measures, and recommending next steps like Implement multi-factor authentication (MFA) for all corporate systems, especially SSO and remote access gateways, Monitor for infostealer malware infections on employee devices and Enforce strict password policies and regular credential rotation.
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.
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 high confidence (95%), supported by evidence indicating 77% of the 70 unique credentials matched known infostealer infection logs, Exploit Public-Facing Application (T1190) with moderate to high confidence (70%), supported by evidence indicating targeting corporate Single Sign-On (SSO) gateways particularly F5 BIG-IP interfaces, and External Remote Services (T1133) with moderate to high confidence (85%), supported by evidence indicating credentials repurposed against ADFS, Security Token Services (STS), and OWA portals. Under the Credential Access tactic, the analysis identified Credentials from Password Stores (T1555) with high confidence (90%), supported by evidence indicating credentials harvested from infostealer malware infections on employee devices and Brute Force: Credential Stuffing (T1110.004) with high confidence (95%), supported by evidence indicating sophisticated credential stuffing campaign targeting corporate SSO gateways. Under the Execution tactic, the analysis identified Command and Scripting Interpreter (T1059) with moderate to high confidence (70%), supported by evidence indicating automated login attempts using credentials. Under the Persistence tactic, the analysis identified Valid Accounts (T1078) with high confidence (90%), supported by evidence indicating stolen employee credentials used to gain network access. Under the Defense Evasion tactic, the analysis identified Subvert Trust Controls: Install Root Certificate (T1553.004) with moderate confidence (60%), supported by evidence indicating source IP traced to compromised Fortinet FortiGate-60E with self-signed SSL certificate and Valid Accounts (T1078) with moderate to high confidence (85%), supported by evidence indicating stolen credentials bypass traditional security measures. Under the Lateral Movement tactic, the analysis identified Remote Services: Remote Desktop Protocol (T1021.001) with moderate to high confidence (70%), supported by evidence indicating vPNs, SSO portals, or remote access gateways targeted and Valid Accounts (T1078) with moderate to high confidence (80%), supported by evidence indicating single stolen ADFS password could unlock multiple systems. Under the Collection tactic, the analysis identified Data from Information Repositories (T1213) with moderate to high confidence (70%), supported by evidence indicating credentials repurposed against ADFS, STS, and OWA portals. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate confidence (60%), supported by evidence indicating potential data exfiltration as part of motivation. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources
- Ericsson Rankiteo Cyber Incident Details: http://www.rankiteo.com/company/ericsson/incident/JOHROLERI1772202424
- Ericsson CyberSecurity Rating page: https://www.rankiteo.com/company/ericsson
- Ericsson Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/johroleri1772202424-ericsson-rolls-royce-johnson-johnson-breach-february-2026/
- Ericsson CyberSecurity Score History: https://www.rankiteo.com/company/ericsson/history
- Ericsson CyberSecurity Incident Source: https://cybersecuritynews.com/infostealers-fuel-large-scale-brute-forcing/
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/static/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf






