Ransomware Tracker by ExposureDrift
Dashboard / Victims / Intermed Hospital Mongolia

Intermed Hospital Mongolia was listed on 30 October 2024 by the spacebears ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). spacebears listed 1 organizations that month and 163 in total.

  • Listed 751 days ago.
  • 543 organizations were listed by all groups in October 2024, see the month.
  • 61 in Healthcare that month.

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

Intermed Hospital Mongolia corporate emblem
Listed by spacebears Disclosed: 2024-11-08 05:24 UTC

Intermed Hospital Mongolia

intermed.mn Healthcare MN

Threat Group Post & Evidence

Listed by
Spacebears 163 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.

Largest medical center in Mongolia: - Databases,- Personal data - Other valuable information- dcm, xls, jpg, txt... ect. http://www.intermed.mn

Plain-English summary AI-written

The group says it holds databases, personal data, and other valuable information from Mongolia’s largest medical center.

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 Intermed Hospital Mongolia (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 Intermed Hospital Mongolia 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 Intermed Hospital Mongolia 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 Intermed Hospital Mongolia 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 Intermed Hospital Mongolia

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.
  • Lock down exposed admin, VPN and SSO panels Restrict by IP allow-list or a zero-trust proxy and require MFA. Why: A passive scan found 1 critical panel(s) reachable from the internet.
  • Remove dangling DNS records Delete or re-point records that allow subdomain takeover. Why: A passive scan found 1 dangling subdomain(s).
  • Retire staging and dev exposure Take non-production hosts off the internet or behind authentication, and rotate any secrets they held. Why: A passive scan found 1 non-production host(s) that are public.
  • 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.

Within 30 days

  • Check shared suppliers and software List the suppliers and software you share with other Healthcare organizations and ask them whether they were affected. Why: spacebears listed 3 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 intermed.mn
Industry Vertical Healthcare
Country MN
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
100/100 • CRITICAL
Last Audited: 2026-11-14 18:36 UTC Passive Recon
Total Network Assets 27
7 hosts • 20 unique IPs
0 cloud-hosted • 1 SaaS
Subdomain Assets 7
Critical Panels 1 (VPN/Admin/SSO)
Non-Prod / UAT 1 Staging/Dev
SaaS Ecosystem 1 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade C (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 Cloudflare Managed DNS
Edge CDN / Shield Cloudflare CDN / DDoS Shield
SPF Record Configured
DMARC Policy Missing
Public DNS records only • no port scanning

More Claims by spacebears

All →
SDJ Design Engineering Limited
Manufacturing 2026-11-20 03:55 UTC
Rise | A Community Service Partnership
Retail & E-Commerce 2026-11-20 03:54 UTC
Epoch Residential
Hospitality 2026-11-20 03:53 UTC
SGLA
Professional Services 2026-10-22 07:02 UTC
Alma Center Servizi Medicali S.r.l.
Healthcare 2026-10-15 06:05 UTC