Skip to main content

Ransomware victim disclosure

All victims

kr3m. media GmbH

listed as Kr3m · Claimed by Fog · listed 1 year ago

16m
Age
since listed · data leaked

Status timeline

  1. ListedMar 6, 2025
  2. Data leakeddate unknown

At a glance

Group
Fog
Status
Data leaked
Country
Germany
Listed on leak site
Mar 6, 2025

About the victim

AI dossier — public-source company profile

kr3m. media GmbH is a German media company based on the domain kr3m.com. The public site indicates a digital media/creative services focus, though specific operational details are limited in available excerpts.

Industry
Media & Digital Services

Attack summary

Severity: medium — GitLab access suggests potential exposure of source code and development secrets; however, no proof files are advertised, no ransom demand stated, and no confirmation of actual exfiltration or operational impact. Medium reflects the risk inherent in developer platform compromise without confirmed data publication.

The Fog group claims to have accessed kr3m.'s GitLab instance(s), listing this victim among '19 biggest gitlabs'. No explicit confirmation of data exfiltration, encryption, or ransom demand is stated in the truncated post.

medium

Data the group says was taken

AI dossier — extracted from the leak post
  • GitLab repositories/source code
  • development infrastructure

What the group claims

Extract from The 19 biggest gitlabs

Sources

Source

Indexed 1 year ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About Fog

Fog is a relatively new ransomware group that emerged in July 2024, operating with apparent financial motivations and demonstrating rapid expansion in their victim targeting across multiple geographic regions and industry sectors. The group's origin and specific affiliations remain unclear due to their recent emergence, though their operational patterns suggest they likely operate independently rather than as part of an established Ransomware-as-a-Service ecosystem. Given the limited public documentation from major security agencies and researchers due to the group's recent appearance, specific details about their attack methodology, initial access vectors, and encryption techniques have not yet been comprehensively analyzed or reported by authoritative sources such as CISA, FBI, or major threat intelligence firms. The group has reportedly victimized 189 organizations primarily across the United States, Germany, France, Australia, and Brazil, with their attacks predominantly targeting the technology sector, followed by education, business services, and manufacturing industries, though no specific high-profile campaigns or record ransom demands have been publicly documented by major security researchers at this time. As of current reporting, Fog appears to remain active given their recent emergence and ongoing victim acquisition patterns observed throughout 2024. The group has been linked to 189 public disclosures across our corpus. First observed on a leak site on July 16, 2024; most recent post March 20, 2025. The operation is currently inactive.

Timeline of this disclosure

  • March 6, 2025Kr3m listed by Fogon the group's public leak site

Sector and geography

Geographically, Kr3m is reported in Germany, a country with 926 ransomware disclosures in our corpus.

If your organisation is affected

A listing by Fog means Kr3m appeared on a ransomware extortion site and data attributed to it has been published. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

  • Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
  • Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
  • Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
  • Report the incident to your national CERT, CERT-Bund (Germany), as required for your jurisdiction.
  • Monitor for the data appearing on Fog's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.