Was stllc.org hit by ransomware?

stllc.org was listed by the lockbit5 ransomware operation (United States), and stolen data was published on the group's leak site. Darkfield tracks this disclosure with the original leak post, screenshot and group context.

Who is the lockbit5 ransomware group?

lockbit5 is a ransomware operator tracked by Darkfield. See the full operator dossier for its known victims, sectors targeted, IOCs and leak-site infrastructure.

What data was leaked in the stllc.org breach?

lockbit5 published data attributed to stllc.org. Darkfield captured the leak post and a screenshot of the listing.

Ransomware victim disclosure

← All victims

St. Luke Lutheran Community

listed as stllc.org · Claimed by Lockbit5 · listed 3 months ago

Age

since listed · data leaked

Status timeline

ListedApr 29, 2026
Data leakeddate unknown

At a glance

Group: Lockbit5
Status: Data leaked
Country: United States
Listed on leak site: Apr 29, 2026

About the victim

AI dossier — public-source company profile

St. Luke Lutheran Community is a not-for-profit, faith-based continuing care senior community headquartered in North Canton, Ohio. It operates four campuses across northeastern Ohio offering independent living, assisted living, short-term rehabilitation, memory care, nursing care, and therapy services. The organization serves older adults 24 hours a day, 365 days a year.

Industry: Senior Care & Assisted Living (Non-Profit Continuing Care)
Address: 220 Applegrove St. NE, North Canton, OH (primary campus); also 615 Latham Lane, Akron, OH; 4301 Woodale Ave. SE, Minerva, OH; 201 Holl Rd. NE, North Canton, OH

Attack summary

Severity: critical — The victim is a multi-site senior care and nursing facility handling highly sensitive regulated data including medical records, personally identifiable information, and health information for vulnerable elderly residents — falling squarely under HIPAA-regulated PHI. Data has been published, confirming exfiltration at a healthcare/social care organization.

LockBit 5 claims to have attacked St. Luke Lutheran Community and has published data (disclosed status: data_published), indicating exfiltration of organizational data from a non-profit senior care provider handling sensitive resident and patient information.

critical

Data the group says was taken

AI dossier — extracted from the leak post

Resident personal information
Patient medical/care records
Employee records
Financial records
Contact and correspondence data

What the group claims

Welcome to St. Luke Lutheran Community St. Luke Lutheran Community is a not-for-profit, continuing...

Sources

Victim sitestllc.org
Leak posthttp://lockbitapt67g6rwzjbcxnww5efpg4qok6vpfeth7wx3okj52ks4wtad.onion/post/6de4e7feefc9e0638b0ae938afc6c437

Source

Indexed 3 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 lockbit5

Based on the provided data, LockBit5 appears to be a recently emerged ransomware operation first observed in December 2025, representing what may be a new iteration or rebrand within the LockBit ransomware ecosystem, with primary financial motivations evidenced by their targeting of high-value sectors. Given the LockBit naming convention and the timing of emergence, this group likely operates from Eastern Europe or Russia and may represent either a continuation of previous LockBit operations or a new affiliate group leveraging the established LockBit brand, though specific organizational details remain undocumented by major security agencies. While detailed attack methodologies have not been publicly documented by CISA, FBI, or major security researchers, the group's targeting pattern across 157 victims suggests a broad-spectrum approach focusing on technology, manufacturing, healthcare, and transportation sectors primarily in the United States, Brazil, Germany, Italy, and Mexico. Due to the group's recent emergence in December 2025, there are no publicly documented notable campaigns or major incidents reported by established threat intelligence sources, though the victim count indicates active operations. The group appears to be currently active based on the recent first observation date, though comprehensive analysis from major security agencies has not yet been published given the short timeframe since emergence. The group has been linked to 320 public disclosures across our corpus. First observed on a leak site on December 7, 2025; most recent post July 11, 2026. The operation is currently active.

Timeline of this disclosure

April 29, 2026stllc.org listed by lockbit5on the group's public leak site

Other recent disclosures by lockbit5

lockbit5 has been linked to 320 public victims on Darkfield. A sample of the most recent:

See the full lockbit5 dossier →

Sector and geography

Geographically, stllc.org is reported in United States, a country with 3,115 ransomware disclosures in our corpus.

If your organisation is affected

A listing by lockbit5 means stllc.org 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 lockbit5'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.