Skip to content
cisonews.net

Incident · 8-K Item 8.01; 8-K/A Item 1.05

Stryker reports a global disruption and later files under Item 1.05 citing first-quarter impact

Compiled 2026-09-27 from public records. By the cisonews.net Desk.

Stryker, the medical technology company, disclosed on March 11, 2026 that it had identified a cybersecurity incident that day causing a global disruption to its Microsoft environment. Four weeks later, on April 9, it amended the filing into Item 1.05 after concluding the incident had materially affected operations and first-quarter results.

Initial filing, Item 8.01

At first the company said it had no indication of ransomware or malware.

Updates in March

A March 12 update said order processing, manufacturing and shipping were disrupted, while patient-related services and connected products were not believed affected. On March 23 Stryker revised its earlier view on malware.

Item 1.05 amendment

Stryker said it was fully operational across its manufacturing network and did not expect the incident to materially affect full-year 2026 guidance.

Not disclosed

The filings do not say how the actor got in or whether data was taken.

Sources

  1. 2026-03-11 · AStryker Corporation, Form 8-K (SEC EDGAR), published March 11, 2026
  2. 2026-03-12 · AStryker Corporation, Form 8-K, Item 7.01 (SEC EDGAR), published March 12, 2026
  3. 2026-03-23 · AStryker Corporation, Form 8-K, Item 7.01 (SEC EDGAR), published March 23, 2026
  4. 2026-04-09 · AStryker Corporation, Form 8-K/A, Item 1.05 (SEC EDGAR), published April 9, 2026

Tier A: the organization itself, a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.

See an error? Corrections are made on the page and logged on the corrections page. Send them through contact.