Home All Victims motorenmaier gmbh

motorenmaier gmbh

qilin

This record tracks a ransomware attack claimed by the qilin group against motorenmaier gmbh. It collects the publicly disclosed attack details — sector, location and timeline — as published on the operator's leak site and indexed by Breach House.

Window Zero

EXPOSURE GAP

Window Zero is the time the breach stayed in the open before anyone said so — the gap between when the attack was first discovered on the operator's leak site (t1) and when it was publicly disclosed (t2). The wider this window, the longer victims, staff and customers were exposed with no warning.

21days open
t1 · Published t2 · Pending
Aug 15, 2026Not disclosed yet
Country
Discovered
2026-08-16
Published
August 15, 2026
Leak Status
pending
checked 2026-09-05
Disclosed / Notified
Not disclosed yet
Victim ID
mTPpr5OYTkPP

Attack Summary

N/A

Leak Screenshots

1 CAPTURED

Captured directly from the operator's leak site by our collector, last checked 2026-09-05. Verdict evidence: [M1] No download links, torrent, mirrors, part files, or published labels visible.

Capture history — 5 day(s) tracked. Content is locked.

2026-09-05
2026-09-04
2026-09-04
2026-09-03
2026-09-02
Showing the latest capture only
Unlock the 5 captures already taken.

Dark Web Exposure

Findings for motorenmaier.de — indexed by HaveIBeenRansom.
1
found in Infostealer logs
5
found in Traditional breaches
2
found in Ransomware leaks
VerificationsIO_BF.7z.011
Kedr | Forum 🪾 · breach
••• emails
Q railing
play · ransomware
••• emails
2844Breaches_BF.7z
B F R e p o V 3 F i l e s · breach
••• emails
OnlinerSpambot_BF.7z
B F R e p o V 3 F i l e s · breach
••• emails
Collection#3.zip
DBs w MTDT · breach
••• emails
Leak volumes are locked
Sign in to reveal how many records each source exposed.
Want the complete picture — passwords, machines, full leak files? It's all searchable on HaveIBeenRansom.
Search this victim →
Visit Website Original Post View Group: qilin
Legal Disclaimer: This ransomware victim record reflects information published on the operator's leak site. Breach.house only records what the operators themselves publish in the open. We take screenshots of their public pages and keep the proof material they post there, so that a listing can be verified and its status tracked over time. We do not purchase data, we do not solicit or encourage its publication, we do not access any private system, and we do not alter anything we record. Nothing is offered for download here, and detailed content is not published on this page or anywhere else on the public site: access to it is restricted to vetted customers under contract, for incident response, due diligence and cyber-resilience work. Breach.house is not affiliated with, and does not act on behalf of, the operators who publish this material. If you represent an organisation or individual named here and want a record reviewed or removed, contact us and we will act on it.