← Breach analysis by the Dual Vulnerabilities framework

NM Office of Superintendent of Insurance Ransomware (Unattributed, 2023)

2023 · United States · O - Public administration and defence · Ransomware attack with agency-wide outage

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack with agency-wide outage

Dual vulnerability type

Strategy to Leadership

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

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

Why this classification

(1) OSI is New Mexico's insurance regulator; its licensing, consumer-complaint and service-of-process functions presuppose continuous availability of its own systems, and continuity of operations is a strategic-level expectation for a state institution, later made explicit as a funded programme. (2) In practice, from 28 September 2023 a ransomware attack (a 2026 KRQE investigation names the Rhadamanthys info-stealer; the entry vector itself is undocumented and is not load-bearing here) encrypted the agency's files and knocked workstations, servers, email, phones and the website offline; the agency was totally shut down for a week with staff sent home, a reported two-million-dollar ransom demand was not paid, core operations returned only on 5 October 2023 with phones and website still down, and the agency's own release announced the website fully functional only on 21 December 2023. (3) The classification rests on the recovery stage: OSI's own Legislative Finance Committee presentation shows that the full offsite disaster recovery environment, an independent security assessment, DHS support and a cyber security framework were all funded by a post-incident $2 million special appropriation, and dedicated security staff were recruited only afterwards. The expectation (an isolated recovery capability for a critical agency) originated at the strategic level, where such capabilities are decided and funded, and the chain broke at leadership: it was never decided, prioritised or resourced before the intrusion - no source shows a pre-breach continuity programme that was decided and resourced but not realised in operations, which is why this is a knowing-doing gap inside the doctrinal column (Strategy to Leadership) rather than Strategy to Execution. The response stage corroborates the reading: leadership publicly promised restoration by early next week while the website took about twelve weeks, a public account contradicted by the agency's own later disclosure. Egress is not in play: no data exfiltration was ever confirmed. RM31 (Strategy to Leadership lens): leadership continuity objectives were not supported by realistic investment or priorities before the incident - the agency had no full offsite disaster recovery environment until the post-incident special appropriation funded its development and implementation, so the specific missing arrangement, the isolated recovery capability, turned an encryptable network into a weeks-long agency-wide outage (causal role: Constraining). RM04 (Strategy to Leadership lens): concentration in the service model was not recognised or governed - a single intrusion disabled the agency's website, email, phones, workstations and servers at once, and with no independent recovery environment, recovery options were reduced so far that rebuilding required new legislative money (causal role: Amplifying). RM08 (Strategy to Leadership lens): the strategy did not allocate the staff and skills its security intent required - OSI lists recruitment of IT essential staff (System, Network and Security/Compliance Administrators) and a cyber expert among the post-incident accomplishments, a dedicated security capability that was knowable but neither staffed nor funded before the intrusion (causal role: Enabling).

Evidence by stage

Risk markers

Sources

Notes

EuRepoC records functional impact as under 4 weeks, while the victim's own 21 December 2023 release dates full website restoration at about twelve weeks after the incident (core operations returned 5 October 2023); the primary release is used for the timeline. The roughly two-million-dollar ransom demand was reported by KRQE and not confirmed by the Department of Information Technology; reporting says no ransom was paid. No data exfiltration was ever publicly confirmed, so the egress stage is recorded with no gap. The earlier New Mexico Regulation and Licensing Department hack (2022) named in the KOB article is a different agency, so no recurring-weakness marker is coded. The ground.news entry in the case file is an aggregator summary of the KRQE report; the KRQE article is cited directly instead. An nmpoliticalreport.com article on the Superintendent's 29 September 2023 interim-committee briefing could not be opened and is not cited. Link check: nmlegis.gov blocks automated access (HTTP 403); the page was opened and read during research. Link check: krqe.com blocks automated access (HTTP 403); the page was opened and read during research. Link check: ladailypost.com blocks automated access (HTTP 429); the page was opened and read during research.