Ransomware Tracker by ExposureDrift
Dashboard / Victims / Bosch

Bosch was listed on 13 July 2026 by the D1R ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). D1R listed 3 organizations that month and 3 in total.

  • Listed 128 days ago.
  • 948 organizations were listed by all groups in July 2026, see the month.
  • 164 in Manufacturing that month.
  • 58 in DE that month.

Updated 2026-11-14 15:52 UTC. Data: public leak-site listings. How we work.

Bosch corporate emblem
Listed by D1R Disclosed: 2026-07-13 11:33 UTC

Bosch

bosch.de Manufacturing DE

Threat Group Post & Evidence

Listed by
D1R 3 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.

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.

Again, thanks to database Synopsys provided us with After analyzing technical leaks by other groups and cross-referencing targets from TARGETLIST.txt A company access was found and in the archives, a $10,000 gem: Bosch CAN module implementation Now it is going for free for every engineer and car enthusiast, thanks to Synopsys providing us with neat roadmap to tech sector Sorry, Bosch, you got third-partied! Call the Synopsys CEO and thank them for letting us all know where the valuable data is!

Kinds of data mentioned

  • Databases and backups

    “Again, thanks to database Synopsys provided us with After analyzing technical leaks by other groups and cross-referencing…”

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 Bosch (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 Bosch 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 Bosch 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.
  • 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: databases and backups.

Within 30 days

  • Keep watching Bosch 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 Bosch

Within 3 days

  • 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.
  • 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. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Germany.
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 bosch.de
Industry Vertical Manufacturing
Country DE
Enrichment Status ENRICHED

Listing severity score (heuristic)

60/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 18/25 pts
Larger claim: gigabytes, or business or financial records named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence
60/100 • HIGH
Last Audited: 2026-11-14 16:27 UTC Passive Recon
Total Network Assets 3
2 hosts • 1 unique IPs
0 cloud-hosted • 3 SaaS
Subdomain Assets 2
Critical Panels 0 (VPN/Admin/SSO)
Non-Prod / UAT 0 Staging/Dev
SaaS Ecosystem 3 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade A+ (SPF/DMARC)
Open the full attack surface scan →
Is Your Organization Exposed?

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

Defense Telemetry

Passive DNS
Mail Gateway Microsoft 365 / Exchange Online
DNS Authority Authoritative DNS (de)
Edge CDN / Shield None
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by D1R

All →
ARM
Technology 2026-07-13 11:33 UTC
Synopsys
Technology 2026-07-13 11:32 UTC