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

Incident Score: Analysis & Impact (GOG1768273478)

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

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-5
Company Score Before Incident755 / 1000
Company Score After Incident750 / 1000
Company LinkView GOG Profile
INCIDENT NUMBERGOG1768273478
Type of Cyber IncidentVulnerability
ATTACK VECTORExploitation of symbolic links bypass in Gogs
DATA EXPOSEDNA
INCIDENT DATE09/07/2025
STATUSOngoing

Key Highlights From The Incident Analysis

  • Timeline of GOG'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 GOG 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 GOG breach identified under incident ID GOG1768273478.

The analysis begins with a detailed overview of GOG's information like the linkedin page: https://www.linkedin.com/company/gogcom, the number of followers: 11267, the industry type: Computer Games and the number of employees: 812 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 755 and after the incident was 750 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 GOG and their customers.

On 10 December 2025, Gogs (self-hosted Git service) disclosed Remote Code Execution (RCE) issues under the banner "CVE-2025-8110 Exploitation in Gogs Self-Hosted Git Service".

The United States Cybersecurity & Infrastructure Security Agency (CISA) added CVE-2025-8110, a remote code execution vulnerability in the Gogs self-hosted Git service, to its Known Exploited Vulnerabilities Catalog.

The disruption is felt across the environment, affecting 1,400 internet-facing Gogs instances (over 50% compromised).

In response, and began remediation that includes Maintainers working on a fix (unpatched as of writing).

The case underscores how Ongoing, and recommending next steps like Patch Gogs instances once a fix is available; monitor for suspicious repository activity (e.g., random 8-character owner/repo names).

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%), with evidence including cVE-2025-8110, a remote code execution (RCE) vulnerability in Gogs, and over 1,400 internet-facing Gogs instances detected. Under the Execution tactic, the analysis identified Exploitation for Client Execution (T1203) with high confidence (90%), with evidence including arbitrary command execution on compromised systems, and supershell-based malware deployed via RCE. Under the Persistence tactic, the analysis identified Server Software Component: Web Shell (T1505.003) with moderate to high confidence (80%), with evidence including supershell-based malware installed on compromised systems, and eight-character random owner/repo names created. Under the Defense Evasion tactic, the analysis identified Exploitation for Defense Evasion (T1211) with moderate to high confidence (80%), supported by evidence indicating symbolic links bypass in Gogs to overwrite files outside repositories and Masquerading (T1036) with moderate to high confidence (70%), supported by evidence indicating random 8-character owner/repo names to blend in with legitimate activity. Under the Command and Control tactic, the analysis identified Application Layer Protocol (T1071) with moderate to high confidence (70%), supported by evidence indicating supershell-based malware likely uses C2 channels for remote control. 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%)
Execution
Exploitation for Client Execution (90%)
Persistence
Server Software Component: Web Shell (80%)
Defense Evasion
Exploitation for Defense Evasion (80%)
Masquerading (70%)
Command and Control
Application Layer Protocol (70%)

Sources & References