Skip to content

DaVita ransomware attack

Summary

DaVita Dialysis logo

Ransomware disrupted DaVita’s systems, admissions and billing while dialysis care continued. Later findings confirmed stolen laboratory data and restoration.

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

Organization types

Critical infrastructure sector

Incident characteristics

Assessments

Attack mechanisms

  • Ransomware

    Malware that encrypts systems or data, typically accompanied by a ransom demand.

  • Unauthorized access

    Unauthorized access to systems, accounts, networks, or data.

Data impacts

  • Data theft or exfiltration

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

  • Data publication or leak

    Stolen, exposed, or otherwise compromised data was publicly released, posted, distributed, or offered for download.

  • Data encryption

    Data was rendered inaccessible through unauthorized encryption, including ransomware-related encryption.

Operational impacts

  • Partial service outage

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

  • Internal systems unavailable

    Internal business, administrative, operational, or staff-facing systems were unavailable.

  • Payment processing disruption

    The organization could not process, receive, issue, reconcile, or record payments 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.

  • Alternate service channel required

    The organization redirected users to a different website, office, telephone number, email address, provider, or service channel.

  • Staff unable to work normally

    Employees or contractors were unable to perform normal duties because systems, data, facilities, or communications were unavailable.

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

Analyst assessment

DaVita experienced a confirmed ransomware attack that disrupted internal operations while dialysis care continued under contingency arrangements. The company’s April 14, 2025, SEC disclosure said it detected the incident April 12, found parts of its network encrypted and isolated affected systems. That is strong evidence of ransomware and operational disruption, without establishing that every treatment center lost service.

Later company findings place unauthorized access between March 24 and April 12. Removing the intruder April 12 did not end the operational disruption: DaVita’s May 12 quarterly disclosure said most functions had returned but it still could not estimate the full disruption’s duration. The company subsequently said all affected systems were restored. Its 2025 annual report also confirms restoration of relevant business functions. Operational status is therefore resolved, with the precise completion date unestablished.

Operational significance

The attack affected the business processes supporting care. DaVita’s 2025 annual report identifies impaired billing and revenue collection, difficulty accepting new patients and disruption of other business functions. Its initial operational notice directed admissions and urgent requests to an alternative telephone line and medical records to fax. These workarounds and administrative constraints were material even though existing patients continued receiving treatment. The available evidence does not establish treatment cancellations, patient injury or a shutdown of all clinics.

For 2025, DaVita reported approximately $1 million in patient-care charges and $24.2 million in general and administrative expenses for incident remediation and restoration. That approximately $25.2 million excludes business-interruption effects. Earlier quarterly charges are part of the cumulative annual figure and should not be added again. These expenses are separate from any ransom or later legal settlement.

The Veterans Affairs account says Veteran care at DaVita continued and VA systems were unaffected. It does not support a separate VA network incident. DaVita also says its laboratory subsidiary processes results for other providers; the involvement of their patients’ records does not establish operational outages at those providers.

Confidence and uncertainty

Confidence is high in the cyberattack, encryption, disruption and data theft because DaVita directly documented them. The company says an attacker posted claimed stolen data April 24 and that it obtained the posted set around June 18, identifying sensitive information from its dialysis laboratory database. The company notice filed with South Carolina describes information that varied by person: identifying and contact details, Social Security numbers, health insurance and clinical information, laboratory results and, for some people, tax identification numbers or check images. Initial April reporting that theft was unconfirmed has been superseded.

The HHS breach portal, checked Oct. 25, 2026, lists 2,689,826 affected individuals for DaVita’s Aug. 1, 2025, submission. A later preliminary settlement order identifies 2,394,674 proposed class members. These are distinct reported populations, not counts to combine or treat as treatment interruptions.

Interlock claimed the attack, and a stable tracker entry identifies DaVita’s domain. Responsibility remains low-confidence: the claim and lawsuit allegations do not independently establish the operator, and DaVita has not publicly confirmed the group. The claimed data volume is not a verified forensic measurement. No ransom amount, payment outcome or initial access method is established.

Analytic gaps

The exact restoration date, affected systems and locations, and scope of admission and collection delays remain incomplete. The latest specific ongoing recovery observation is May 12, 2025; subsequent breach notifications, financial consequences and litigation do not extend the technical outage.

As of the research cutoff, the settlement administrator describes an agreement capped at $15 million, while a court order schedules final approval for Feb. 18, 2027. The proposal is not a completed payment or a judicial finding of wrongdoing. DaVita denies liability. Final settlement costs, insurance recoveries and total financial impact remain unestablished.

Threat actor and claim

Listed as: DaVitaSource: ransomware.liveDiscovered:

Claim details

Stable Interlock-attributed tracker record identifies DaVita and its exact davita.com domain. The April 25 timestamp records tracker discovery, not attack onset or original publication. DaVita’s own incident update says an actor posted claimed stolen data April 24 and that the company obtained the posted set around June 18 and confirmed laboratory information was involved. This supports a data publication finding without independently proving Interlock responsibility. External reporting attributes the claim to Interlock and describes roughly 1.5 TB; the volume is an allegation, not a confirmed measurement. The company has not publicly confirmed the gang, ransom amount or payment outcome. Original leak-post URL and exact claim publication time remain unknown. No separate claim against DaVita Labs was found in canonical-name and domain searches.

Organizations involved

Impacted locations

  • Denver County, Colorado

    Denver is the affected company’s headquarters and administrative physical anchor. This does not assert a citywide outage, disruption of Denver government or effects at every DaVita clinic. Consolidated city-county identity is supported by official history, Census geography and exact OSM relation 1411339.

  • DeLand, Florida

    Physical home of the named affected laboratory operation. Exact official address 3000 DaVita Way is within DeLand city and Volusia County according to Census. This is an organization-site anchor; the evidence does not establish that stolen data were hosted exclusively in this building or that all local medical services were interrupted.

Sources

DaVita Form 8-K: ransomware incident
DaVita notice of data breach dated Aug. 5, 2025
HHS OCR breach portal: DaVita Inc.

See something that needs correction?

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