GI
Ransomware Victim Technology

Gitlabs: Professional Computer, X-Pans, Propulsion Academy AG

Ransomware attack by Fog Β· Disclosed January 30, 2025 Β· πŸ‡¨πŸ‡­ Switzerland

Date Disclosed
Jan 30, 2025
2025
Threat Group
Fog
189 total victims
Industry
Technology

ThreatAI Analysis

Compiled from this incident record and the threat intelligence profile for Fog. Figures and technique mappings are quoted from the source data, not inferred.

About the Fog group

Fog, which uses the .flocked extension for encrypted files, was first observed in May in campaigns by Storm-0844, a threat actor known for distributing Akira. By June, Storm-0844 was deploying Fog more than Akira. Fog has listed 189 victims since December 2021.

Incident Analysis

Gitlabs: Professional Computer, X-Pans, Propulsion Academy AG was targeted by Fog ransomware, one of the most active ransomware groups in our database with 189 confirmed victims globally. The attack was disclosed on January 30, 2025, when Gitlabs: Professional Computer, X-Pans, Propulsion Academy AG appeared on the group's dark web leak site.

Gitlabs: Professional Computer, X-Pans, Propulsion Academy AG is based in Switzerland , operating in the Technology sector. Switzerland ranks #13 globally for ransomware attacks, with 199 victims in our database.

Sector context: Technology companies hold intellectual property, customer data, and source code β€” all highly valuable assets. A successful ransomware attack can also put downstream customers at risk through supply chain exposure.

Fog typically employs a double extortion model: first exfiltrating sensitive data from the victim's systems, then deploying ransomware to encrypt files. Victims face two simultaneous threats β€” paying to restore access and paying to prevent publication of stolen data. The group's leak site publishes victim names and exfiltrated data as leverage.

Data source: This incident record is sourced from public ransomware group leak site disclosures aggregated via the ransomware.live API. Disclosure date reflects when the victim was published on the leak site, which may differ from the initial date of compromise. This platform does not publish or link to stolen data. Last data update: Sep 22, 2026 12:00 UTC.

Frequently Asked Questions

Was Gitlabs: Professional Computer, X-Pans, Propulsion Academy AG attacked by ransomware?

Yes. Gitlabs: Professional Computer, X-Pans, Propulsion Academy AG was listed as a victim of the Fog ransomware group on January 30, 2025. The organisation is based in Switzerland and operates in the Technology sector. The disclosure appeared on the group's dark web leak site.

Which ransomware group attacked Gitlabs: Professional Computer, X-Pans, Propulsion Academy AG?

Gitlabs: Professional Computer, X-Pans, Propulsion Academy AG was attacked by Fog ransomware. Fog is one of the most active ransomware groups, having claimed 189 victims globally. The group typically employs a double-extortion model: encrypting the victim's files and threatening to publish stolen data.

When did the Gitlabs: Professional Computer, X-Pans, Propulsion Academy AG ransomware attack occur?

The ransomware attack on Gitlabs: Professional Computer, X-Pans, Propulsion Academy AG was disclosed on January 30, 2025. This date reflects when the victim was published on the threat group's leak site, which may differ from the actual date of initial compromise.

What data was stolen in the Gitlabs: Professional Computer, X-Pans, Propulsion Academy AG ransomware attack?

The specific data stolen from Gitlabs: Professional Computer, X-Pans, Propulsion Academy AG has not been independently verified by this platform. Ransomware groups typically exfiltrate data before encrypting systems and use the threat of publication to pressure victims. As a Technology organisation, Gitlabs: Professional Computer, X-Pans, Propulsion Academy AG likely held source code, intellectual property, and customer data.

How can organisations protect against Fog attacks?

To defend against Fog and similar threat actors, organisations should: maintain regular offline backups tested for restoration; implement network segmentation to limit lateral movement; deploy multi-factor authentication on all remote access; use endpoint detection and response (EDR) tools; conduct regular phishing and security awareness training; and monitor threat intelligence feeds for indicators of compromise (IOCs) associated with active groups.