A new workspace for radiologists.Discover RAI PACS Pro ↗
RAI PACS Pro

Select your language

Sign inStart free ↗
RAI HEALTH JOURNAL

The Stryker cyberattack: lessons for healthcare continuity

A look back at March 2026: distinguishing corporate disruption, device safety and hospitals’ dependence on suppliers.

← All articles
RAI Health · AI-assisted editorial contentCybersecurity · Medical devices
Server cabinets lining a data centre aisle, with a management terminal showing a blank screen.
Licensed stock photograph illustrating digital infrastructure in healthcare. It does not depict a Stryker facility or a system affected by the attack.
Brett Sayles / Pexels · Pexels License · Image source

Incident and disclosure dates

Stryker experienced corporate network disruption after the cyberattack of 11 March 2026. Its 23 March SEC report records initial disclosures dated 11 and 12 March and clarifies that disruption extended beyond Microsoft systems. This article reviews a past event.

Service impact, device safety and recovery

The manufacturer reported disruption to orders, manufacturing and shipping. On 19 March, it acknowledged some personalised-implant cases had been rescheduled because of shipping delays, while stating that product and device safety were unaffected. Its 1 April update reported an operational global manufacturing network and restored commercial systems. These are dated manufacturer statements, not an independent clinical safety assessment.

Technical cause and data impact: what remains unknown?

The 23 March filing describes a non-propagating malicious file used to execute commands and conceal activity. It does not establish the initial entry method or a verified total for data loss. These sources do not justify describing the event as confirmed ransomware, a compromised implant or proven patient harm.

Defence: limit the reach of administrator access

Microsoft’s Intune guidance emphasises job-scoped administrative permissions, phishing-resistant multifactor authentication and approval by multiple administrators for sensitive actions. These controls aim to limit the impact a central management account can have across device groups. The guidance should not be read as proof of how the initial Stryker intrusion occurred.

Practical preparation for hospitals

HHS ASPR TRACIE connects cyber preparedness with clinical continuity and downtime procedures. Our editorial takeaway: exercises should include a critical supplier losing its ordering or shipping service, as well as a hospital system outage. Agree alternative contact channels, responsible teams and reconciliation procedures for when systems return. This incident review is not advice to change device settings or stop treatment.

Sources

  1. Stryker — Customer Updates: Stryker Network Disruption (March–April 2026) ↗
    Accessed: 2026-10-10
  2. Stryker Corporation — Form 8-K, March 23, 2026 (SEC EDGAR) ↗
    Accessed: 2026-10-10
  3. Microsoft Intune Customer Success — Best practices for securing Microsoft Intune ↗
    Accessed: 2026-10-10
  4. HHS ASPR TRACIE — Topic Collection: Cybersecurity ↗
    Accessed: 2026-10-10

This article is for education and information. Referencing an organization does not imply its endorsement of RAI PACS Pro. This is not a claim of clinical effectiveness for a product or model.

Focus on the image.

Sign in to Pro ↗