Skip to content

Watsonville hospital cyberattack disrupts care systems

Summary

Watsonville Community Hospital logo

A November 2024 cyberattack disrupted Watsonville Community Hospital’s network, charts and prescription notifications, requiring paper workflows. Systems were restored in December; later notices confirmed unauthorized access and copied files.

Key facts

Timeline

  • Incident start:
    ? Earliest known or assessed start of malicious activity or incident activity.
  • First public signal:
    ? Earliest public indication of an outage, disruption, closure or other observable incident impact. The signal does not need to mention cybersecurity.
  • First public cyber evidence:
    ? Earliest credible public information connecting the incident or disruption to malicious cyber activity.
  • Official cyber disclosure:
    ? First official acknowledgment by the affected organization or an authoritative public body that the incident was cyber-related.
  • Last impact seen:
    ? Latest public indication that disruption, degraded operations, recovery work or unresolved impact was still ongoing.

Primary victim organization

Impacted location

Critical infrastructure sector

Incident characteristics

Assessments

Attack mechanisms

Data impacts

  • Data theft or exfiltration

    Data was copied, transferred, downloaded, or otherwise removed from the affected environment by an unauthorized party.

  • Data unavailable

    Authorized users could not access required data because of the incident, even when the data was not encrypted, deleted, or destroyed.

Operational impacts

  • Partial service outage

    A service, system, platform, or operational capability remained available only in part or with significant limitations.

  • Network outage

    Internal or external network connectivity was unavailable or materially impaired.

  • Internet access disruption

    The organization lost or materially restricted internet connectivity.

  • Records access disruption

    Staff, customers, patients, students, residents, or other users could not access records or case information normally.

  • Healthcare operations disrupted

    Clinical, diagnostic, pharmacy, patient-care, medical-record, or other healthcare operations were materially affected.

  • Service delay

    Services continued but with longer processing, response, delivery, or completion times.

  • Manual workaround required

    Staff or users had to rely on paper, telephone, in-person, offline, or other manual processes.

Extortion indicators

  • Leak-site listing

    The victim was listed on a threat actor or ransomware data-leak site as an alleged target or nonpaying victim.

  • Data sample published

    The actor published or shared a sample of allegedly stolen victim data to substantiate the extortion claim.

Incident narrative

Hospital systems went offline

Watsonville Community Hospital in California lost access to its computer network Nov. 29, 2024. Internet connectivity and systems used for patient charts and prescription notifications were disrupted. In initial reporting Dec. 2, hospital spokesperson Nancy Gere said staff had switched to paper charts and prescriptions while specialists investigated.

Care continued with delays

The hospital kept emergency, inpatient and outpatient services open. On Dec. 6, Gere confirmed a cyberattack and said the outage was continuing. Manual lab and X-ray requests slowed emergency services, with additional staff assigned to carry orders between departments.

In a Dec. 12 recovery report, Gere said internet access, electronic patient charts and prescription notifications were working again. Staff had added information recorded on paper to the electronic record system, and emergency services were operating normally. Systems had returned over the preceding days; the report did not establish one exact final restoration date.

Later investigation established data access

The hospital’s October 2025 notice identified unauthorized network access from Nov. 25 through Nov. 30, 2024, during which files were accessed or downloaded. A review of the affected files finished on or about Sept. 22, 2025.

Information varied by person and could include identifiers, medical and insurance information, financial details and account credentials. The hospital began notifying identified individuals. Its earlier statement that there was no indication of copying from the electronic health record system did not establish that medical information stored elsewhere was unaffected.

HHS’s public breach table lists a reported 30,312 affected people and a Dec. 31, 2024, submission date.

Attribution remains unconfirmed

Comparitech reported that Termite claimed the hospital on its leak site. DataBreaches.net also reported alleged data samples and a later release. The reviewed hospital notices do not authenticate those materials or confirm the group’s responsibility or ransomware encryption. The exact initial access method and a ransom demand or payment remain unverified in the reviewed primary evidence.

Threat actor and claim

Listed as: Watsonville Community HospitalSource: ransomware.liveDiscovered:

Claim details

Termite listed Watsonville Community Hospital in a claim observed Dec. 11, 2024. Comparitech reported the listing, and DataBreaches.net reported alleged personnel/patient samples and a later release. Observation is not exact original post publication or independent authentication of the claimed materials. Hospital notices separately confirm unauthorized access and copied files but do not confirm Termite responsibility, ransomware encryption, a demand or payment. A separate Sinobi listing observed Oct. 1, 2025 remains an unresolved possible later event and is not attributed to this intrusion.

Organizations involved

Impacted location

  • Watsonville, California

    The affected hospital’s verified physical site is in Watsonville at 75 Nielson Street. This city anchor does not establish disruption to every city service or to its entire tri-county patient catchment. The separate health care district’s legal geographic remit requires its own verified boundary.

Sources

Notice of Data Privacy Incident
Notice of Data Privacy Incident

See something that needs correction?

Signed-in members can report an error, update, or missing source.