bayer.com

This domain scores better than 22% of the 226 Healthcare organisations we track (cohort median 79). The sample is seeded from public incident data, not a random cross-section of the sector.

Posture summary

Ransomware leak-site listings (1)

This domain is named on the public leak site of a ransomware group. A leak-site post is a claim published by the group — not a verified fact, and not a statement by this organization. Groups list victims who did not pay, overstate what they hold, and occasionally name the wrong company. What is certain is that the listing itself is public.

Leak-site postings are collected here from 2026-07-30 onwards; an earlier listing would not appear above.

Source: Ransomware.live

Public attack surface (72 hostnames in Certificate Transparency)

Hostnames this organization published in public TLS certificates. Passive OSINT — nothing was scanned; a wildcard certificate is in use, so the real footprint may be larger.

The hostname inventory — which forgotten hosts exist and where — is part of the complete audit for this domain.

Lookalike domains (40 registered of 78 checked, 5 serving no website)

Registered permutations of this domain. Existence is a fact, not an accusation — ownership and intent are not assessed. Those able to receive mail are the ones usable for invoice fraud and phishing. The Risk score (0–100) is a published formula weighing mail capability, registration age, spelling and phishing-feed hits, reduced when a name looks brand-owned (same registrar/nameservers) or merely parked.

37 further registered lookalike(s), 30 of them able to receive mail. The full list, with mail capability for each, is part of the complete audit.

Recommendations

• highEnforce DMARC

  No enforcing DMARC policy was observed. Publish a DMARC record and move to p=quarantine then p=reject to reduce spoofing.

• mediumEnable DNSSEC

  DNSSEC signing was not detected for this domain.

• criticalTreat data published on a leak site as disclosed

  This domain is named on Black X's public leak site on 2026-10-09. A leak-site post is a claim published by the group, not a verified fact — but the post itself is public, and if it is accurate the data is already out. Confirm the claim, then work from the assumption of disclosure: rotate every credential that touched the affected systems, invalidate active sessions, and check your notification duties under GDPR Art. 33/34.

• criticalReset credentials seen in infostealer logs

  Public infostealer telemetry associates 39 employee credential set(s) with this domain — passwords captured from infected devices, which bypass password policy and often session-hijack past MFA. The most recent dates from 2026-04-25. Most commonly RedLine. Force a reset for the affected services, invalidate active sessions, and check the devices themselves.

• mediumReview third-party credential exposure

  603 credential set(s) for third-party services used by this domain appear in the same telemetry. Supplier and SaaS accounts are a common lateral path.

• mediumStrengthen password requirements

  63% of the exposed employee passwords analysed rate as weak or very weak. Raise minimum length and screen new passwords against breach lists.

• highMonitor lookalike domains

  30 registered lookalike domain(s) can receive mail, which is what makes them usable for invoice fraud and credential phishing. 4 of those serve no website at all but can already receive mail, so a reply sent to them would be delivered although nothing is visible in a browser. With no website there is nothing to inspect, so watch for DNS or web changes rather than treating them as harmless. Monitor them and consider defensive registrations.

• mediumReview the public subdomain footprint

  72 hostnames for this domain appear in public Certificate Transparency logs. Retire forgotten hosts — stale subdomains are a common entry point and a takeover risk.