← Breach analysis by the Dual Vulnerabilities framework

Curry County Ransomware (Royal Ransomware Group, 2023)

2023 · United States · O - Public administration and defence · Ransomware attack on county server network

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack on county server network

Dual vulnerability type

Strategy to Leadership

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

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

Why this classification

(1) The strategic expectation at the county was that the Board of Commissioners keeps its statutory records and public services running: it owns the records function (deed, licence and court-adjacent files) and acts on it at budget level, as it later showed when it transferred $500,000 in ARPA funds to restore lost records. By early 2023 leadership also knew cyber security was a need: it was in the middle of negotiating a cyber-security contract with the local electric utility and had applied twice for a cyber-security grant. (2) In practice, on 26 April 2023 the Royal ransomware group encrypted the county server network; the sheriff's dispatch noticed the same morning, every department lost access, all online files were destroyed, and the county had to wipe and rebuild network, servers and computers from scratch with CISA, state and volunteer help, services staying disrupted from April into about August with costs put at millions of dollars. The rebuild itself revealed what leadership had never funded: no redundant data storage, hardware past its useful life, no IT director (hired only afterwards), multi-factor authentication that had to be implemented for all devices during the rebuild, and cyber-insurance cover the county's own operations director called almost non-existent because very limited protections were in place at renewal. (3) This is a knowing-doing gap inside the doctrinal column, not a failed execution of a decided policy: the continuity expectation sat with the Board itself, and the sources show the chain broke at the leadership funding decision - grants failed, the security contract was not concluded, basic resilience was never budgeted - rather than at operations failing to deliver a resourced programme. The entry vector is undisclosed and not load-bearing; the classification rests on the recovery stage (with the response-readiness gap pointing the same way). A secondary pattern is visible at Expertise to Execution (known remedies - backups, MFA - simply absent), but no source shows them decided and resourced. (4) RM31 (Strategy to Leadership lens): the county's continuity objective was never supported by realistic investment or priorities - no redundant storage existed at attack time, and redundancy was only remedied afterwards, which turned an encryption event into a multi-month rebuild from scratch (causal role: Constraining). RM08 (Strategy to Leadership lens): leadership strategy did not allocate the staff, budget or skills the intent required - two failed cyber-security grant applications, a first IT director hired only after the incident, and near-zero insurance at renewal show capability was knowable but never made available (causal role: Enabling). RM36 (Strategy to Leadership lens): leadership had an emergency-management programme but never established or tested cyber response readiness within it, so during the incident the EOC struggled with the uniqueness of a cyber attack and had to improvise network-rebuild capability from outside the county (causal role: Constraining).

Evidence by stage

Risk markers

Sources

Notes

EuRepoC row; description matches the stated victim (Curry County, Oregon). Data-quality: the row's source_url is the county newslist page (now a redirect to the relaunched county site with no 2023 items left) plus three therecord.media articles about OTHER Royal ransomware victims (Dallas TX, a coastal Mississippi county, a Pennsylvania court DDoS) - none is about Curry County; all case evidence therefore comes from own research (regional press, county documents). County Resolution R-2023-10 (local emergency declared 5 May 2023, citing the 26 April ransomware attack) is a scanned PDF with no text layer; only its partially extracted WHEREAS text was read and it is cited solely for the 5 May emergency declaration, also confirmed by IJPR reporting; the resolution's preliminary damage estimate in excess of $5,000,000 appears in the indexed page text but could not be re-verified from the scan, so the rationale uses officials' own 'millions of dollars' figure instead. Data-theft conflict: some headlines say data was stolen and Royal claimed exfiltration, but the county reported no evidence of personal-information compromise and EuRepoC records no data breach - egress treated as not in play. One-sided lead not used: in May 2024 a resident (later a county commissioner) claimed from meeting records that leadership had been warned of a cyber attack as early as January 2021 and that no access-restriction or enhanced-backup action was reported; single unverified source, and the promised after-action report was not published as of that article. The case file carries no related_rows. The ransom payment decision was never publicly disclosed (county declined, citing the ongoing FBI/DHS investigation). Link check: ijpr.org was unreachable at check time (timeout); the page was opened and read during research. Link check: kdrv.com blocks automated access (HTTP 429); the page was opened and read during research. Link check: kezi.com blocks automated access (HTTP 429); the page was opened and read during research.