← Breach analysis by the Dual Vulnerabilities framework

University of Maribor Ransomware (Unattributed, 2024)

2024 · Slovenia · P - Education · Ransomware attack

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack

Dual vulnerability type

Strategy to Execution

Evidence coverage: 2/6 stages, weight 14/60

Decisive stage: recovery (clearest evidence) · Alternative: Strategy to Leadership

Why this classification

(1) The strategic expectation at the University of Maribor was that its central computing capacity - the single platform carrying digital identity, e-mail, student and staff e-services and the academic, HR and financial systems of Slovenia's second-largest university - was protected by a properly configured protection and backup regime; the Information Commissioner publicly restated the underlying duty on 25 October 2024: for ransomware the security copies matter most, they must not be exposed to the attack and they must actually allow restoration. (2) In practice a single intrusion on the evening of 23 October 2024 encrypted the central data and server capacities and disabled nearly all IT services; Delo and STA reported the attackers encrypted all data including the backup copies; a month later the university was rebuilding slowly and with special caution from backup copies and other return procedures, with around 300 services still not returned to use and no timeline; four months on, everything was restored without data loss but only at a remediation cost of EUR 177,444.72 and with some minor systems still partially non-functional. (3) This is a knowing-doing, doctrinal-material gap rather than weak security in general: the formal expectation of an isolated, tested restore capability existed and leadership affirmed it, but the architecture never realised it - the recovery path evidently depended on the same central environment the attacker reached, so the blast radius of one central compromise was the whole university and recovery stretched over months; the entry vector was reportedly identified internally but never publicly explained and is not load-bearing, and the classification rests on the recovery stage (with the same centralised design showing at containment). The only account of why the arrangements fell short is a security expert quoted by Delo who said awareness was not lacking but funding for proper equipment was; that reported resourcing pressure is noted as a secondary Strategy-to-Leadership pattern but no source documents a leadership decision on the backup arrangement itself. RM31 (Strategy to Execution lens): continuity objectives existed and were publicly affirmed, yet the backup/restore arrangement was not isolated or proven against an attack on the central environment - Delo and STA reported the copies were encrypted too, and the university's own statements show a cautious multi-month rebuild from copies whose adequacy could not be taken for granted (causal role: Constraining). RM04 (Strategy to Execution lens): nearly all university services depended on the one central compute/identity platform, so leadership's own service model turned a single compromise into a total outage and also narrowed the recovery options, since the dependency at the centre was both the breach target and the restore path (causal role: Amplifying). RM08 (Strategy to Execution lens): security capability was knowable but under-funded - the expert assessment reported by Delo was that the university is aware of cyber security but lacks sufficient funds for proper protective equipment, which is why the known control designs were never fully realised in the material estate (causal role: Enabling).

Evidence by stage

Risk markers

Sources

Notes

Case-file caveats: eurepoc_extra.start_date (20.10.2024) predates all reporting, which puts the attack on the evening of 23.10.2024; Year taken as 2024. mitre_impact says Data Exfiltration, but the victim's own analysis (traffic data and the 25.11.2024 statement) found no access to or export of personal data, and no leak or extortion demand ever surfaced; the egress stage is recorded accordingly. The ransomware type and Russian-speaking attribution come from unnamed sources in 24ur.com and Delo (Babuk-type code; the original Babuk group had shut down in 2021 and leaked its source code), and the police criminal investigation did not identify the perpetrator by February 2025 - attribution treated as unconfirmed. The claim that the backup copies were themselves encrypted rests on Delo's unnamed sources and STA; the university did not comment on it directly and the rector asserted a properly configured protected-copies system, so the recovery gap is evidenced by the months-long, cautious, cost-heavy rebuild rather than by an admission. The two source_url articles (Večer, Delo) opened fine and match the row description, which is consistent with the stated victim. No regulator sanction found: the Information Commissioner told Delo on 25.10.2024 it had not yet been formally notified and sanctions were premature; no later decision surfaced in this research.