2022 · Argentina · O - Public administration and defence · Malware attack via compromised backup system causing website outage
Analysed 2026-11-06 by Hermes
Open this case in the tool →Malware attack via compromised backup system causing website outage
Strategy to Execution
Evidence coverage: 3/6 stages, weight 20/60
Decisive stage: recovery (clearest evidence) · Alternative: Expertise to Execution
(1) INDEC, Argentina's national statistics office, ran a formal continuity arrangement: periodic scheduled backups of its systems - the control meant to guarantee recovery of the Institute's systems. (2) In practice the backup environment was not isolated or validated: malicious code that had reached the estate and lodged in the periodic backup was activated when the scheduled backup itself executed, encrypting the virtual machine that authenticates internal users; the website and internal authentication were disrupted for more than 24 hours and the remaining servers had to be shut down as a precaution (the disconnection worked: no other servers or data were hit, and the spokesperson stated no data was compromised). (3) The continuity requirement existed as a formal arrangement but did not translate into operational architecture - the recovery capability itself became the attack mechanism. That is a doctrinal-origin, execution-break gap, not a leadership decision: no source shows any strategic decision about backup isolation was known and deferred. The entry vector is not load-bearing and was never disclosed (ESET records that nothing was shared about the malware type or how access was attempted); how the code reached the estate is undocumented, and that entry/detection gap would be the secondary Expertise to Execution pattern in this case. The classification rests on the recovery stage, the only gap documented by secondary sources reporting the victim's own account. RM31 (Strategy to Execution lens): the continuity requirement of periodic backups was not translated into isolated, validated arrangements - the backup system hosted the virus and the scheduled backup job itself activated it, constraining recovery and extending the outage (causal role: Constraining). RM28 (Strategy to Execution lens): endpoint and malware-protection requirements were not implemented or enforced across the servers, since malicious code was able to lodge on the hosting server and backup system and to execute there (causal role: Enabling). RM34 (Strategy to Execution lens): monitoring and alert-handling requirements did not operate as intended - the resident malware went unnoticed until it executed during the backup, so the organisation learned of the incident only from the encryption damage (causal role: Obscuring).
RM31 — Resilience / backup preparedness gapRM28 — Endpoint / malware-protection gapRM34 — Monitoring / detection / alert-handling gapLink check: databreaches.net blocks automated access (HTTP 403); the page was opened and read during research. Two of the dataset's source URLs are dead: the Infobae article (infobae.com, HTTP 404, no Wayback snapshot in the CDX index) and the tsnnecochea.com.ar retrospective (HTTP 404); the mechanism details first reported by Infobae were read instead via the two cited articles, which quote the victim's spokesperson and reproduce INDEC's Facebook/Twitter statements verbatim. The Twitter statement URL in the case file was not opened; the quote was read on the two cited pages. Timing caveat: INDEC's own follow-up update says the site was active again after security tests (within about a day), while the EuRepoC row codes disruption > 24h and functional impact days (< 7 days); the longer dataset figure was used. No attribution, no forensic report and no public investigation findings were ever published (ESET: no information shared on malware type, access method or scope); the 2012-2013 Anonymous defacements of INDEC found in search are a different mechanism with no documented lesson linkage, so no recurrence marker was coded; csidb.net results were excluded as a breach database per research boundaries. Actor unattributed - does not affect the victim-side classification.