← Breach analysis by the Dual Vulnerabilities framework

INTA Ransomware attack (Unattributed, 2023)

2023 · Argentina · O - Public administration and defence · Ransomware attack with nationwide service outage

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack with nationwide service outage

Dual vulnerability type

Expertise to Execution

Evidence coverage: 3/6 stages, weight 15/60

Decisive stage: containment (clearest evidence) · Alternative: Expertise to Leadership

Why this classification

(1) INTA is a national state agency whose IT infrastructure serves a network of more than 400 territorial points and around 7,000 people, and whose agricultural weather radars also feed the Servicio Meteorológico Nacional; after an attack with the same methodology in March 2022 that its own memo says was contained, the expectation was that a propagating ransomware would be held at the technical level by the institute's own specialists. (2) In practice the ransomware spread across the central network infecting ever more machines and encrypting their contents; the only option INTA had was to suspend all institutional IT services nationwide, to cut even the un-hacked radar links to the weather service by security protocol, and to shut the complete system down and clean it unit by unit; three days after detection its own technicians described the malware as still inside, and normalisation ran from mid-May (administrative systems, about 90% by 24 May) to the radar reconnect on 29 May, with two specialised security firms and externally contracted staff brought in and a ransom of USD 2.5 million refused. (3) The expectation and the knowledge here are both material - a propagating ransomware and its remedies (endpoint controls, segmentation, isolation of services, clean rebuild) are specialist knowledge, and INTA's own memo shows the organisation had already seen and contained this same methodology thirteen months earlier - while no source places a doctrinal artefact, a deferred decision or a withheld budget on either side of the gap. What the sources do show is that the known remedy was not realised in the architecture and in operations, so that the only remaining control was a total shutdown of the institution; that is the knowing-doing gap of Expertise to Execution (expertise present, not operationalisable), and the classification rests on the containment stage. The entry vector was never disclosed and is not load-bearing; detection on the same day is not coded as a gap. A second, thinner pattern sits in the recovery stage: capacity that had to be bought in during the crisis would point to Expertise to Leadership, but no source documents a need leadership knew and left unfunded, so it is described here rather than made decisive. RM30 (Expertise to Execution lens): containment could not be implemented in the architecture, because the malware propagated 'infectando cada vez más equipos en la red' until the blast radius covered the whole national network of 400-plus points and roughly 7,000 users, leaving a full shutdown as the only way to stop it (causal role: Amplifying). RM04 (Expertise to Execution lens): institutional e-mail, the administrative and payment systems, internet access at every experimental station and the radar feeds to the weather service all depended on the same central network, so one compromise forced a precautionary nationwide shutdown and the deliberate cut of the radar links degraded short-term weather warnings during a storm (causal role: Amplifying). RM21 (Expertise to Execution lens): the institute's own memo records an earlier comparable incident - March 2022, same methodology, then contained - and states that this time the same methodology did compromise several services, so the earlier event was not turned into validated changes that would stop the repeat (causal role: Perpetuating / learning-blocking). RM38 (Expertise to Execution lens): after detection the eradication could not be scoped or completed by the available tooling and capacity - the malware was 'todavía adentro' days later, services stayed down until the team could review 'dónde estaba alojado el ransomware', and the clean of more than 400 units ran into late May (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Source caveats: the internal memo to INTA staff is not published by the institute itself; its text is quoted verbatim by Clarín, Agrofy News and Bichos de Campo, each of which states it obtained the document, so the memo-based claims are scored as secondary reporting of a primary document. INTA's public disclosure of 2 May 2023 (X thread) was opened and read and is the primary source for the nationwide suspension decision and the 400-point scope. Two source_url leads from the case file could not be opened (tn.com.ar and tsnnecochea.com.ar both refused the request); they were not cited. Attribution: no group was ever officially named - the case file codes the initiator as Not attributed - and the president's statements about a self-described Russian-speaking group are unverified; third-party ransomware trackers link an earlier March 2022 listing to the Everest group, which this analysis did not verify and does not rely on. Disclosure conduct: INTA filed with CERT.ar 'según indica la normativa correspondiente' and told Clarín it had not spoken publicly beyond its social-media notice 'por razones de seguridad'; the ransom figure reached the public through the internal memo given to the press rather than a statement, which is why no notification marker (RM39) is coded. The pay/no-pay decision was documented (refused, with an external forensic review and a judicial complaint prepared), so RM42 is excluded; no regulator or formal investigation of INTA's controls is known, so 'No DV evidenced' is not available. The recovery-stage capacity constraint (two security firms, contracted staff, ten days of overtime) is described in the rationale but not coded as RM08, because the four-marker limit was used for the decisive containment gap and the response-stage eradication gap. Dataset fields: EuRepoC codes functional_impact as Months and intelligence_impact as no data breach/exfiltration, while reporting has the president claiming normalisation within a week (18 May), about 90% of systems back on 24 May and the radars reconnected on 29 May, and Bichos de Campo reporting at least two days of information lost; economic_impact 0 reflects that no ransom was paid, not the cost of a multi-week outage of a national agency. Sector: INTA is a decentralised state agency under the Ministry of Agriculture coded here as O (public administration), matching the receiver category State institutions / political system; M Professional, scientific and technical activities (agricultural research and technology transfer) is the alternative reading. Unattended run: no consent-requiring action (form, login, upload) was needed or taken.