Analyst assessment
Taos County experienced a cyberattack that disrupted government computer systems beginning in early June 2025. Our reporting dates detection to June 5 and recounts County Manager Brent Jaramillo’s July 1 acknowledgment of a sophisticated cyberattack. Local real-estate agent Rob Swan’s June 26 account places detection approximately June 6 and describes a precautionary shutdown.
Operational significance
The disruption affected administrative and records functions. Our report identified unavailable computers in several county offices and the Adult Detention Center, alongside slower court work and stalled property transfers. These consequences support a public-service disruption assessment; they do not establish that detention custody, emergency response or every county service ceased.
The June 26 account independently described county departments operating with limited capability or stopping work and identified real-estate transactions as affected. July 4 reporting described partial recovery with continuing manual work and delays. A system shutdown can impede services without proving that an attacker encrypted files.
Confidence and uncertainty
Confidence is high that a disruptive cyberattack occurred, based on the reported county acknowledgment and consistent accounts of service interruption. The technical mechanism remains less certain. Although our original headline used ransomware, the reviewed evidence does not establish an encryptor, encryption extent or a specific initial-access method.
Comparitech reported a Kairos listing and payment deadline, but explicitly could not authenticate the purported stolen files. Responsibility remains a claim. Neither the claimed data volume nor the group’s geographic origin is treated as an independently established fact in this record.
Analytic gaps
The exact intrusion window, systems affected, verified data-loss scope, payment outcome and full-restoration date remain unresolved. A local writer inferred payment from removal of a listing; that inference does not verify a transaction.
Operational disruption is presumed resolved because of the elapsed time. No end date is assigned.