Incident Score: Analysis & Impact (FORPALGITIVA1782980964)
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 Fortinet'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 Fortinet 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 Fortinet breach identified under incident ID FORPALGITIVA1782980964.
The analysis begins with a detailed overview of Fortinet's information like the linkedin page: https://www.linkedin.com/company/fortinet, the number of followers: 1310862, the industry type: Computer and Network Security and the number of employees: 16380 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 264 and after the incident was 259 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 Fortinet and their customers.
A newly reported cybersecurity incident, "Sophisticated Supply-Chain Attack via GitHub PoCs Targeting Cybersecurity Researchers", has drawn attention.
A coordinated supply-chain campaign exploited GitHub proof-of-concept (PoC) repositories to deploy a stealthy Python-based Remote Access Trojan (RAT) called *ChocoPoC*, targeting vulnerability researchers and penetration testers.
The disruption is felt across the environment, affecting Researchers' development environments, Python-based systems, and exposing Credentials (Chrome, Edge, Brave, Firefox), shell history, system reconnaissance data, files.
In response, and began remediation that includes Removal of malicious Python packages (*skytext*, *frint*, *slogsec*), cleanup of trojanized dependencies (*_distutils_hack*, *.pth* files).
The case underscores how Ongoing, teams are taking away lessons such as Risks of unvetted PoC dependencies, need for isolated testing environments, and rigorous dependency analysis, and recommending next steps like Use isolated environments for testing PoCs, Analyze dependencies rigorously and Monitor for malicious PyPI packages and C2 infrastructure.
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 Dependencies and Development Tools (T1195.002) with high confidence (95%), with evidence including exploited GitHub proof-of-concept (PoC) repositories to deploy RAT, and malicious entries in requirements.txt (frint, skytext) and Phishing: Spearphishing Link (T1566.002) with moderate to high confidence (80%), supported by evidence indicating tricking victims into installing malicious dependencies under guise of legitimate exploit tools. Under the Execution tactic, the analysis identified Command and Scripting Interpreter: Python (T1059.006) with high confidence (90%), with evidence including pip install executed malicious Python extension (gradient.so/pyd), and choco.py downloader executed via Python and User Execution: Malicious File (T1204.002) with moderate to high confidence (85%), supported by evidence indicating researchers ran pip install on malicious requirements.txt. Under the Persistence tactic, the analysis identified Hijack Execution Flow: DLL Search Order Hijacking (T1574.001) with moderate to high confidence (80%), supported by evidence indicating trojanized _distutils_hack package and malicious .pth files in site-packages and Event Triggered Execution: Component Object Model Hijacking (T1546.015) with moderate to high confidence (70%), supported by evidence indicating malicious .pth files ensure execution on every Python interpreter startup. Under the Defense Evasion tactic, the analysis identified Obfuscated Files or Information (T1027) with high confidence (90%), supported by evidence indicating obfuscated code with anti-analysis measures (debugger detection, environment gates), Virtualization/Sandbox Evasion: System Checks (T1497.001) with moderate to high confidence (85%), supported by evidence indicating malware remains dormant in sandboxes, triggered by filename hash match, and Indicator Removal: File Deletion (T1070.004) with moderate to high confidence (70%), supported by evidence indicating ephemeral GitHub/PyPI accounts with identical operational patterns. Under the Credential Access tactic, the analysis identified Credentials from Password Stores: Credentials from Web Browsers (T1555.003) with high confidence (95%), supported by evidence indicating credential theft (Chrome, Edge, Brave, Firefox) and Unsecured Credentials: Bash History (T1552.003) with moderate to high confidence (80%), supported by evidence indicating shell history harvesting. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating file exfiltration, system reconnaissance data collection and Automated Collection (T1119) with moderate to high confidence (80%), supported by evidence indicating malware polls C2 for further instructions, executes arbitrary commands. Under the Command and Control tactic, the analysis identified Application Layer Protocol: DNS-over-HTTPS (DoH) (T1071.004) with high confidence (90%), supported by evidence indicating dNS-over-HTTPS (DoH) to resolve api.mapbox.com to attacker IP and Web Service: Bidirectional Communication (T1102.002) with moderate to high confidence (85%), supported by evidence indicating mapbox datasets used as covert C2 channel for Base64-encoded payloads. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating data exfiltration via Mapbox C2 channel and Exfiltration Over Web Service: Exfiltration to Cloud Storage (T1567.002) with moderate to high confidence (80%), supported by evidence indicating mapbox datasets used for exfiltration. Under the Reconnaissance tactic, the analysis identified Active Scanning: Vulnerability Scanning (T1595.002) with moderate to high confidence (70%), supported by evidence indicating targeted high-severity CVEs (FortiWeb, Ivanti Sentry, PAN-OS). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Fortinet Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/fortinet/incident/FORPALGITIVA1782980964
- Fortinet CyberSecurity Rating page: https://www.rankiteo.com/company/fortinet
- Fortinet Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/forpalgitiva1782980964-ivanti-fortinet-github-palo-alto-networks-vulnerability-october-2025/
- Fortinet CyberSecurity Score History: https://www.rankiteo.com/company/fortinet/history
- Fortinet CyberSecurity Incident Source: https://gbhackers.com/chocopoc-campaign-abuses-github/
- 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