Ransomware Tracker by ExposureDrift
Dashboard / Victims / ****cr*nem*ds.c*m

****cr*nem*ds.c*m was listed on 24 January 2026 by the devman ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). devman listed 30 organizations that month and 184 in total.

  • Listed 298 days ago.
  • 695 organizations were listed by all groups in January 2026, see the month.
  • 49 in Healthcare that month.
  • 7 in SJ that month.

Updated 2026-11-13 18:12 UTC. Data: public leak-site listings. How we work.

****cr*nem*ds.c*m corporate emblem
Listed by devman Disclosed Date: Not Applicable (Identity Undisclosed)

****cr*nem*ds.c*m

Healthcare SJ

Threat Group Post & Evidence

Listed by
Devman 184 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.

Patient data, medical cards clinic records

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 ****cr*nem*ds.c*m (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 ****cr*nem*ds.c*m 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 ****cr*nem*ds.c*m 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.

Within 30 days

  • Keep watching ****cr*nem*ds.c*m 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 ****cr*nem*ds.c*m

Within 3 days

  • Find out what was actually taken The post names no specific kind of data, so no data-specific steps are shown. Check the group's own post and your logs to learn what is claimed and what is real. Why: The listing text names no data types.
  • Check regulatory and stakeholder notification duties Health data adds sector rules. This is general guidance, not legal advice: confirm current rules with counsel. Why: The listing or sector points to health data.
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 Healthcare
Country SJ
Enrichment Status ENRICHED

Listing severity score (heuristic)

81/100 • CRITICAL

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 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 devman

All →
Crystal Coast Pain Management
Healthcare 2026-02-04 01:24 UTC
ENCOMPASS-INC
Financial Services 2026-02-02 23:34 UTC
woodwardoralsurgery.com
Healthcare 2026-01-30 20:33 UTC
wjnklaw.com
Professional Services 2026-01-30 17:34 UTC
consultaegis.com
Government & Defense 2026-01-29 11:31 UTC
zallc.org
Financial Services 2026-01-29 11:29 UTC