Incident Score: Analysis & Impact (SOU1777645601)
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 SourceForge'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 SourceForge 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 SourceForge breach identified under incident ID SOU1777645601.
The analysis begins with a detailed overview of SourceForge's information like the linkedin page: https://www.linkedin.com/company/sourceforge-net, the number of followers: 38709, the industry type: Software Development and the number of employees: 63 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 SourceForge and their customers.
On 01 September 2025, a cybersecurity incident called "Cyber-Espionage Group HeartlessSoul Targets Russian Aviation and Government Sectors" came to light.
A cyber-espionage campaign attributed to the group HeartlessSoul has been actively targeting Russian government agencies and aviation industry organizations since at least September 2025.
The disruption is felt across the environment, and exposing Geospatial intelligence (GIS) data, screenshots, keystrokes, browser data, Telegram credentials, device locations.
Formal response steps have not been shared publicly yet.
The case underscores how Ongoing.
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 Phishing (T1566) with high confidence (90%), supported by evidence indicating heartlessSoul employs phishing emails containing malicious archive files, Phishing: Spearphishing Link (T1566.002) with moderate to high confidence (80%), supported by evidence indicating malvertising campaigns to distribute malware, Drive-by Compromise (T1189) with moderate to high confidence (80%), supported by evidence indicating fake aviation-related websites and domains to trick victims, and Supply Chain Compromise: Compromise Software Supply Chain (T1195.002) with high confidence (90%), supported by evidence indicating trojanized version of GearUP hosted on SourceForge. Under the Execution tactic, the analysis identified User Execution: Malicious File (T1204.002) with high confidence (90%), with evidence including malicious archive files, and trojanized version of GearUP. Under the Persistence tactic, the analysis identified Boot or Logon Autostart Execution (T1547) with moderate to high confidence (70%), supported by evidence indicating spyware capable of harvesting screenshots, keystrokes, browser data. Under the Privilege Escalation tactic, the analysis identified Process Injection (T1055) with moderate confidence (60%), supported by evidence indicating spyware capable of harvesting Telegram credentials and device locations. Under the Defense Evasion tactic, the analysis identified Masquerading (T1036) with high confidence (90%), supported by evidence indicating files disguised as FPV drone simulators and tools for bypassing Starlink and Obfuscated Files or Information (T1027) with moderate to high confidence (80%), supported by evidence indicating trojanized version of GearUP. Under the Credential Access tactic, the analysis identified Input Capture: Keylogging (T1056.001) with high confidence (90%), supported by evidence indicating malware harvests keystrokes and Credentials from Password Stores (T1555) with high confidence (90%), supported by evidence indicating malware harvests Telegram credentials. Under the Discovery tactic, the analysis identified System Information Discovery (T1082) with moderate to high confidence (80%), supported by evidence indicating malware determines device locations and Process Discovery (T1057) with moderate to high confidence (70%), supported by evidence indicating spyware capable of harvesting browser data. Under the Collection tactic, the analysis identified Screen Capture (T1113) with high confidence (90%), supported by evidence indicating malware harvests screenshots, Data from Local System (T1005) with high confidence (90%), supported by evidence indicating stealing geospatial intelligence (GIS) data, and Data from Information Repositories (T1213) with moderate to high confidence (80%), supported by evidence indicating harvesting browser data. Under the Command and Control tactic, the analysis identified Application Layer Protocol (T1071) with moderate to high confidence (70%), supported by evidence indicating spyware capable of exfiltrating data. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), with evidence including data exfiltration such as Yes, and stealing geospatial intelligence (GIS) data. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- SourceForge Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/sourceforge-net/incident/SOU1777645601
- SourceForge CyberSecurity Rating page: https://www.rankiteo.com/company/sourceforge-net
- SourceForge Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/sou1777645601-sourceforge-cyber-attack-september-2025/
- SourceForge CyberSecurity Score History: https://www.rankiteo.com/company/sourceforge-net/history
- SourceForge CyberSecurity Incident Source: https://therecord.media/russia-cyber-espionage-aviation
- 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