Gitlabs: Synelixis Solutions, INGV, VMO Holdings
bd_4458309bef88513a · schema v1 · pii pii-v1
Full breach record for Gitlabs: Synelixis Solutions, INGV, VMO Holdings →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Fog on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
It seems there is a bit of confusion in the request as GitLab, Synelixis Solutions, INGV (National Institute of Geophysics and Volcanology), and VMO Holdings appear to be separate entities. GitLab is a web-based DevOps tool that provides a platform for software development and version control. Synelixis Solutions is an IT company specializing in hardware and software solutions. INGV deals with research in geophysics and volcanology. VMO Holdings is a private holding company.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Feb 26, 2025
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
fog
According to ransomware.live, 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.