← Breach analysis by the Dual Vulnerabilities framework

Morlaix ransomware (Unattributed, 2023)

2023 · France · O - Public administration and defence · Ransomware attack

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack

Dual vulnerability type

No DV evidenced

Alternative: Expertise to Execution

Why this classification

(1) Morlaix is a commune of roughly 15,000 inhabitants run under the French local-authority cybersecurity doctrine, whose core expectations are regular backups, isolation of compromised systems, escalation to ANSSI and accurate communication with residents; the mayor stated after the incident that the municipality had invested in and reinforced security measures, and the city's own 2025 financial summary confirms continued security spending. (2) Overnight, ransomware encrypted two of the town's three servers and left a ransom note; the attack was noticed on Thursday 21 September 2023 when staff relaunched the servers, all service e-mail addresses and internal software were taken down, and staff worked on paper for days. The response executed the doctrine: the affected servers were immediately stopped and isolated for investigation, ANSSI was called at once, a complaint was filed, the town disclosed the attack on its Facebook page the same day with an accurate account of what was closed and what still worked, warned of longer processing times for passport and ID services, refused the extortion, and restored from a backup made the night before, so no data loss was reported and no data exfiltration was substantiated. The city website and teleservices, hosted on the Morlaix Communauté server, were unaffected, keeping the blast radius inside the town's own servers; after the incident the city signed contracts with Orange Cyberdéfense and for awareness tools, documented in its own 2025 report. (3) This is alignment, not merely an absence of bad news: control performance is positively documented at three lifecycle stages - recovery (backup executed the previous evening, usable, no data loss), containment (immediate isolation, limited blast radius) and response (immediate escalation, complaint, accurate self-initiated same-day disclosure) - and no source documents a victim-side gap at any stage, so it is a confirmed negative case rather than a knowing-doing or doctrinal-material gap. The entry vector is officially undetermined (diagnostic still in progress; the mayor's mail/USB speculation is explicitly conjecture) and is not load-bearing; an undetermined entry route alone does not create a gap. Two structural conditions remain and are recorded as risk markers rather than as a DV gap: all municipal internal software and e-mail ran on the two in-house servers, so their encryption stopped internal operations across the whole commune, and the malware ran undetected on those servers until the morning restart - but no source shows a known hardening or detection remedy that was available and not applied before the incident. The classification rests on the recovery and response stages; the entry stage yields no assessable mechanism.

Risk markers

Sources

Notes

Source caveats: (a) the victim's own Facebook announcement (in the dataset source_url) could not be opened (login wall); its text is quoted verbatim in the opened articles; (b) the Le Telegramm initial report and its follow-up on the return to normal (cited by the dataset round-up) returned HTTP 403 and no archived snapshot exists, so the refusal-to-pay claim is taken from the LeMagIT weekly round-up that cites Le Telegramm; (c) the entry vector was never determined in any opened source and no group claimed the attack, so actor is 'Unattributed cybercriminals' (the mayor's mail/USB conjecture is flagged by him as conjecture and was not used as evidence); (d) EuRepoC records no confirmed data breach, while contemporaneous reporting said exfiltration could not yet be ruled out - egress is recorded as no substantiated theft, not verified clean; (e) no reporting after 27 September 2023 was found on the restoration timeline; EuRepoC's functional impact is days (<7 days), consistent with the Le Telegramm headline indicating a near return to normal soon after; (f) the city's own 2025 financial summary dates the cyberattack to October 2023 while all contemporaneous reporting dates discovery to 21 September 2023 - the note was used only for the post-incident contracts, the September date is kept as Year/incident date. Data quality: the case-file description matches the stated victim. RM28 is coded from the demonstrated fact that the malware ran on the servers until encryption, at inference level; no source describes the endpoint protection state. Per the run's research boundaries, no leak site, breach database or dark-web source was consulted. Link check: ouest-france.fr blocks automated access (HTTP 403); the page was opened and read during research.