Skip to main content

Ransomware victim disclosure

All victims

Crenshaw Community Hospital

Claimed by Payoutsking · listed 1 year ago

12m
Age
since listed · data leaked

Status timeline

  1. ListedJul 7, 2025
  2. Data leakeddate unknown

At a glance

Status
Data leaked
Listed on leak site
Jul 7, 2025

About the victim

AI dossier — public-source company profile

Crenshaw Community Hospital is a not-for-profit hospital located in Luverne, Alabama, serving Crenshaw County and surrounding communities since 1967. It provides comprehensive healthcare services including emergency care, outpatient clinics, laboratory and radiology services, rehabilitation facilities, mental health care, and physical therapy.

Industry
Healthcare - Hospital
Address
101 Hospital Drive, Luverne, AL 36049
Founded
1967

Attack summary

Severity: low — Disclosure status is 'data_published' but the leak post provides no proof files, screenshots, or specific details about exfiltrated data. No ransom demand or operational impact is stated. This appears to be a listing/announcement only.

The ransomware group claims to have attacked Crenshaw Community Hospital, but the leak post contains only an AI-generated description of the hospital with no specific details about what data was exfiltrated or encrypted, nor any proof of the attack.

low

Original description

AI-summarised, not from the leak post

Crenshaw Community Hospital is a medical facility based in Luverne, Alabama. Established in 1967, it offers a wide range of comprehensive health care services. In addition to an emergency department, the not-for-profit hospital operates outpatient clinics, laboratory and radiology services, and rehab facilities. The hospital remains committed to meeting the healthcare needs of Crenshaw County and the surrounding communities.

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 payoutsking

Payoutsking is a ransomware group first observed in July 2025 with an apparent primary motivation of financial gain, having been attributed to approximately 100 known victims within a relatively short operational window. Limited public documentation exists from major threat intelligence sources such as CISA, FBI, or Mandiant at this time, which is consistent with the group's recent emergence and potentially limited public disclosure of incidents. Based on available victimology data, the group has concentrated its targeting efforts primarily across the United States, Germany, the United Kingdom, France, and Spain, suggesting a deliberate focus on economically developed Western nations likely selected for their higher ransom-payment capacity. The sectors most frequently targeted include manufacturing, business services, technology, and construction, with a notable proportion of victims falling outside readily classifiable industry categories, which may indicate opportunistic targeting rather than a highly specialized vertical focus. No definitive attribution regarding country of origin, RaaS affiliation, or specific technical tooling has been publicly confirmed by authoritative sources as of this writing, and the group's attack methodology, encryption schemes, and extortion tactics remain insufficiently documented in open-source reporting to characterize with analytical confidence. Given the group's very recent emergence and the relatively high victim count accumulated in a short timeframe, payoutsking warrants continued monitoring, and security researchers and organizations in the identified target sectors should treat this actor as an active and potentially escalating threat pending further technical analysis and public disclosure. The group has been linked to 105 public disclosures across our corpus. First observed on a leak site on July 7, 2025; most recent post July 14, 2026. The operation is currently active.

Timeline of this disclosure

  • July 7, 2025Crenshaw Community Hospital listed by payoutskingon the group's public leak site

Sector and geography

This disclosure adds to ransomware activity in the Healthcare sector, which has 2,600 disclosures indexed across all operators we track. Geographically, Crenshaw Community Hospital is reported in United States, a country with 3,115 ransomware disclosures in our corpus.

If your organisation is affected

A listing by payoutsking means Crenshaw Community Hospital 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 payoutsking'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.