Incident Score: Analysis & Impact (ORAJOOMANWPMDIGTHE1783693992)
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 DigitalOcean'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 DigitalOcean 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 DigitalOcean breach identified under incident ID ORAJOOMANWPMDIGTHE1783693992.
The analysis begins with a detailed overview of DigitalOcean's information like the linkedin page: https://www.linkedin.com/company/digitalocean, the number of followers: 158363, the industry type: Software Development and the number of employees: 2363 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 705 and after the incident was 700 with a difference of -5 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 DigitalOcean 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 Exploitation of Remote Services (T1210) with moderate to high confidence (80%), supported by evidence indicating nacos configuration server flaw (CVE-2021-29441) exploited. 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) granting remote control over servers and Exploitation for Client Execution (T1203) with moderate to high confidence (70%), supported by evidence indicating automated scanning and exploitation of WordPress/Joomla plugins. Under the Persistence tactic, the analysis identified Server Software Component: Web Shell (T1505.003) with high confidence (90%), supported by evidence indicating 25,195+ sites with webshells (down.php, VShell) installed. Under the Privilege Escalation tactic, the analysis identified Exploitation for Privilege Escalation (T1068) with moderate to high confidence (70%), supported by evidence indicating webshells granting remote control imply privilege escalation. Under the Defense Evasion tactic, the analysis identified Masquerading: Masquerade Task or Service (T1036.004) with moderate to high confidence (80%), supported by evidence indicating vShell disguised as a kernel process (kworker/0 such as 2), Obfuscated Files or Information (T1027) with moderate to high confidence (80%), supported by evidence indicating down.php - heavily obfuscated webshell 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 613 configuration files extracted, including cloud credentials and database passwords and Unsecured Credentials: Private Keys (T1552.004) with high confidence (90%), supported by evidence indicating alipay RSA private keys exposed. Under the Discovery tactic, the analysis identified Active Scanning: Vulnerability Scanning (T1595.002) with high confidence (90%), supported by evidence indicating fOFA used 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 activity logs and scan results found on exposed server. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating 613 configuration files extracted from 11 corporate systems. 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 for resale and Exfiltration Over Web Service: Exfiltration to Cloud Storage (T1567.002) with moderate confidence (60%), supported by evidence indicating cloud credentials (AWS, Alibaba, Oracle) extracted. Under the Impact tactic, the analysis identified Resource Hijacking (T1496) with moderate to high confidence (70%), supported by evidence indicating webshells installed for resale of access to other criminals. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- DigitalOcean Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/digitalocean/incident/ORAJOOMANWPMDIGTHE1783693992
- DigitalOcean CyberSecurity Rating page: https://www.rankiteo.com/company/digitalocean
- DigitalOcean Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/orajoomanwpmdigthe1783693992-themerex-joomla-simple-file-list-wp-file-manager-oracle-digitalocean-vulnerability-june-2026/
- DigitalOcean CyberSecurity Score History: https://www.rankiteo.com/company/digitalocean/history
- DigitalOcean CyberSecurity Incident Source: https://thehackernews.com/2026/07/exposed-hacker-server-reveals-wp.html
- 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