Machelen (Belgium) was listed on 27 October 2026 by the rhysida ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). rhysida listed 20 organizations that month and 328 in total.
- Listed 23 days ago.
- 1147 organizations were listed by all groups in October 2026, see the month.
- 157 in Healthcare that month.
- 4 in BE that month.
Updated 2026-11-19 05:31 UTC. Data: public leak-site listings. How we work.
Threat Group Post & Evidence
- Listed by
- Rhysida 328 listings in total
The listing states no data size and no ransom demand.
Dark Web Leak Proof Screenshot
Original Source (Safe Tor Stream)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.
Machelen (Belgium) Machelen (Belgium) - municipal and social welfare (OCMW) file servers1.3 million files, ~2.9 TB. Working copy + backup copy (lawer2/lawer3). Language: Dutch, partly French.Contents:Social welfare and migration service client files: passports, ID cards, residence permits, sick notes.WZC nursing home: medical files, staff HR dossiers, workplace accidents.Civil status records (births, marriages) with national register numbers (NISS/RRN).Payslips, financial data.Correspondence (~23k messages), employee home folders.Databases and backups: full OCMW database backup (6 GB, 09/2026), 645 .mdb databases, 12,873 .dbf, 110 .bak (17 GB).Verified: 13,319 files with personal data. Among them - a valid Belgian ID card (expiry 02/2029), Belgian and Moroccan passports, national register numbers (RRN), sick notes with patient addresses, medical documents (GDPR Art. 9 special categories)…
Show the full post (909 characters)
Machelen (Belgium) Machelen (Belgium) - municipal and social welfare (OCMW) file servers1.3 million files, ~2.9 TB. Working copy + backup copy (lawer2/lawer3). Language: Dutch, partly French.Contents:Social welfare and migration service client files: passports, ID cards, residence permits, sick notes.WZC nursing home: medical files, staff HR dossiers, workplace accidents.Civil status records (births, marriages) with national register numbers (NISS/RRN).Payslips, financial data.Correspondence (~23k messages), employee home folders.Databases and backups: full OCMW database backup (6 GB, 09/2026), 645 .mdb databases, 12,873 .dbf, 110 .bak (17 GB).Verified: 13,319 files with personal data. Among them - a valid Belgian ID card (expiry 02/2029), Belgian and Moroccan passports, national register numbers (RRN), sick notes with patient addresses, medical documents (GDPR Art. 9 special categories). More
Amounts as written
- 2.9 TB
- 6 GB
- 17 GB
- 13,319 files
Kinds of data mentioned
-
Identity documents
“…partly French.Contents:Social welfare and migration service client files: passports, ID cards, residence permits, sick notes.WZC nursing home: medical files, staff HR dossiers,…”
-
Medical or patient records
“…files: passports, ID cards, residence permits, sick notes.WZC nursing home: medical files, staff HR dossiers, workplace accidents.Civil status records (births, marriages) with…”
-
Customer or client data
“…Language: Dutch, partly French.Contents:Social welfare and migration service client files: passports, ID cards, residence permits, sick notes.WZC nursing home: medical files,…”
-
Employee and HR records
“…cards, residence permits, sick notes.WZC nursing home: medical files, staff HR dossiers, workplace accidents.Civil status records (births, marriages) with national register…”
-
Databases and backups
“…welfare (OCMW) file servers1.3 million files, ~2.9 TB. Working copy + backup copy (lawer2/lawer3). Language: Dutch, partly French.Contents:Social welfare and migration…”
Plain-English summary AI-written
The group says it holds municipal and social welfare files from Machelen, including personal, medical, financial, employee, database, and backup records.
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 Machelen (Belgium) (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 Machelen (Belgium) 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 Machelen (Belgium) 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, identity documents, employee and hr records.
- Check software and integrations you take from them If you run their software or call their API, check that updates come through the usual channel and rotate the keys and tokens you hold for it. Why: The post names: databases and backups.
- 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 Machelen (Belgium) 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 Machelen (Belgium)
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: identity documents, customer or client data.
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.
- 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, identity documents.
- Rotate database and cloud access Rotate database and cloud-storage keys, review public bucket and snapshot sharing, turn on object-level audit logging and keep backup encryption keys separate. Why: The post names: databases and backups.
- 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: 2.9 TB, 6 GB, 17 GB. Treat group figures as unverified.
- 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.
- 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.
-
Check the ways rhysida is reported to get in
Check these first; they are how the group is reported to work in general.
- Actors typically log in to VPN access points with stolen valid credentials, which the advisory ties to organizations without multi-factor authentication. (update of Apr 2025)
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: rhysida listed 7 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)
91/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 IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.