Incident Score: Analysis & Impact (WHMPACGITCPA1784816835)
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 Packagist Conductors'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 Packagist Conductors 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 Packagist Conductors breach identified under incident ID WHMPACGITCPA1784816835.
The analysis begins with a detailed overview of Packagist Conductors's information like the linkedin page: https://www.linkedin.com/company/packagist, the number of followers: 902, the industry type: Information Technology & Services and the number of employees: 8 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 752 and after the incident was 733 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 Packagist Conductors and their customers.
On 12 July 2026, dinushchathurya (Packagist account) disclosed Supply Chain Attack issues under the banner "Large-Scale Cyber Campaign Hijacks GitHub Actions to Target Web Hosting Servers".
A sophisticated cyber campaign is exploiting GitHub Actions to weaponize trusted open-source projects, turning them into tools for scanning and compromising web hosting servers.
The disruption is felt across the environment, affecting cPanel and WHM servers, web hosting infrastructure, and exposing Cloud credentials, payment data, source control tokens (AWS keys, GitHub/GitLab tokens, OpenAI/Google API keys, Stripe credentials, SSH material).
In response, moved swiftly to contain the threat with measures like Disabling suspicious workflows, rotating credentials, and began remediation that includes Patching cPanel/WHM systems (CVE-2026-41940).
The case underscores how Active, teams are taking away lessons such as Risks of untrusted automation in CI/CD pipelines, importance of credential rotation and patch management, and recommending next steps like Disable suspicious GitHub Actions workflows, rotate exposed credentials, patch cPanel/WHM systems, monitor for unauthorized access.
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 Supply Chain Compromise: Compromise Software Supply Chain (T1195.002) with high confidence (90%), with evidence including compromised a legitimate PHP developer’s Packagist account, and injected malicious GitHub Actions workflow files into ten development versions and Exploit Public-Facing Application (T1190) with moderate to high confidence (80%), supported by evidence indicating exploits CVE-2026-41940, an authentication bypass flaw in cPanel and WHM. Under the Execution tactic, the analysis identified Serverless Execution (T1648) with high confidence (90%), with evidence including launch temporary Ubuntu runners via GitHub Actions workflows, and spinning up an ephemeral GitHub runner and User Execution: Malicious File (T1204.002) with moderate to high confidence (70%), supported by evidence indicating workflows...launch temporary Ubuntu runners that download Linux payloads. Under the Persistence tactic, the analysis identified Hijack Execution Flow: DLL Side-Loading (T1574.002) with moderate confidence (60%), supported by evidence indicating malicious GitHub Actions workflow files into ten development versions of their packages and Valid Accounts: Cloud Accounts (T1078.004) with moderate to high confidence (70%), supported by evidence indicating compromised maintainer account (dinushchathurya). Under the Privilege Escalation tactic, the analysis identified Exploitation for Privilege Escalation (T1068) with moderate to high confidence (80%), supported by evidence indicating exploits CVE-2026-41940, an authentication bypass flaw in cPanel and WHM. Under the Defense Evasion tactic, the analysis identified Modify Cloud Compute Infrastructure: Create Cloud Instance (T1578.003) with moderate to high confidence (80%), supported by evidence indicating spinning up an ephemeral GitHub runner via GitHub Actions and Masquerading: Match Legitimate Name or Location (T1036.005) with moderate to high confidence (70%), with evidence including weaponize trusted open-source projects, and compromised a legitimate PHP developer’s Packagist account. Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1528) with high confidence (90%), supported by evidence indicating expose cloud credentials...AWS keys, GitHub/GitLab tokens, OpenAI/Google API keys and Unsecured Credentials: Private Keys (T1552.004) with high confidence (90%), supported by evidence indicating sSH material...compromised via cPanel and WHM servers. Under the Discovery tactic, the analysis identified Active Scanning: Vulnerability Scanning (T1595.002) with moderate to high confidence (80%), supported by evidence indicating scan the internet for vulnerable hosts via GitHub runners. Under the Collection tactic, the analysis identified Data from Cloud Storage (T1530) with moderate to high confidence (80%), supported by evidence indicating cloud credentials, payment data, source control tokens compromised and Data from Local System (T1005) with moderate to high confidence (70%), supported by evidence indicating jeopardize multiple customer accounts, databases, and application secrets. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating exfiltrates stolen data in small chunks via HTTP POST requests and Transfer Data to Cloud Account (T1537) with moderate to high confidence (70%), supported by evidence indicating heartbeats sent every 30 seconds to threat actor-controlled server (43.228.157.68). Under the Impact tactic, the analysis identified Resource Hijacking (T1496) with moderate to high confidence (80%), supported by evidence indicating abuses free GitHub compute resources to target cPanel and WHM servers. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Packagist Conductors Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/packagist/incident/WHMPACGITCPA1784816835
- Packagist Conductors CyberSecurity Rating page: https://www.rankiteo.com/company/packagist
- Packagist Conductors Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/whmpacgitcpa1784816835-packagist-whm-cpanel-github-cyber-attack-july-2026/
- Packagist Conductors CyberSecurity Score History: https://www.rankiteo.com/company/packagist/history
- Packagist Conductors CyberSecurity Incident Source: https://cybersecuritynews.com/hackers-abuse-github-actions-to-exploit-cpanel/
- 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