← Breach analysis by the Dual Vulnerabilities framework

Morón Municipality Ransomware (Unattributed, 2024)

2024 · Argentina · 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

Strategy to Execution

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

Decisive stage: recovery (clearest evidence) · Alternative: Expertise to Execution

Why this classification

(1) Morón Municipality ran all of its resident-facing digital services (online procedures, the municipal web, the Morón a mano app) and its internal telephony on one municipal network, and its doctrinal recovery expectation was explicit in its own official communiqué: every server has daily backups, so normalization was promised within days. (2) On Easter Sunday 31 March 2024 anonymous hackers deployed ransomware that encrypted that entire estate at once - all servers, all areas, the Palacio Municipal and the decentralised dependencies, plus the telephone lines - and although the municipality disclosed the same day, filed a criminal complaint and worked from backups with external cybersecurity specialists, restoration took weeks of complex and detailed manual work: by 28 April, four weeks on, the system was still only almost fully normalized when a second ransomware attack hit it. (3) The classification rests on the recovery stage: the strategic artefact existed and was publicly asserted (declared daily backups, promised days), but operations could not realise it - a full restore from daily backups that takes four weeks of manual, server-by-server effort shows the backup regime was a declared practice, not a tested, operational recovery capability. That is a doctrinal expectation failing at execution (Strategy to Execution), not leadership knowingly deferring anything. The entry vector is undisclosed and not load-bearing; detection, disclosure and egress show no documented gap. (4) RM31 (Strategy to Execution lens): the continuity requirement the municipality itself proclaimed - daily backups on all servers, recovery in days - was not translated into a tested restore capability, since the victim's own account of weeks of complex and detailed manual reconstitution against the promised days identifies the restore process as untested (causal role: Constraining). RM30 (Strategy to Execution lens): isolation and segmentation requirements were not implemented in the architecture, so one intrusion reached all servers, all areas and the telephony simultaneously and the blast radius equalled the whole organisation (causal role: Amplifying). RM04 (Strategy to Execution lens): all resident-facing services and internal telephony depended on the single shared municipal network, a single point of failure that turned one encryption event into a total service outage and left no partial-service fallback while the shared estate was rebuilt (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

EuRepoC row; victim disclosed (source_disclosure). Year from eurepoc_extra.start_date (31.03.2024), country from receiver_country. A second ransomware attack on 28 April 2024 (announced by the municipality, reported by infodiadia) is a separate incident and is not classified here - the case file carries no related_rows; it is used only as follow-up reporting that the first incident's recovery still was not complete four weeks on. Actor unattributed and no ransom payment was reported; the extortion note (Tor decryption steps) is cited as reported in press and the official communiqué. Entry vector undisclosed; the employee e-mail / Trojan possibility is an unverified, offhand statement by municipal spokespersons to MDZ and is not treated as evidence. No data exfiltration established (EuRepoC intelligence_impact: none). Analysis performed unattended; no source requiring consent (forms, logins, uploads) was used. Link check: mdzol.com blocks automated access (HTTP 403); the page was opened and read during research.