Skip to content

McLaren Health Care ransomware attack

Summary

McLaren Health Care logo

McLaren Health Care’s August 2024 ransomware attack disrupted phone and IT services and delayed some care. Systems were restored by Aug. 26, but manual records entry remained underway. A later notice confirmed earlier unauthorized access; a final backlog-clearance date is unverified.

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

Critical infrastructure sector

Incident characteristics

Assessments

Attack mechanisms

  • Ransomware

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

Data impacts

  • 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

  • Phone service disruption

    Telephone, voice-over-IP, call-center, or related voice communication services were unavailable or materially impaired.

  • Internal systems unavailable

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

  • Database unavailable

    A database or data-management system became unavailable or inaccessible.

  • Records access disruption

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

  • Records processing disruption

    The organization could not create, update, search, file, approve, transmit, or otherwise process records normally.

  • Scheduling disruption

    Appointment, booking, reservation, dispatch, staffing, or other scheduling functions were unavailable or impaired.

  • 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.

  • Backlog created

    The disruption caused an accumulation of unprocessed requests, cases, orders, records, appointments, or other work.

  • 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

  • Ransom demand

    The victim received a demand for payment in exchange for restoring access, decrypting systems, preventing disclosure, or stopping another threatened action.

  • Data-theft extortion

    The actor threatened to disclose, sell, distribute, or otherwise misuse stolen data unless the victim paid or complied with demands.

  • Public leak threat

    The actor explicitly threatened to publish or publicly release victim data or incident details.

Incident narrative

Analyst assessment

McLaren Health Care’s 2024 ransomware attack disrupted information technology and phone services across its Michigan health system. Its official Aug. 7 acknowledgment confirmed a criminal cyberattack and described hospital and outpatient downtime procedures.

McLaren’s 2024 annual report dates the systemwide cyberattack to Aug. 5 and says the organization locked down its systems and shifted to paper records. A subsequent notification letter identifies unauthorized access July 17-Aug. 3, an earlier intrusion window that does not establish the start of patient-service disruption. This incident is separate from McLaren’s 2023 attack.

Operational significance

McLaren reported limited system access, rescheduled non-emergency care and asked patients to bring medication information, printed orders and test results. Emergency departments and most surgeries continued. Later reporting of the health system’s updates described ambulance diversion for certain conditions at some locations, alongside continued clinical operations.

By Aug. 26, McLaren reported its IT platforms and clinical and administrative operations restored, according to its statement to Becker’s Hospital Review. Staff had begun transferring manually charted patient information into electronic records. That remaining work separates restored access from completed records reconciliation.

Confidence and uncertainty

Ransomware confidence is high: McLaren identified ransomware in its later statements and filed notification. Responsibility remains less certain. An Aug. 5 public post shared an alleged INC Ransom note from the Bay City location, asserting encryption and threatening disclosure of stolen information unless paid. The photograph establishes a public allegation, rather than independently authenticated attribution or a verified inventory of encrypted and copied files.

The June 2025 notification describes potentially affected personal information and a file review completed May 5, 2025. Those later investigation and notification dates do not establish continuing hospital outages. The reviewed letter uses variable data fields, limiting conclusions about the information involved for every recipient.

Indiana’s 2025 breach register lists 743,131 people affected by the incident, including 530 Indiana residents, and records June 20, 2025, as the notification date. This reported count does not establish which information was involved for every person.

A Michigan judge granted final settlement approval April 21, 2026. The agreement’s $14 million fund covers claims arising from both the 2023 and 2024 breaches, without an admission of wrongdoing. The combined fund does not establish the cost of the 2024 attack alone or a ransom payment.

Analytic gaps

The final date for completing manual-records entry remains unverified. The incident is presumed resolved at the research cutoff, with no confirmed end date for all recovery work. The Aug. 26 restoration milestone should not be extended by the projected duration of the backlog.

The initial entry route, complete data-impact inventory, authentication of the alleged INC note and ransom-payment outcome remain unverified.

Threat actor and claim

Source: Publicly shared alleged INC Ransom notePublished: Discovered:

Claim details

An Aug. 5, 2024, public post by Thomas Barz shared a photograph described as coming from a former colleague at McLaren’s Bay City location. The note bears an INC Ransom header and alleges encryption and data theft, threatening disclosure unless paid. The photograph establishes a reported allegation, rather than independently authenticated actor responsibility, a confirmed actor-site listing or verified contents of stolen files. Its date identifies the public photograph. McLaren subsequently confirmed ransomware but did not identify INC in its statement or consumer letter. The ransom amount, payment outcome and any public release remain unverified.

Organizations involved

Impacted locations

Sources

Publicly shared alleged INC Ransom note from McLaren Bay City location

Thomas Barz shared a photograph described as coming from a former colleague at McLaren’s Bay City location. The alleged INC Ransom note asserts encryption and data theft and threatens disclosure unless paid.

McLaren Health Care confirms criminal cyberattack and describes downtime procedures

McLaren confirmed a criminal cyberattack and described limited IT and telephone access, hospital and outpatient downtime procedures, and rescheduled non-emergency care. Emergency departments and most surgeries continued.

AG Nessel Alerts Consumers of Ways to Protect Their Data After McLaren Cyber Attack

Michigan’s attorney general cited McLaren’s acknowledgment of a criminal cyberattack, limited system access and disruption reported Aug. 6, 2024, while facilities remained largely operational.

McLaren Health Care hit by ransomware attack again

McLaren confirmed ransomware and limited IT access in its Aug. 16 update. Reporting also described earlier ambulance diversions for certain conditions at some sites while clinical care continued.

McLaren back online after ransomware attack

McLaren reported restored IT systems and clinical and administrative functionality, with temporary procedures lifted. Staff had begun entering manually charted patient information into electronic records.

McLaren Health Care June 20, 2025, consumer notification letter

McLaren’s June 20, 2025, notification identifies suspicious-activity discovery about Aug. 5, 2024, unauthorized network access July 17-Aug. 3 and completion of its file review May 5, 2025.

McLaren Health Care Annual Report 2024

McLaren’s 2024 annual report dates the systemwide cyberattack to Aug. 5 and describes immediate system lockdown, paper records and continued patient care. It also identifies the historical 13-hospital network, including Bay Special Care.

McLaren Health Care class action settlement agreement and release

The agreement establishes a $14 million settlement fund covering claims from the separate 2023 and 2024 breaches, payable by McLaren and/or its insurers.

See something that needs correction?

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