Was Wilhelm Kühne hit by ransomware?

Wilhelm Kühne was listed by the lamashtu 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 lamashtu ransomware group?

lamashtu 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 Wilhelm Kühne breach?

lamashtu published data attributed to Wilhelm Kühne. Darkfield captured the leak post and a screenshot of the listing.

Ransomware victim disclosure

← All victims

Wilhelm Kühne

Claimed by Lamashtu · listed 7 hours ago

Today

Age

since listed · data leaked

Status timeline

ListedSep 30, 2026
Data leakeddate unknown

At a glance

Group: Lamashtu
Status: Data leaked
Country: Germany
Sector: Manufacturing
Listed on leak site: Sep 30, 2026

About the victim

AI dossier — public-source company profile

Wilhelm Kühne is a German facility services company founded in 1950, specializing in professional cleaning and building maintenance. The company serves offices, schools, healthcare facilities, and commercial properties across Germany.

Industry: Facility Services & Professional Cleaning
Address: Oldenburg, Germany
Founded: 1950

Attack summary

Severity: low — The leak post contains only a generic announcement with no proof files, screenshots, or specific data inventory disclosed. No operational disruption is claimed. The post reads as a listing/announcement without substantive evidence of exfiltration or encryption.

The lamashtu group claims to have compromised Wilhelm Kühne. The leak post does not specify whether data was exfiltrated, encrypted, or both, nor does it detail what specific data categories are at stake.

low

What the group claims

Wilhelm Kühne is a German facility services company specializing in professional cleaning and building maintenance. Founded in 1950, it serves offices, schools, healthcare facilities, and commercial properties.

Sources

Source

Indexed 7 hours 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 lamashtu

Based on the limited available information, Lamashtu is an emerging ransomware group that was first observed in April 2026, appearing to be financially motivated based on their operational patterns. The group's origin and potential affiliations remain unclear due to their recent emergence and limited public documentation by major threat intelligence organizations. Lamashtu's attack methodology and specific technical capabilities have not been extensively documented by established security researchers, though their targeting patterns suggest they employ standard ransomware deployment techniques across multiple industry verticals. The group has conducted at least 8 confirmed attacks, demonstrating a geographically diverse targeting approach with victims identified in France, Italy, the United States, Singapore, and Malaysia, while focusing primarily on business services, manufacturing, transportation and logistics, hospitality and tourism, and energy sectors. Given the group's recent first observation in April 2026 and limited public threat intelligence reporting from established sources like CISA, FBI, or major security firms, Lamashtu appears to represent a newly active threat actor whose current operational status and long-term capabilities require further monitoring and analysis. The group has been linked to 44 public disclosures across our corpus. First observed on a leak site on April 13, 2026; most recent post September 30, 2026. The operation is currently active.

Timeline of this disclosure

September 30, 2026Wilhelm Kühne listed by lamashtu on the group's public leak site

Other recent disclosures by lamashtu

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

See the full lamashtu dossier →

Sector and geography

This disclosure adds to ransomware activity in the Manufacturing sector, which has 3,696 disclosures indexed across all operators we track. Geographically, Wilhelm Kühne is reported in Germany, a country with 393 ransomware disclosures in our corpus.

If your organisation is affected

A listing by lamashtu means Wilhelm Kühne 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 lamashtu'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.