GLOBALMalwareRansomwareFogRansom DemandedActor NamedData Leak ThreatenedData PublishedHigh
Gitlabs: Omydoo, Ayomi, ADULLACT
bd_61cc0d22af8154d5 · schema v1 · pii pii-v1
Full breach record for Gitlabs: Omydoo, Ayomi, ADULLACT →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.
Group activity: Not FoundDiscovered: 2025-02-13
Source: Ransomware.live
Tracked as a single-filing incident — the only disclosure on record for this event so far.Unverified claimView incident
No regulatory filing corroborates this yet. If an SEC 8-K, state-AG notice, or victim statement lands, DisclosureLens will merge it into an incident and link it here.
Source provenance
- Source URL
- https://www.ransomware.live/id/R2l0bGFiczogT215ZG9vLCBBeW9taSwgQURVTExBQ1RAZm9n
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Feb 13, 2025
- Raw hash
- bed1a773c5c587478956d28df9b9d3e39685c222e4bade28023bf92f814ae938
Reporting entity
- Name
- fog
Victim entity
- Name
- Gitlabs: Omydoo, Ayomi, ADULLACTnorm: gitlabs omydoo ayomi adullact
What this source establishes
- Source ceiling
- A leak-site claim can't tell us: discovery date · materiality · notification · affected count · confirmed data types · compliance clock. These stay blank until a regulatory filing or victim disclosure lands.
- Attack vector
- Ransomware· fog
- Threat actor
- FogExternalFinancial
Compliance
- Compliance flags
- — (clock not assessable for this source)
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.