Valisana was listed on 20 July 2024 by the ransomhouse ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). ransomhouse listed 11 organizations that month and 214 in total.
- Listed 853 days ago.
- 430 organizations were listed by all groups in July 2024, see the month.
- 59 in Healthcare that month.
- 5 in BE that month.
Updated 2026-11-19 06:29 UTC. Data: public leak-site listings. How we work.
Threat Group Post & Evidence
- Listed by
- Ransomhouse 214 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.
Valisana! Verantwoordelijkheid is de morele nood om aan onze eigen handelingen of die van anderen te beantwoorden. Bij Valisana leggen we de nadruk op het belang van ieders verantwoordelijkheid, maar eveneens op gedeelde verantwoordelijkheid. Dit houdt betrokkenheid, zelfstandigheid, erkenning van de anderen en samenwerking in. Wij streven naar wederzijds respect binnen de therapeutische relatie alsook respect voor zichzelf en oprechtheid en duidelijkheid van het project. Respect is een institutionele waarde die zowel patiënten als professionelen betreft. Wij willen openstaan voor verscheidenheid aan culturen, innovaties en leerprocessen. Wij streven naar zorg op maat van de patiënt anders dan standaardoplossingen. Elke patiënt, zonder uitzondering of onderscheid, moet in functie van zijn behoeften op een rechtvaardige en neutrale wijze behandeld worden. Hetzelfde is van toepassing voor …
Show the full post (1299 characters)
Valisana! Verantwoordelijkheid is de morele nood om aan onze eigen handelingen of die van anderen te beantwoorden. Bij Valisana leggen we de nadruk op het belang van ieders verantwoordelijkheid, maar eveneens op gedeelde verantwoordelijkheid. Dit houdt betrokkenheid, zelfstandigheid, erkenning van de anderen en samenwerking in. Wij streven naar wederzijds respect binnen de therapeutische relatie alsook respect voor zichzelf en oprechtheid en duidelijkheid van het project. Respect is een institutionele waarde die zowel patiënten als professionelen betreft. Wij willen openstaan voor verscheidenheid aan culturen, innovaties en leerprocessen. Wij streven naar zorg op maat van de patiënt anders dan standaardoplossingen. Elke patiënt, zonder uitzondering of onderscheid, moet in functie van zijn behoeften op een rechtvaardige en neutrale wijze behandeld worden. Hetzelfde is van toepassing voor de teamleden. Wij moedigen iedereen aan om rechtuit te spreken en werken aan een open feedback cultuur. Wij streven met onze collega’s en patiënten naar een therapeutisch gerichte samenwerking zonder vooroordeel of a priori. We streven naar erkenning en integratie in al onze reflecties, acties en beslissingen, zowel de eigen inbreng van elk teamlid als de specificiteit van elk van onze patiënten.
Plain-English summary AI-written
The group says the text describes Valisana’s values, including responsibility, shared responsibility, respect, openness to diversity and care tailored to patients.
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 Valisana (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 Valisana 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 Valisana 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 Valisana 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 Valisana
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 EU/EEA: GDPR Art. 33 and 34 require notifying the supervisory authority within 72 hours of becoming aware of a personal data breach, and affected people where risk is high. Health data adds sector rules. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Belgium.
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: ransomhouse listed 2 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
Listing severity score (heuristic)
72/100 • ELEVATEDA 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 IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.