Editorial illustration.
Editorial illustration.
Corporate Targets · Cyberattack · 24 of 60

McLaren Restored Its Hospitals. The Breach Investigation Took Nine More Months.

A ransomware attack disrupted a Michigan health-care corporation in 2024. The 2026 settlement that followed covered that incident and an earlier breach, a distinction hidden by the headline number.

On August 8, 2024, McLaren Health Plan told medical providers that it could not receive incoming claims files or reach its claims-adjudication system. Its call center was operating, but employees did not have access to every system. Some hospital authorization requirements were temporarily waived. Outpatient requests could be faxed. The provider bulletin described a business forced to replace connected processes with exceptions and workarounds.

The same document contained an important limit: the company had not yet determined whether patient or employee information had been compromised. It knew that a criminal attack had disrupted its technology and phones. It did not yet know the complete informational damage. That gap would persist well beyond the immediate emergency.

The target was a large health-care organization whose network included hospitals, cancer treatment and other clinical services. The Record’s reporting described emergency departments continuing to operate while some surgeries, procedures and non-emergent appointments were canceled or rescheduled. Downtime procedures kept parts of the organization functioning; they did not make the attack inconsequential. The corporation’s disabled systems reached directly into the delivery and administration of care.

By August 26, McLaren said its technology platforms and clinical and administrative operations had been restored. Bridge Michigan reported that clinicians again had electronic medical-record access. But manually charted information still had to be entered into the electronic system, a process expected to take weeks. Restoration therefore had two stages: returning access and reconciling the work accumulated during the outage.

The data investigation ran on a much longer schedule. A company notice preserved by Montana’s Department of Justice said investigators determined that unauthorized access occurred between July 17 and August 3, 2024. McLaren discovered suspicious activity around August 5. The forensic review identifying potentially affected information concluded on May 5, 2025; the notice was dated June 20.

McLaren described an international ransomware group attacking the McLaren and Karmanos Cancer Institute network. It said it had secured the network, brought in specialists and was adding safeguards. The notice also said there was then no evidence of misuse of the recipient’s information. That statement concerned known misuse, not whether unauthorized access had occurred.

The 2024 notification involved 743,131 people, according to the regulatory filing reported by The Record. BleepingComputer’s contemporaneous account highlighted a limitation in the publicly released template: personalized data fields were redacted. The publication also reported a photograph of an alleged INC ransom note. McLaren’s own notice did not name that group. A reported criminal brand is less certain than the company’s acknowledgment that ransomware was involved.

Then came a second accounting problem. McLaren had also suffered a 2023 breach. The ensuing litigation was eventually resolved together, so the settlement’s size cannot honestly be presented as the bill for the 2024 attack alone.

In their motion for final approval, plaintiffs’ lawyers identified 2,793,965 people potentially affected cumulatively by the two incidents. They described a $14 million non-reversionary fund and a negotiated resolution after mediation. The agreement provided a route to claim documented losses up to $5,000, subject to proof and conditions, alongside other settlement benefits. That ceiling was not an automatic award to each person. The lawyers also acknowledged litigation risks, including causation, damages and class certification.

A final court order dated April 21, 2026 granted approval. It certified a class for settlement purposes covering people whose information was compromised in either the 2023 or 2024 breach. Approval resolved the civil claims through agreement; it did not transform every allegation about inadequate security into a trial finding.

The attack’s documented trajectory is consequently more revealing than a single cost estimate. Claims processing stopped. Clinical teams operated through disruption. Electronic access returned. The identification of affected information continued for months, and compensation litigation extended into 2026. A hospital corporation can restart its network while still carrying a much longer obligation to account for what passed through it.

Compiled November 16, 2026. Records and findings keep the dates stated in their sources; each link in the text opens the document it relies on.