Skip to main content

Ransomware victim disclosure

All victims

General Distributing

Claimed by Medusa · listed 8 months ago

168 Employees
Records
7m
Age
since listed · data leaked

Status timeline

  1. ListedNov 21, 2025
  2. Data leakeddate unknown

At a glance

Group
Medusa
Status
Data leaked
Listed on leak site
Nov 21, 2025
Records
168 Employees

About the victim

AI dossier — public-source company profile

General Distributing is a U.S.-based wholesale distribution and logistics company. Based on the sector classification, the company likely operates in the transportation or wholesale distribution space, moving goods to retailers or commercial customers. No further details are available from the leak post or a public site excerpt.

Industry
Wholesale Distribution / Transportation & Logistics

Attack summary

Severity: high — The disclosed status is 'data_published', meaning Medusa claims to have already released exfiltrated data. Even without confirmed specifics, a wholesale distributor likely holds business records, customer/supplier PII, financial data, and logistics information, warranting a high severity rating. Critical would require confirmed regulated data (e.g., medical or government) at scale, which cannot be verified here.

The Medusa ransomware group claims an attack against General Distributing and has marked the disclosure status as data_published, indicating exfiltrated data has been released. The leak post content was not accessible due to a CAPTCHA challenge, so specific data categories and volumes cannot be confirmed.

high

What the group claims

General Distributing Co is a company that operates in the Convenience Stores, Gas Stations & Liquor Stores industry. It employs 100to249 people and has 25Mto50M of revenue. The company is headquartered in Salt Lake City, Utah. company is headquartered in 5350 W Amelia Earhart Drive, Salt Lake City, UT 84116, USA. 168 Employees

The leak post

captured from the group's site
Human Verify Human verification required We need to ensure you're a real person. Please solve the captcha below to continue. Verify

Sources

Source

Indexed 8 months 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 Medusa

Medusa, also known as MedusaLocker, is a financially motivated ransomware group that emerged in November 2022 and has since compromised 568 known victims across multiple countries. The group's origin and specific affiliations remain unclear from publicly available intelligence, though their operational patterns suggest they function as an independent ransomware operation rather than a documented Ransomware-as-a-Service model. Medusa primarily targets organizations in the United States, United Kingdom, Canada, Italy, and Australia, with a focus on business services, healthcare, manufacturing, and technology sectors, employing typical ransomware tactics including data encryption and likely exfiltration for double extortion purposes, though specific technical methodologies and initial access vectors have not been extensively documented in public threat intelligence reports. While the group has maintained a relatively high victim count since its emergence, detailed information about specific notable campaigns, high-profile victims, or major ransom demands has not been widely reported by major cybersecurity firms or law enforcement agencies. As of current intelligence assessments, Medusa appears to remain active in the threat landscape, continuing to target organizations across their established geographic and sectoral preferences. The group has been linked to 635 public disclosures across our corpus. First observed on a leak site on November 15, 2022; most recent post May 5, 2026. The operation is currently active.

Also tracked as: MedusaLocker, MEDUSA LOCKER.

Timeline of this disclosure

  • November 21, 2025General Distributing listed by Medusaon the group's public leak site
Records
168 Employees

Sector and geography

This disclosure adds to ransomware activity in the Transportation/Logistics sector, which has 1,081 disclosures indexed across all operators we track. Geographically, General Distributing is reported in United States, a country with 11,033 ransomware disclosures in our corpus.

If your organisation is affected

A listing by Medusa means General Distributing 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, CISA (United States), as required for your jurisdiction.
  • Monitor for the data appearing on Medusa'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.