The Cyberattack That Stole Control Instead of Money - Stryker's Story

Stryker lost control without a ransom demand. See what went wrong and how your business can reduce the same risk.
At $25.1 billion in annual revenue and more than 56,000 employees operating across 75 countries, Stryker isn’t just your ordinary organization. It’s a critical pillar of the global healthcare supply chain, and when a company of this scale stumbles, the impact doesn't stay contained.
That is why what unfolded last month can’t be ignored.
In a matter of hours, a cyberattack tore through Stryker’s internal Microsoft environment halting manufacturing, interrupting ordering and shipping, and wiping employee managed devices worldwide. The company’s stock dropped more than three precent the same day, and recovery took more than a week.
There was no ransom demand. No negotiation. No option to pay and restore.
This attack wasn’t about money. It was designed to create operational chaos.
 

What Happened?

On March 11th, 2026, tens of thousands of Stryker managed devices were rendered unusable within hours. Systems were wiped, employees were locked out of their tools, and operations were forced offline across the organization. Manufacturing stopped. Ordering and shipping stalled. The business was effectively paused.
What followed made one thing clear. This was not a routine IT failure or a temporary outage. It was a full-scale operational disruption that exposed deeper gaps in business resilience and preparedness.
That leads to the inevitable question.
How does a Fortune 300 company experience an event of this magnitude?
 

How’d It Happen?

Credential Theft
The attack began with the compromise of administrative credentials, likely achieved through phishing, stolen credentials, or prior access. This type of credential‑based entry is one of the most common initial access vectors observed in large‑scale enterprise incidents.
Privilege Escalation
Once inside the environment, the attackers escalated their access to Global Administrator‑level privileges within Microsoft Entra ID. This level of access granted full control over Microsoft Intune and the broader Microsoft tenant, effectively placing the attackers in the same position as trusted administrators. At this point, traditional defenses were no longer relevant. The attackers were operating with legitimate authority.
Silent Exfiltration
Before executing the destructive phase, the threat actors claimed they exfiltrated approximately 50TB of data. To amplify psychological and reputational impact, this is common for threat actors to exaggerate data theft. However, regardless of the exact volume, investigators confirmed that the attackers were able to operate undetected within the environment for a period of time.
Mass Device Wipe Deployed
Using legitimate Microsoft Intune functionality, the attackers issued remote wipe commands. This resulted in approximately 80,000 to more than 200,000 corporate‑owned and BYO devices being factory reset across 61 countries.
Business Disruption
With employee endpoints wiped and authentication mechanisms rendered unusable, Stryker was forced to pause critical operations. Ordering systems, manufacturing workflows, shipping operations, and internal communications were disrupted simultaneously. The fallout extended beyond Stryker itself. Healthcare providers experienced downstream supply uncertainty, highlighting how deeply interconnected modern business operations have become.
 

What This Event Teaches Every Organization:

The Stryker incident was unique in its scale, but not in its mechanics. The conditions that allowed it to happen exist in many organizations today.
As you read the takeaways below, pause and ask yourself honestly where your organization stands. These are not hypothetical scenarios. They are practical realities that determine how much impact a cyber incident will have when it occurs.
1.   Business Resilience Problem: When systems failed, the consequences were operational. Manufacturing stopped. Orders paused. Decisions slowed. Recovery became a leadership challenge, not a technical one.

If your technology abruptly stopped working, would your organization still know how to operate?

2.   Nation-State Threats Are Real: This attack wasn’t about profit. It was about disruption, signaling, and impact. Private companies were treated as legitimate targets because of what they represent, not something they did wrong.

Are you preparing only for common cybercrime, or for threats that are designed purely to disrupt your business?

3.   Identity Is Our #1 Control: Once privileged identity was compromised, the rest of the environment followed. Tools, devices, and safeguards worked exactly as designed, just in the wrong hands.

Do you truly know who has access to your environment, and what would happen if one set was misused?

4.   Segmentation and Isolation Work: Some parts of the environment recovered faster because they were isolated by design. Others absorbed the full impact.

If something went wrong in one system, how much of your business would feel it?

5.   Business Continuity Plan (BCP) Must Cover Device Destruction: This wasn’t a temporary outage. Devices were wiped permanently. Recovery requires rebuilding, not restoring.

Are your continuity plans built around inconvenience, or around true disruption?

6.   Communication Plans Before Crisis: When core tools disappeared, so did clarity. Confusion costs time, and time compounds damage.

If your primary communication channels went out, would your people know where to turn?

As you reflect on these questions, you may notice a pattern. The greatest risk isn’t a single missing tool or control. It’s the uncertainty of it all. It’s not knowing how your organization would respond when assumptions fail.
If you found yourself hesitating on any of these questions, that isn't failure. It’s opportunity.
The Blackink IT team helps organizations turn real incidents like Stryker into practical preparation. Not fear‑based planning or checklists, but clarity and confidence.
If you’re curious how resilient your organization truly is, schedule a call to walk through the conversation and prepare for the moments that matter most.
 
What You Can Do Now:
Preparation does not require solving everything at once. It starts with a few focused actions that materially improve resilience.
If you want to reduce the impact of a Stryker‑style event, these are the most meaningful first steps.
1.   Run an Incident Response Tabletop Exercise: Bring leadership and IT together to walk through a realistic cyber scenario. Clarify roles, decisions, and communication before pressure is real.
2.   Test Your Backup and Recovery Plan: Confirm what can actually be restored, how long it takes, and what happens if endpoints or identity systems are unavailable.
3.   Complete a Risk Review with Blackink IT: Gain clear visibility into identity risk, segmentation gaps, and operational dependencies so you know where real exposure exists.
4.   Review Your Business Continuity and Disaster Recovery Plan: Make sure your plan assumes permanent device loss and disrupted communication, not just short‑term downtime.

Interested in learning more on keeping your business resilient from cyberattack? Reach out to the cybersecurity experts at Blackink IT, we’re passionate about partnering with organizations to maximize their security, and would love to build a cybersecurity plan that keeps you safe and productive!

Subscribe to the Blackink IT blog

Never miss another article from our technology & cybersecurity experts!
Continue Reading...