Cyber & AI intelligence
Wasteland.
Briefs indexed3478
Issues33
Published Mondays07:30 CT
█ Ransomware DR-SCHNELL-RHYSIDA 2026-10-22

DR.SCHNELL GmbH & Co. KGaA: Rhysida Ransomware Leaks 2.52 TB Including Admin Credentials

"The Rhysida ransomware group has published what it presents as a full network dump from DR.SCHNELL GmbH & Co. KGaA, a German chemical manufacturer. According to threat-intelligence aggregator QPulse, the dump went live…"

The Rhysida ransomware group has published what it presents as a full network dump from DR.SCHNELL GmbH & Co. KGaA, a German chemical manufacturer. According to threat-intelligence aggregator QPulse, the dump went live on October 22, 2026 and contains 175,151 files totalling 2.52 TB. QPulse reports that it includes ERP backups, HR and payroll records for staff in three countries, the CEO's identity documents, TLS private keys and an Office 365 administrator password. One caveat matters for everything below. At the time of writing, every DR.SCHNELL-specific detail in this brief comes from a single source, QPulse, which has not been corroborated by a victim statement, a regulator filing or the established security press. DR.SCHNELL has not commented publicly in any of the material we reviewed. The details should be read as the leak-site claims as described by QPulse, not as facts the company has verified.

What Happened

QPulse says DR.SCHNELL was posted to Rhysida's leak site and discovered on October 22, 2026, and that the full data set was released the same day. QPulse rates the incident 95 out of 100 for severity. A full release usually means no ransom was paid, or that a negotiation deadline passed. Rhysida runs a double-extortion model: it steals data, encrypts systems, then threatens to publish (Dr. Web). It is not known whether DR.SCHNELL's systems were encrypted, when the intrusion began, or what ransom was demanded.

We also checked the Münnecke & Vollmers ransomware monitor. Its recent activity feed, which covers entries up to October 21, 2026, does not yet list DR.SCHNELL. That fits a same-day posting on October 22, but it means we found no second tracker confirming the listing.

For context, this comes weeks after Rhysida's most prominent German operation: the breach of two Berlin Senate departments, Urban Development/Building/Housing and Mobility/Transport/Climate/Environment. Accounts of that incident differ in the details:

Trackers also disagree on how many victims Rhysida has posted since 2023: 296 (Breachsense), 280 as of August 29 (Ransomware.live) and 265 as of February 2026 (Ransom-DB), as compiled by Breached.Company.

What Was Taken

According to QPulse, the 2.52 TB dump contains five categories of data:

No independent party has checked the contents, and QPulse does not say how many people are affected. This brief therefore gives no affected-individual count.

Why It Matters

The access material is what makes this dump especially dangerous, even more than the personal data. If QPulse's description is accurate, the leak creates four distinct risks:

The breach also fits a pattern. Rhysida has hit a German state government and now a German manufacturer within about two months. Dr. Web argues that the attack techniques used against Berlin "have long been hitting the Mittelstand," Germany's mid-sized industrial companies. Breached.Company's analysis of Rhysida's victims shows education (56) and healthcare (41) as its main sectors, but the DR.SCHNELL listing shows manufacturing is also a target.

The Attack Technique

How Rhysida got into DR.SCHNELL has not been reported, and nothing in the sources links this intrusion to a specific technique.

Rhysida's recent German activity offers a reasonable working assumption, but it is not evidence about this case:

Rhysida operates as ransomware-as-a-service, renting its tools to affiliates (Dr. Web). The affiliate responsible for DR.SCHNELL may therefore use different methods from the one behind the Berlin attack.

What Organizations Should Do

  1. Revoke and reissue exposed certificates immediately. Any organization whose private keys may have leaked should revoke the affected certificates, generate new key pairs, and watch Certificate Transparency logs for unauthorized issuance on its domains. Partners of DR.SCHNELL should be wary of unexpected certificate changes or lookalike hosts on dr-schnell.de.
  2. Assume every leaked credential is live. Rotate all Microsoft 365 admin and privileged accounts. Audit the Entra ID tenant for new admin roles, OAuth app consent grants, mailbox forwarding rules and federation changes. Enforce phishing-resistant MFA on all admin accounts.
  3. Revoke tax and signing certificates. Organizations holding Elster or similar authentication certificates should keep an inventory of where those files live. If exposed, revoke them through the issuing portal and watch for unauthorized filings.
  4. Tighten payment verification across the supply chain. Customers and suppliers of DR.SCHNELL should confirm bank-detail changes and payment requests through a separate, known channel. The leaked pricing, procurement and executive data makes invoice fraud highly plausible.
  5. Defend against ClickFix-style lures. Block or alert on PowerShell and Windows Terminal being launched from browser processes. Limit the Win+R run dialog through policy where practical. Train staff that no legitimate CAPTCHA asks them to paste commands.
  6. Get credentials out of file shares. Search file servers and SharePoint for password lists, private keys and certificate files, and move them into a managed secrets vault. Watch domain controllers closely: in Berlin, suspicious domain-controller activity was the first sign of the breach.

Sources: Rhysida Ransomware Group Publishes 2.52 TB Data Dump from DR.SCHNEL... | xHealth Data Breach Affects 118,000 Individuals | Cyberattack in Berlin: 1.4 million files on the dark web | Ransomware-Monitor: Who's hacked? | BSI explains first attack vector on Berlin authorities - Cybercrime... | Rhysida Ransomware Tracker: 296 Victims Mapped Breached.Company | Berliner Datenleck: Was Firmen daraus lernen müssen? | CenterPoint reports customer data breach