Ransomware Tracker by ExposureDrift
Dashboard / Victims / Kochs GmbH

Kochs GmbH was listed on 22 June 2026 by the aurora ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). aurora listed 11 organizations that month and 61 in total.

  • Listed 150 days ago.
  • 708 organizations were listed by all groups in June 2026, see the month.
  • 121 in Manufacturing that month.
  • 48 in DE that month.

Updated 2026-11-19 05:42 UTC. Data: public leak-site listings. How we work.

Kochs GmbH corporate emblem
Listed by aurora Disclosed: 2026-06-22 09:50 UTC

Kochs GmbH

Manufacturing DE

Threat Group Post & Evidence

Listed by
Aurora 61 listings in total

The listing states no data size and no ransom demand.

No capture of the original post

We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.

The group's leak-site address is on paid plans

Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.

What the group says it holds

Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.

[manufacturer] *** — a family-owned German manufacturer of windows, doors, and aluminium façade systems headquartered in Herzogenrath, Nordrhein-Westfalen, with ~240 employees across Germany, the Netherlands, and Hungary. The exposed material includes: 22 GB of payroll database backups (7 MSSQL .bak files, 2016–2023) — every employee's salary, bank IBAN, tax class, social insurance number, pension contributions, and wage garnishments. 2.3 GB of DATEV payroll records (through May 2026) — individual named salary documents, garnishment data, company car records for all three entities. 7 Active Directory passwords in plaintext batch scripts — including both Managing Directors, with one MD's credentials spanning three separate AD domains. 28+ proprietary application source code repositories — WinPro ERP, Apertum CRM, MES integrations, production viewers, time-tracking, and rack-management sys…
Show the full post (1597 characters)

[manufacturer] *** — a family-owned German manufacturer of windows, doors, and aluminium façade systems headquartered in Herzogenrath, Nordrhein-Westfalen, with ~240 employees across Germany, the Netherlands, and Hungary. The exposed material includes: 22 GB of payroll database backups (7 MSSQL .bak files, 2016–2023) — every employee's salary, bank IBAN, tax class, social insurance number, pension contributions, and wage garnishments. 2.3 GB of DATEV payroll records (through May 2026) — individual named salary documents, garnishment data, company car records for all three entities. 7 Active Directory passwords in plaintext batch scripts — including both Managing Directors, with one MD's credentials spanning three separate AD domains. 28+ proprietary application source code repositories — WinPro ERP, Apertum CRM, MES integrations, production viewers, time-tracking, and rack-management systems. Each one hardcodes its database credentials. SSL/TLS private keys for kochs.de (2021–2026) — enabling domain impersonation and man-in-the-middle attacks. 77 VPN pre-shared keys from the LANCOM gateway configuration — the complete remote-access roster since 2018. Managing Director's MRI and X-ray scans — brain and spine medical imaging, GDPR Art. 9 special category health data. 16 named employee disciplinary records, 11 driver's license scans, attorney-client privileged litigation files from two active employment lawsuits. Complete financial records — 2024 annual accounts, P&L, balance sheets, SFirm banking database, Syska ProFI general ledger, cost accounting through December 2024.

Amounts as written

  • 240 employees
  • 22 GB
  • 2.3 GB

Kinds of data mentioned

  • Tax records

    “…(7 MSSQL .bak files, 2016–2023) — every employee's salary, bank IBAN, tax class, social insurance number, pension contributions, and wage garnishments. 2.3 GB of DATEV…”

  • Accounting and ledgers

    “…accounts, P&L, balance sheets, SFirm banking database, Syska ProFI general ledger, cost accounting through December 2024.”

  • Banking and wire details

    “…backups (7 MSSQL .bak files, 2016–2023) — every employee's salary, bank IBAN, tax class, social insurance number, pension contributions, and wage garnishments. 2.3 GB…”

  • Payroll and salaries

    “The exposed material includes: 22 GB of payroll database backups (7 MSSQL .bak files, 2016–2023) — every employee's salary, bank IBAN, tax…”

  • Identity documents

    “…special category health data. 16 named employee disciplinary records, 11 driver's license scans, attorney-client privileged litigation files from two active employment lawsuits. Complete…”

  • Passwords and credentials

    “…garnishment data, company car records for all three entities. 7 Active Directory passwords in plaintext batch scripts — including both Managing Directors, with one MD's credentials…”

  • Medical or patient records

    “…since 2018. Managing Director's MRI and X-ray scans — brain and spine medical imaging, GDPR Art. 9 special category health data. 16 named employee disciplinary records,…”

  • Customer or client data

    “…named employee disciplinary records, 11 driver's license scans, attorney-client privileged litigation files from two active employment lawsuits. Complete financial records…”

  • Employee and HR records

    “…GB of payroll database backups (7 MSSQL .bak files, 2016–2023) — every employee's salary, bank IBAN, tax class, social insurance number, pension contributions, and wage garnishments.…”

  • Contracts and legal files

    “…disciplinary records, 11 driver's license scans, attorney-client privileged litigation files from two active employment lawsuits. Complete financial records — 2024 annual accounts,…”

  • Source code and designs

    “…credentials spanning three separate AD domains. 28+ proprietary application source code repositories — WinPro ERP, Apertum CRM, MES integrations, production viewers, time-tracking,…”

  • Databases and backups

    “The exposed material includes: 22 GB of payroll database backups (7 MSSQL .bak files, 2016–2023) — every employee's salary, bank IBAN, tax class, social…”

Plain-English summary AI-written

The group says it has payroll backups and records containing employee salary, banking, tax, social insurance, pension, garnishment, and company car information, as well as plaintext Active Directory passwords.

Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.

What to do about this listing

Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.

If you work with Kochs (customer, supplier or partner)

Within 3 days

  • Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
  • Ask Kochs directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
  • Review what Kochs can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
  • Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data, passwords and credentials, identity documents, employee and hr records.
  • Verify payment-detail changes by phone Confirm any change to bank details or any urgent invoice with a number you already hold, not one in the message. Why: The post names: banking and wire details, payroll and salaries, accounting and ledgers, tax records.
  • Check software and integrations you take from them If you run their software or call their API, check that updates come through the usual channel and rotate the keys and tokens you hold for it. Why: The post names: source code and designs, databases and backups.
  • If you share health data with them You may be the data controller, with notification duties of your own. Ask counsel which health-privacy rules apply to you. Why: The post names medical or health data.

Within 30 days

  • Keep watching Kochs A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Kochs

First 24 hours

  • Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: passwords and credentials, identity documents, customer or client data, payroll and salaries.
  • Protect payments Tell your bank, verify any change to supplier or payroll bank details by calling a known number, and watch for invoice-fraud emails that use real names and amounts. Why: The post names: banking and wire details, payroll and salaries, accounting and ledgers.

Within 3 days

  • Handle health-data exposure Work out which patient or health records are in scope, apply the health-privacy notification rules that cover them, and prepare patient communications. Why: The post names: medical or patient records.
  • Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: employee and hr records, identity documents.
  • Rotate secrets and signing keys Assume secrets in repositories are exposed: rotate API keys, tokens and code-signing keys, and review build and release systems for unexpected changes. Why: The post names: source code and designs.
  • Rotate database and cloud access Rotate database and cloud-storage keys, review public bucket and snapshot sharing, turn on object-level audit logging and keep backup encryption keys separate. Why: The post names: databases and backups.
  • Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 240 employees, 22 GB, 2.3 GB. Treat group figures as unverified.
  • Check regulatory and stakeholder notification duties EU/EEA: GDPR Art. 33 and 34 require notifying the supervisory authority within 72 hours of becoming aware of a personal data breach, and affected people where risk is high. Health data adds sector rules. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Germany.

Within 30 days

  • Review privileged and contract material Ask counsel which contracts and privileged files are named, and whether client or partner confidentiality terms oblige you to tell them. Why: The post names: contracts and legal files.
  • Watch for tax-filing fraud Tell your tax advisers and, where available, tax authorities so fraudulent filings made with exposed identifiers can be caught early. Why: The post names: tax records.
  • Check shared suppliers and software List the suppliers and software you share with other Manufacturing organizations and ask them whether they were affected. Why: aurora listed 10 other Manufacturing organization(s) in the last 90 days.
General readiness for any ransomware claim (not about this listing)
  • Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
  • Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
  • Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.

Listing details

Resolved Domain Not stated
Industry Vertical Manufacturing
Country DE
Enrichment Status ENRICHED

Listing severity score (heuristic)

69/100 • ELEVATED

A heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.

1. Sector Criticality 20/30 pts
Industrial manufacturing
2. Group tier 10/25 pts
Tier 3: all other groups
3. Data Volume & PII Scope 25/25 pts
Largest claim: a terabyte or more, or regulated data named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence

No scan has been run for this domain yet, so there are no figures to show. Running one is passive: it reads public DNS and certificate records only.

Launch Attack Surface Recon →
Is Your Organization Exposed?

Run a free passive scan on your own domain to see what an attacker can see from the outside.

More Claims by aurora

All →
Boutinot Limited
Agriculture and Food Production 2026-11-19 14:06 UTC
Boulart Inc.
Healthcare 2026-11-19 10:37 UTC
Mor Group
Professional Services 2026-11-19 10:37 UTC
Sice Previt S.p.A.
Manufacturing 2026-11-17 09:09 UTC
Johnson Development Corp.
Financial Services 2026-11-09 12:44 UTC
Rapid Manufacturing
Manufacturing 2026-10-30 15:03 UTC