Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Joomla! » ORAJOOMANWPMDIGTHE1783693992

Incident Score: Analysis & Impact (ORAJOOMANWPMDIGTHE1783693992)

The details regarding individual company incidents & reports gives you full view from every side.

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-19
Company Score Before Incident767 / 1000
Company Score After Incident748 / 1000
INCIDENT NUMBERORAJOOMANWPMDIGTHE1783693992
Type of Cyber IncidentVulnerability
ATTACK VECTORExploiting known vulnerabilities, Automated scanning, Webshell deployment
DATA EXPOSEDConfiguration files, Cloud credentials (AWS,...
INCIDENT DATE10/06/2026
STATUSOngoing (exposure discovered, but full scope of compromise may still be unknown)

Key Highlights From The Incident Analysis

  • Timeline of Joomla!'s Vulnerability 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 Joomla! 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 Joomla! breach identified under incident ID ORAJOOMANWPMDIGTHE1783693992.

The analysis begins with a detailed overview of Joomla!'s information like the linkedin page: https://www.linkedin.com/company/joomla, the number of followers: 14223, the industry type: Technology, Information and Internet and the number of employees: 145 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 767 and after the incident was 748 with a difference of -19 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 Joomla! and their customers.

On 09 July 2026, a cybersecurity incident called "WP-SHELLSTORM Cybercrime Group's Exposed Server Reveals Mass Webshell Operation Targeting 1.4 Million Sites" came to light.

A cybercrime group, tracked as WP-SHELLSTORM, inadvertently exposed its operations for three weeks after leaving an unsecured server online.

The disruption is felt across the environment, affecting WordPress sites (45,000+ targeted, 17,000+ compromised), Joomla sites (560,000+ targeted, 77 compromised) and Java-based corporate systems (11 systems across 9 companies), and exposing Configuration files, Cloud credentials (AWS, Alibaba, Oracle, Tencent, DigitalOcean) and Database passwords, with nearly 613 configuration files from 11 systems; 1.4 million websites targeted records at risk.

In response, moved swiftly to contain the threat with measures like Group deleted log entries between July 2–4 after exposure was discovered.

The case underscores how Ongoing (exposure discovered, but full scope of compromise may still be unknown), teams are taking away lessons such as Human error (unsecured server) led to exposure of a major cybercrime operation. Basic security hygiene (e.g., securing servers, sanitizing logs) is critical even for sophisticated threat actors, and recommending next steps like Patch known vulnerabilities promptly, especially in WordPress and Joomla plugins, Monitor for webshell activity and unusual processes (e.g., [kworker/0:2]) and Secure servers and sanitize logs to avoid exposure of operational details.

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 (90%), supported by evidence indicating exploited 27 known vulnerabilities, primarily in WordPress plugins and External Remote Services (T1133) with moderate to high confidence (80%), supported by evidence indicating deployed webshells granting remote control over compromised servers. Under the Execution tactic, the analysis identified Command and Scripting Interpreter: Unix Shell (T1059.004) with moderate to high confidence (80%), supported by evidence indicating webshells (down.php, VShell) used for remote command execution and Exploitation for Client Execution (T1203) with moderate to high confidence (70%), supported by evidence indicating exploited CVE-2026-3844, CVE-2026-48907 to deploy webshells. Under the Persistence tactic, the analysis identified Server Software Component: Web Shell (T1505.003) with high confidence (90%), supported by evidence indicating installed webshells (down.php, VShell) on 25,195+ sites and Create or Modify System Process: Windows Service (T1543.003) with moderate to high confidence (70%), supported by evidence indicating vShell disguised as kernel process (kworker/0 such as 2). Under the Privilege Escalation tactic, the analysis identified Exploitation for Privilege Escalation (T1068) with moderate to high confidence (70%), supported by evidence indicating exploited vulnerabilities in plugins to gain remote control. 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 vShell disguised as kernel process (kworker/0 such as 2), Obfuscated Files or Information: Command Obfuscation (T1027.010) with moderate to high confidence (70%), supported by evidence indicating down.php webshell heavily obfuscated (derived from BestShell), and Hide Artifacts: Hidden Window (T1564.003) with moderate confidence (60%), supported by evidence indicating webshells designed to evade detection. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Credentials In Files (T1552.001) with high confidence (90%), supported by evidence indicating extracted cloud credentials (AWS, Alibaba, Oracle, Tencent, DigitalOcean) and Unsecured Credentials: Private Keys (T1552.004) with moderate to high confidence (80%), supported by evidence indicating alipay RSA private keys compromised. Under the Discovery tactic, the analysis identified Active Scanning: Vulnerability Scanning (T1595.002) with high confidence (90%), supported by evidence indicating used FOFA to build target lists of 1.4 million websites and File and Directory Discovery (T1083) with moderate to high confidence (70%), supported by evidence indicating extracted 613 configuration files from 11 systems. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating extracted configuration files, database passwords, private keys. Under the Command and Control tactic, the analysis identified Application Layer Protocol: Web Protocols (T1071.001) with high confidence (90%), supported by evidence indicating webshells (down.php, VShell) used for C2 communication. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), supported by evidence indicating webshell access brokerage implies data exfiltration/sale. Under the Impact tactic, the analysis identified Resource Hijacking (T1496) with moderate to high confidence (70%), supported by evidence indicating compromised 25,195+ sites for resale of access. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Exploit Public-Facing Application (90%)
External Remote Services (80%)
Execution
Command and Scripting Interpreter: Unix Shell (80%)
Exploitation for Client Execution (70%)
Persistence
Server Software Component: Web Shell (90%)
Create or Modify System Process: Windows Service (70%)
Privilege Escalation
Exploitation for Privilege Escalation (70%)
Defense Evasion
Masquerading: Match Legitimate Name or Location (80%)
Obfuscated Files or Information: Command Obfuscation (70%)
Hide Artifacts: Hidden Window (60%)
Credential Access
Unsecured Credentials: Credentials In Files (90%)
Unsecured Credentials: Private Keys (80%)
Discovery
Active Scanning: Vulnerability Scanning (90%)
File and Directory Discovery (70%)
Collection
Data from Local System (80%)
Command and Control
Application Layer Protocol: Web Protocols (90%)
Exfiltration
Exfiltration Over C2 Channel (80%)
Impact
Resource Hijacking (70%)