Skip to main content

Ransomware victim disclosure

All victims

Pamyra GmbH

listed as Gitlabs: Acqua development, QBurst, Pamyra.de · Claimed by Fog · listed 1 year ago

17m
Age
since listed · data leaked

Status timeline

  1. ListedFeb 16, 2025
  2. Data leakeddate unknown

At a glance

Group
Fog
Status
Data leaked
Country
Germany
Listed on leak site
Feb 16, 2025

About the victim

AI dossier — public-source company profile

Pamyra.de is a German online platform that aggregates and compares shipping and freight services (Spedition) across Europe. It enables private and commercial customers to compare prices and book transportation services for parcels, pallets, furniture, machinery and other freight across Germany, Austria, Switzerland and broader Europe.

Industry
Logistics & Transportation Price Comparison

Attack summary

Severity: medium — Data published status confirms exfiltration, but no proof files are advertised and no specific sensitive data categories (PII at scale, financial records, regulatory data) are confirmed. The nature and volume of compromised data from a logistics comparison platform is moderate concern.

The Fog group claims to have compromised Pamyra.de and at least two other technology firms (Acqua Development and QBurst). The leak post indicates data disclosure but provides no specific details about what data was exfiltrated or whether systems were encrypted.

medium

Data the group says was taken

AI dossier — extracted from the leak post
  • Customer booking records
  • Business transaction data
  • User account information

Original description

AI-summarised, not from the leak post

Gitlabs: Acqua development, QBurst, Pamyra.de refers to a combination of several tech companies. GitLab, a web-based DevOps lifecycle tool that provides a Git-repository manager, is pivotal. Acqua Development creates personalized software solutions, while QBurst provides development services across digital platforms. Pamyra.de, on the other hand, is a German online shipping price comparison portal, focusing on courier, express and parcel services.

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

  • February 16, 2025Gitlabs: Acqua development, QBurst, Pamyra.de listed by Fogon the group's public leak site

Sector and geography

This disclosure adds to ransomware activity in the Technology sector, which has 3,549 disclosures indexed across all operators we track. Geographically, Gitlabs: Acqua development, QBurst, Pamyra.de is reported in Germany, a country with 926 ransomware disclosures in our corpus.

If your organisation is affected

A listing by Fog means Gitlabs: Acqua development, QBurst, Pamyra.de 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.