Qilin ransomware claims Université Libre de Bruxelles breach
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Qilin ransomware operators claim breach of Belgian university affecting thousands of employee and user credentials.
Ransomware.live, a public tracking platform for ransomware campaigns, reports that Qilin ransomware operators have claimed responsibility for a breach of Université Libre de Bruxelles (ULB), a major Belgian public university. According to the posting, the attack compromised 39 employees, 2,268 user accounts, and 630 third-party employee credentials. The attackers also identified 109 external attack surface assets and obtained DNS records for the institution's domain. The breach appears to be part of Qilin's extortion-based operational model, in which operators exfiltrate data and threaten disclosure to pressure victims into ransom payment. No technical exploitation details, malware samples, or attack vectors are specified in this public claim.
For defenders, the posting confirms Qilin remains actively targeting institutional networks and maintaining a credential-harvesting capability at scale. The specificity of the compromise metrics (employee count, user account volume, external assets) suggests reconnaissance and lateral movement rather than mass-exploitation of a single vulnerability. Educational institutions should review access logs, reset credentials for potentially exposed accounts, and segment networks to limit lateral movement by ransomware payloads. Third-party credential compromise is a known attack chain leading to ransomware deployment.
This is a victim-notification post from a public ransomware tracking site and does not constitute detailed threat intelligence on exploitation methods, malware capabilities, or attack infrastructure.
Mentioned in this report
Detection guidance
1 detection for this report is in the app — rules that match its indicators, converted to Splunk SPL, to Elastic where their fields map onto Elastic's integrations and to Microsoft Defender XDR KQL wherever Defender records the activity, plus YARA and Suricata. Three days of it free, no card.
Source reporting: https://www.ransomware.live/id/VW5pdmVyc2l0w6kgTGlicmUgZGUgQnJ1eGVsbGVzQHFpbGlu
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 614 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs