Rumah Sakit Universitas Indonesia (RSUI) was listed on 20 July 2026 by the nova ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). nova listed 21 organizations that month and 177 in total.
- Listed 121 days ago.
- 948 organizations were listed by all groups in July 2026, see the month.
- 90 in Healthcare that month.
- 6 in ID that month.
Updated 2026-11-18 11:12 UTC. Data: public leak-site listings. How we work.
Rumah Sakit Universitas Indonesia (RSUI)
Threat Group Post & Evidence
- Listed by
- Nova 177 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.
Rumah Sakit Universitas Indonesia (RSUI) is the teaching hospital of the University of Indonesia, providing advanced medical care, education, and clinical research in Indonesia - medical data from drive at risk, Nova Provide tree and samples from stolen data to the company when its get in touch with support department.
Kinds of data mentioned
-
Medical or patient records
“…the teaching hospital of the University of Indonesia, providing advanced medical care, education, and clinical research in Indonesia - medical data from drive at risk, Nova…”
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 Rumah Sakit Universitas Indonesia (RSUI) (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 Rumah Sakit Universitas Indonesia (RSUI) 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 Rumah Sakit Universitas Indonesia (RSUI) 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.
- If you share health data with them You may be the data controller, with notification duties of your own. Ask counsel which health-privacy rules apply to you. Why: The post names medical or health data.
Within 30 days
- Keep watching Rumah Sakit Universitas Indonesia (RSUI) 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 Rumah Sakit Universitas Indonesia (RSUI)
Within 3 days
- Handle health-data exposure Work out which patient or health records are in scope, apply the health-privacy notification rules that cover them, and prepare patient communications. Why: The post names: medical or patient records.
- 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
Listing severity score (heuristic)
81/100 • CRITICALA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceNo 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.
Open the full attack surface scan →Run a free passive scan on your own domain to see what an attacker can see from the outside.