Was vgrn.de hit by ransomware?

vgrn.de was listed by the lockbit5 ransomware operation (Germany), 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 vgrn.de breach?

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

Ransomware victim disclosure

← All victims

Verbandsgemeinde Rhein-Nahe

listed as vgrn.de · Claimed by Lockbit5 · listed 1 day ago

Age

since listed · data leaked

Status timeline

ListedAug 16, 2026
Data leakeddate unknown

At a glance

Group: Lockbit5
Status: Data leaked
Country: Germany
Sector: Energy & Utilities
Listed on leak site: Aug 16, 2026

About the victim

AI dossier — public-source company profile

Verbandsgemeinde Rhein-Nahe is a municipal administrative body (Verbandsgemeinde) in Germany, serving as a collective local government entity for multiple communes in the Rhineland-Palatinate region.

Industry: Local Government Administration

Attack summary

Severity: medium — Government entity targeted with data published status confirmed, but no proof files, data inventory details, or specific exfiltrated content described in the available excerpt. Operational impact and data sensitivity cannot be assessed from the limited information provided.

LockBit5 claims to have conducted an attack on Verbandsgemeinde Rhein-Nahe. No specific details are provided regarding whether data was encrypted, exfiltrated, or both, nor are specific data types disclosed in the available post excerpt.

medium

What the group claims

Verbandsgemeinde Rhein-Nahe is a company that operates in the Government industry.

Sources

Victim sitevgrn.de
Leak posthttp://lockbitapt67g6rwzjbcxnww5efpg4qok6vpfeth7wx3okj52ks4wtad.onion/post/56802155da7ca00b8af929049da5fcf1

Source

Indexed 1 day 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 335 public disclosures across our corpus. First observed on a leak site on December 7, 2025; most recent post August 16, 2026. The operation is currently active.

Timeline of this disclosure

August 16, 2026vgrn.de listed by lockbit5on the group's public leak site

Other recent disclosures by lockbit5

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

See the full lockbit5 dossier →

Sector and geography

This disclosure adds to ransomware activity in the Energy & Utilities sector, which has 168 disclosures indexed across all operators we track. Geographically, vgrn.de is reported in Germany, a country with 383 ransomware disclosures in our corpus.

If your organisation is affected

A listing by lockbit5 means vgrn.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 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.