AI English summary of an SEC filing — figures as filed
The company said it identified a cybersecurity incident on March 11, 2026, which disrupted its business operations when it occurred. It said it has since worked with third-party experts and law enforcement to contain and neutralize the impact of the incident and restore operations, and that its investigation is ongoing.
Key points
AI summaryThe company said it identified a cybersecurity incident on March 11, 2026, which disrupted its business operations when it occurred. It said it has since worked with third-party experts and law enforcement to contain and neutralize the impact of the incident and restore operations, and that its investigation is ongoing.
The company said it assessed quantitative and qualitative factors that emerged in the weeks after the incident and determined that the incident had a material impact on its operations, with a resulting impact on its financial results for Q1 2026. It said it considered the scope and duration of the operational disruption, the systems affected, and the potential customer and regulatory impacts in reaching that determination.
The company said it believes the incident has not had, and is not reasonably likely to have, a material impact on its 2026 full-year guidance. It also said it is scheduled to report results for the first quarter of fiscal year 2026 on April 30, 2026, where it will discuss its Q1 results and the components of its full-year guidance in further detail.
The company said that as of the date of this amendment (Amendment No. 1), it is fully operational across its global manufacturing network and its commercial, ordering and distribution systems have been restored. This amendment amends the original 8-K report it filed on March 11, 2026.
Summary
AI-writtenAnalysis scope · Filing bodyWe analyzed the filing body and confirmed exhibits. This is not a review of other exhibits, investor presentations or the full earnings call.
Stryker Identifies Cybersecurity Incident on March 11, 2026
The company said it identified a cybersecurity incident on March 11, 2026, which disrupted its business operations when it occurred. It said it has since worked with third-party experts and law enforcement to contain and neutralize the impact of the incident and restore operations, and that its investigation is ongoing.
Source · Based on the filing body and exhibits
Material Operational Impact Affects Q1 2026 Results
The company said it assessed quantitative and qualitative factors that emerged in the weeks after the incident and determined that the incident had a material impact on its operations, with a resulting impact on its financial results for Q1 2026. It said it considered the scope and duration of the operational disruption, the systems affected, and the potential customer and regulatory impacts in reaching that determination.
Source · Based on the filing body and exhibits
Company View on Full-Year Guidance
The company said it believes the incident has not had, and is not reasonably likely to have, a material impact on its 2026 full-year guidance. It also said it is scheduled to report results for the first quarter of fiscal year 2026 on April 30, 2026, where it will discuss its Q1 results and the components of its full-year guidance in further detail.
Source · Based on the filing body and exhibits
Operational Recovery Status as of Amendment Date
The company said that as of the date of this amendment (Amendment No. 1), it is fully operational across its global manufacturing network and its commercial, ordering and distribution systems have been restored. This amendment amends the original 8-K report it filed on March 11, 2026.
Source · Based on the filing body and exhibits
AI summarized the filing and translated the summary into English; it may differ from the original. For reference only, not investment advice. AI translated the published Korean report into English. Figures are copied as filed, not recalculated.
Original filing
The filing as submitted to SEC EDGAR. You can check the figures and statements of this summary against it.
Loading the filing text…