← Breach analysis by the Dual Vulnerabilities framework

Rio Grande municipality malware attack (Unattributed, 2023)

2023 · Puerto Rico · O - Public administration and defence · Malware attack with system corruption and data theft

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Malware attack with system corruption and data theft

Dual vulnerability type

Expertise to Execution

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

Decisive stage: containment (clearest evidence) · Alternative: Strategy to Execution

Why this classification

(1) The municipality ran its administrative systems and public web portal with its own IT staff - an IT systems officer and an IT director - and was expected to hold the basic practices known to such specialists: isolating the internet-facing portal from internal administrative data and being able to notice data leaving the network. (2) In practice a single virus introduced through the public portal corrupted the portal and the entire content of the municipal system, and administrative data was extracted without detection: the theft surfaced only on Monday 27 November 2023 when the IT officer saw data missing from the monitors; a private IT company confirmed the attack and damage was estimated at approximately 75,000 US dollars. The entry vector and the actor were never disclosed and the entry stage is not load-bearing for the classification. (3) The classification rests on the containment stage: the remedies (trust separation between the public web presence and administrative systems, egress monitoring) sit in the material column with the municipality's own specialists and required no leadership decision, yet were not realised in architecture or operations - the blast radius of one portal compromise was the municipality's whole content, and the exfiltration passed unnoticed. This is a knowing-doing gap within the material column - expertise was present (the specialists detected the visible damage, procured forensics and involved the authorities) while known controls were not executed: Expertise to Execution. That the origin and break read this way is an inference from the documented blast radius and undetected extraction; no source documents the network architecture, which caps the confidence. A secondary pattern (Strategy to Execution) would need evidence of formal policy that never reached operations; no source shows any policy artefact. (4) RM30 (Expertise to Execution lens): containment could not be implemented in the municipality's architecture as the specialists would have known it - a single virus through the web portal reached and corrupted the entire content of the municipal system instead of being bounded to the exposed portal (causal role: Amplifying). RM35 (Expertise to Execution lens): egress monitoring was absent in operations, so the extraction of administrative data left the network unnoticed and came to light only retroactively from the missing data on the monitors, widening the impact beyond the visible corruption (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Thin police-blotter record: reporting quotes the police report of the complaint filed by the municipality's IT officer; no follow-up reporting on the investigation or restoration was found. The EuRepoC start_date (01.11.2023) is inconsistent with the sources' detection date (Monday 27 November 2023); the year 2023 is unaffected. Impact fields (disruption > 24h, functional impact < 7 days, minor data breach) come from the EuRepoC record and are not corroborated in the press. The mayor's statement that the lost data was minimal is treated as consistent with the dataset's minor-exfiltration classification rather than a disclosure discrepancy, so no response-stage gap or RM39 is coded. Aggregators list a later ransomware claim (2026) against the same municipality; it rests on leak-adjacent sources this run does not open, the case file carries no related_rows, and it is not used as evidence here. No security regulator or CERT examined the incident; law enforcement (Puerto Rico Justice Department CIC and Cybercrime Division) investigated without published outcome.