Ransomware Tracker by ExposureDrift
Dashboard / Victims / Cook Medical LLC

Cook Medical LLC was listed on 14 August 2026 by the shinyhunters ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). shinyhunters listed 19 organizations that month and 162 in total.

  • Listed 98 days ago.
  • 1198 organizations were listed by all groups in August 2026, see the month.
  • 135 in Healthcare that month.
  • 411 in US that month.

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

Cook Medical LLC corporate emblem
Listed by shinyhunters Disclosed: 2026-08-14 05:59 UTC

Cook Medical LLC

cookmedical.com Healthcare US

Threat Group Post & Evidence

Listed by
Shinyhunters 162 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.

Customer data, employee data, and other internal corporate data was compromised. The Company engaged with us but made several paltry offers, did not want to pay what we asked for and decided they are okay with the data leak to happen instead of increasing their offer by a little, then we'd likely have accepted and this post would not have gone up. The Company failed to reach an agreement with us despite our incredible patience, all the chances and offers we made. They don't care. | Size: 182GB+ (compressed) | Updated: 14 August 2026 | SHA256: 8a87ba511f25f20a193f05a6578a620b02302c2075a6f2dff428d1f1a826ba63

Amounts as written

  • 182GB

Kinds of data mentioned

  • Customer or client data

    “Customer data, employee data, and other internal corporate data was compromised. The Company engaged…”

  • Employee and HR records

    “Customer data, employee data, and other internal corporate data was compromised. The Company engaged with us but made…”

  • Contracts and legal files

    “…accepted and this post would not have gone up. The Company failed to reach an agreement with us despite our incredible patience, all the chances and offers we made. They don't care.…”

Plain-English summary AI-written

The group says it holds customer data, employee data, and other internal corporate data.

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 Cook Medical (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 Cook Medical 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 Cook Medical 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, employee and hr records.

Within 30 days

  • Keep watching Cook Medical 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 Cook Medical

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: customer or client data.

Within 3 days

  • 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.
  • 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: 182GB. Treat group figures as unverified.
  • Check regulatory and stakeholder notification duties United States: state breach-notification laws apply; listed companies may also have SEC Form 8-K Item 1.05 duties for material incidents, and HIPAA applies to health data. Health data adds sector rules. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United States.

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.
  • Check shared suppliers and software List the suppliers and software you share with other Healthcare organizations and ask them whether they were affected. Why: shinyhunters listed 5 other Healthcare 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 cookmedical.com
Industry Vertical Healthcare
Country US
Enrichment Status ENRICHED

Listing severity score (heuristic)

72/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 30/30 pts
Healthcare and life sciences
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
62/100 • HIGH
Last Audited: 2026-11-14 16:17 UTC Passive Recon
Total Network Assets 21
6 hosts • 15 unique IPs
0 cloud-hosted • 4 SaaS
Subdomain Assets 6
Critical Panels 0 (VPN/Admin/SSO)
Non-Prod / UAT 0 Staging/Dev
SaaS Ecosystem 4 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 Proofpoint Enterprise Protection
DNS Authority Authoritative DNS (com)
Edge CDN / Shield None
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by shinyhunters

All →
WARNING
Technology 2026-09-30 00:02 UTC
Final statement re PSA
Technology 2026-09-24 08:44 UTC
Fresenius Medical Care
Healthcare 2026-09-22 22:42 UTC
PSA - READ THIS NOW
Financial Services 2026-09-22 18:51 UTC
Note to Cl0p-_
Unknown 2026-09-20 00:15 UTC
Qi****
Unknown 2026-09-17 01:28 UTC