Was BAVACAI hit by ransomware?

BAVACAI was listed by the MEDUSA LOCKER (aka BAVACAI 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 MEDUSA LOCKER (aka BAVACAI ransomware group?

MEDUSA LOCKER (aka BAVACAI 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 BAVACAI breach?

MEDUSA LOCKER (aka BAVACAI published data attributed to BAVACAI, around 8050 files records. Darkfield captured the leak post and a screenshot of the listing.

Ransomware victim disclosure

← All victims

BAVACAI

Claimed by MEDUSA LOCKER (aka BAVACAI · listed 3 months ago

8050 files

Records

Age

since listed · data leaked

Status timeline

ListedMay 31, 2026
Data leakeddate unknown

At a glance

Group: MEDUSA LOCKER (aka BAVACAI
Status: Data leaked
Country: Germany
Sector: Legal Services
Listed on leak site: May 31, 2026
Records: 8050 files

About the victim

AI dossier — public-source company profile

BAVACAI is a German legal services firm operating in the Hesse region. The company handles civil litigation cases (GBA proceedings) across multiple jurisdictions including Darmstadt, Langen, and surrounding areas.

Industry: Legal Services

Attack summary

Severity: high — Confirmed exfiltration of 8,050 files containing sensitive legal case information, client identity data, and court proceedings. Legal privilege violations and significant personal data exposure of litigation parties.

MEDUSA LOCKER claims to have encrypted BAVACAI's systems and exfiltrated approximately 8,050 files. The group has published a sample of case files and legal documents as proof of access.

high

Data the group says was taken

AI dossier — extracted from the leak post

Civil litigation case files (GBA proceedings)
Client names and case details
Court filings and legal documents
Client correspondence

The group's post references roughly 10 proof files.

What the group claims

Victim identified as 'bapamai' on the leak site. Leaked files appear to be legal documents (GBA - Grundbuchamtsachen/land registry or court documents) related to various German locations including Gundernhausen-Darmstadt, Schwanheim, Bensheim, Ober-Roden, suggesting a German legal or notary firm.

The leak post

captured from the group's site

⚠ Demo access — showing up to 10 files per folder. Full data will be available after publication.   
 |  
|  |  
|  [(006-2023 N) GBA v. Gundernhausen-Darmstadt Blatt 2149 Wohlgemuth.doc](http://t33zoj4qwv455fog7qnb2azi5xcdxkixughmmduzbw2rtdgryqfbh6id.onion/company/bapamai/preview/\(006-2023%20N\)%20GBA%20v.%20Gundernhausen-Darmstadt%20Blatt%202149%20Wohlgemuth.doc)  |  
|  [(007-2023 N) Friedrich, Ubegl.mit Weiterleitung.doc](http://t33zoj4qwv455fog7qnb2azi5xcdxkixughmmduzbw2rtdgryqfbh6id.onion/company/bapamai/preview/\(007-2023%20N\)%20Friedrich,%20Ubegl.mit%20Weiterleitung.doc)  |  
|  [(007-2024 N) GBA v. Ober-Roden, AG Langen Hessen, Blätter 6142 u. 6214 Förster-R-.doc](http://t33zoj4qwv455fog7qnb2azi5xcdxkixughmmduzbw2rtdgryqfbh6id.onion/company/bapamai/preview/\(007-2024%20N\)%20GBA%20v.%20Ober-Roden,%20AG%20Langen%20Hessen,%20Bl%C3%A4tter%206142%20u.%206214%20F%C3%B6rster-R-.doc)  |  
 |  
 |  
|  [(009-2022 N) GBA Kusche (Rappe) -.doc](http://t33zoj4qwv455fog7qnb2azi5xcdxkixughmmduzbw2rtdgryqfbh6id.onion/company/bapamai/preview/\(009-2022%20N\)%20GBA%20Kusche%20\(Rappe\)%20-.doc)  |  
 |  
|  [(011-2023 N) GBA v. Schwanheim Blatt 6258 (Werkmann).doc](http://t33zoj4qwv455fo…

Data the group says was taken

legal documents
court documents

Screenshot of the leak post

Sources

Leak posthttp://t33zoj4qwv455fog7qnb2azi5xcdxkixughmmduzbw2rtdgryqfbh6id.onion/company/bapamai/

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 MEDUSA LOCKER (aka BAVACAI

MedusaLocker (also identified under the alias BAVACAI) is a ransomware group first observed in May 2026, operating with a primary financial motivation consistent with contemporary cybercriminal ransomware operations. Due to the extremely limited public documentation available at this time — with only a single known victim on record and a very recent emergence date — comprehensive attribution, origin, and affiliation details cannot be responsibly stated without risking speculation beyond what is publicly confirmed by authoritative sources such as CISA, the FBI, or Mandiant. It should be noted that a separate, well-documented ransomware family also named MedusaLocker has been publicly tracked since 2019 and operates as a Ransomware-as-a-Service model; whether this BAVACAI-aliased entity represents a rebrand, offshoot, or entirely distinct group sharing the name is not confirmed by available public intelligence. Given the single known victim and the May 2026 first-observed date, this group should be considered an emerging or early-stage threat with minimal public threat intelligence footprint, and analysts are advised to treat any further characterization as preliminary pending additional reporting from law enforcement or the security research community. Monitoring for additional victim disclosures, leak site activity, and technical indicators will be necessary to develop a more complete operational profile. The group has been linked to 7 public disclosures across our corpus. First observed on a leak site on May 15, 2026; most recent post June 4, 2026. The operation is currently active.

Timeline of this disclosure

May 31, 2026BAVACAI listed by MEDUSA LOCKER (aka BAVACAIon the group's public leak site

Records: 8050 files

Other recent disclosures by MEDUSA LOCKER (aka BAVACAI

MEDUSA LOCKER (aka BAVACAI has been linked to 7 public victims on Darkfield. A sample of the most recent:

See the full MEDUSA LOCKER (aka BAVACAI dossier →

Sector and geography

This disclosure adds to ransomware activity in the Legal Services sector. Geographically, BAVACAI is reported in Germany, a country with 393 ransomware disclosures in our corpus.

If your organisation is affected

A listing by MEDUSA LOCKER (aka BAVACAI means BAVACAI 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 MEDUSA LOCKER (aka BAVACAI'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.