Skip to content
Baker Capital StrategiesMARKETS. FILINGS. PERSPECTIVE.
Powered by THEMA

BAKER CAPITAL STRATEGIES

Get the free weekly BCS email.

Selected company filings and market updates, delivered by email. Your first report will follow soon.

  • Your weekly BCS reportMarket updates and links to filings you can explore.
  • THEMA at launchWe’ll send directions for setting up your filing alerts when THEMA officially opens.

One signup for the weekly email and your free THEMA Basic account at launch.

Already registered or a CSW member?Log in to THEMA →

At least 8 characters. This also creates your free THEMA account for launch.

You’re signing up for the weekly BCS email and THEMA launch/setup updates. Unsubscribe using the link in any email. Privacy policy · Terms

BCS

Current Report · Items 7.01, 9.01 · 8-K

Stryker Corporation

SYKNYSEEQUITYCurrent

Regulation FD Disclosure

Item 7.01 Regulation FD Disclosure. As previously reported in two separate Current Reports on Form 8-K, filed with and furnished to (as the case may be) the U.S. Securities and Exchange Commission (the “SEC”) on March 11, 2026, and March 12, 2026, respectively, Stryker Corporation (the “Company”) disclosed that the Company had identified a cybersecurity incident.…

Filed Mar 23, 2026Accepted Mar 23, 2026, 8:30 AM EDTCIK 310764Accession 0001193125-26-118634
Share

Company context

Stryker is a global leader in medical technologies and, together with our customers, we are driven to make healthcare better. We offer innovative products and services in MedSurg, Neurotechnology and Orthopaedics that help improve patient and healthcare outcomes. Alongside our customers around the world, we impact more than 150 million patients annually. More information is available at www.stryker.com.

Current securities

Recent company filings

  1. Departure of Directors or Certain Officers; Election of Directors; Appointment of Certain Officers; Compensatory Arrangements · Regulation FD DisclosureOct 6, 2026
  2. 4 filingSep 2, 2026
  3. 4 filingAug 18, 2026
  4. 144 filingAug 18, 2026
  5. 144 filingAug 17, 2026

Disclosure sections

Items 7.01, 9.01

Select an item to read the extracted section. The as-filed document remains the primary evidence.

Item 7.01Item 7.01 - Regulation FD Disclosure
Item 7.01 Regulation FD Disclosure. As previously reported in two separate Current Reports on Form 8-K, filed with and furnished to (as the case may be) the U.S. Securities and Exchange Commission (the “SEC”) on March 11, 2026, and March 12, 2026, respectively, Stryker Corporation (the “Company”) disclosed that the Company had identified a cybersecurity incident. Since then, the Company has worked around the clock, together with third-party experts and law enforcement to contain and neutralize the impact of the cyber incident and restore operations. Since then, the Company has been providing updates to its customers, suppliers, vendors and partners on its ongoing investigation through the Company’s website and its social media channels. The information included in this report is a further update on the status of its ongoing investigation, which is also being communicated to its customers, suppliers, vendors, and partners through its website. Early in the Company’s investigation and based on the information it had at that time, management believed that the incident did not involve ransomware or malware. Further into the course of its investigation alongside Palo Alto Networks’ Unit 42 and other experts, the Company was able to identify that while the threat actor used a malicious file to run commands which allowed it to hide its activity while in its systems, this file was not capable of spreading - either inside or outside of the Company’s environment. As of the date of this report, the Company’s investigation has not identified malicious activity directed towards its customers, suppliers, vendors or partners. The Company has continued to learn more alongside its third-party advisors, including those at Palo Alto Networks Unit 42. Their latest findings are included in a General Assurance letter, which is attached hereto as Exhibit 99.1 and can also be found on the Company’s website at Stryker.com. This letter reaffirms the Company’s belief that this incident is contained and that the current analysis has not identified any evidence of the threat actor accessing customer, supplier, vendor and partner systems as a result of this incident. The Company has also posted a statement on its website at Stryker.com which is attached hereto as Exhibit 99.2. As its investigation is ongoing, the Company will continue to update its customers, suppliers, vendors and partners through its website disclosures, which updates will supersede previously made website reports. For example, the Company’s website reports have been updated to reflect that the cybersecurity incident caused disruption to the Company’s corporate network environment, including but not limited to the Microsoft environment. The Company’s investigation of the cybersecurity incident is ongoing, and the scope, nature and impact, including, but not limited to operational and financial impact, of the incident continue to be assessed and re-evaluated. Accordingly, the Company has not yet determined whether the incident is reasonably likely to have a material impact on the Company. The information furnished in this report, including Exhibits 99.1 and 99.2, shall not be deemed “filed” for purposes of Section 18 of the Securities Exchange Act of 1934, as amended (the “Exchange Act”), or incorporated by reference in any filing under the Securities Act of 1933, as amended, or the Exchange Act, except as shall be expressly set forth by specific reference in such filing. Caution Concerning Forward-Looking Statements This Current Report on Form 8-K contains forward-looking statements subject to the safe harbor protection provided by Section 27A of the Securities Act of 1933, Section 21E of the Securities Exchange Act of 1934, and the Private Securities Litigation Reform Act of 1995. All statements other than statements of historical fact are forward-looking statements, including statements regarding the Company’s current beliefs regarding the extent of the cybersecurity incident and the results or findings of the Company’s investigation thereof; the Company’s ability to contain and/or mitigate the incident; the disruption to our business or operations; and the potential impact on the Company’s reputation, financial condition and results of operations. These forward-looking statements involve known and unknown risks, uncertainties and other important factors that may cause actual results to differ materially from expectations as of the date of this filing. Factors that could cause actual results to differ materially from those indicated in the forward-looking statements include, but are not limited to, any impairment of the integrity of the Company’s systems or data; delays or difficulties in restoring the Company’s systems and data; the Company’s continued ability to use alternatives to its systems, to the extent needed; the Company’s ability to process information it collected while using alternatives to its systems and the integrity of that information; the adequacy of processes during the period of disruption of the Company’s systems; the results of the Company’s analysis of the scope and details of the cybersecurity incident; the unauthorized release of any of the Company’s data, including third party data held by the Company, or the use of any such data for any fraudulent purposes; potential adverse impact of the incident on the Company’s results of operations, including revenue, operating income and cash flows from operations, and on its financial condition, including liquidity; diversion of management’s attention from operations of the Company to address the cybersecurity incident; potential litigation related to the cybersecurity incident; potential adverse effects on relationships with customers, suppliers, patients and other third parties as a result of the cybersecurity incident; reputational risk related to the cybersecurity incident; regulatory scrutiny as a result of the cybersecurity incident; and other risks listed or described from time to time in our filings with the SEC, including our Annual Report on Form 10-K and Quarterly Reports on Form 10-Q that we have filed or will file hereafter. Except as required by applicable law, we disclaim any intention or obligation to publicly update or revise any forward-looking statement to reflect any change in our expectations or in events, conditions or circumstances on which those expectations may be based, or that affect the likelihood that actual results will differ from those contained in the forward-looking statements.
Filed exhibits (2)
EX-99.1 (by filename) d94012dex991.htm

EX-99.1 2 d94012dex991.htm EX-99.1 EX-99.1 Exhibit 99.1 March 20, 2026 Stryker Corporation Att: David Nathans, Vice President, Chief Information Security Officer Subject: Stryker Corporation Partner and Customer Connections to the Stryker Environment Mr. Nathans, Per your request, Palo Alto Networks Unit 42 hereby issues this letter as a status update on Unit 42’s services assisting Stryker Corporation (Stryker) to provide, at your direction, Digital Forensics and Incident Response (DFIR) services in relation to a security compromise involving impacts to Stryker’s Entra ID environment, servers, and workstations (“Security Incident”). Scope of Work As part of the completed activities for this engagement, Unit 42 has worked with Stryker’s technical teams to perform the following: Threat Hunting & Forensic Analysis: Conducted deep-dive analysis of endpoint forensic images, network logs, and identity infrastructure (including Entra ID/Active Directory) to identify indicators of compromise (IOCs) and evidence of unauthorized access. Containment & Eradication: Identified and neutralized suspected malicious binaries and unauthorized persistence mechanisms. …

Open exhibit ↗
EX-99.2 (by filename) d94012dex992.htm

EX-99.2 3 d94012dex992.htm EX-99.2 EX-99.2 Exhibit 99.2 Customer Update: Stryker Network Disruption 03/23/2026 Our internal teams continue to work around the clock with external partners to make meaningful progress on our restoration efforts. We are grateful for the partnership and collaboration with government agencies and industry partners. We believe the incident is contained, and we are prioritizing restoration of systems that directly support customers, ordering and shipping. Our internal teams, in partnership with third-party experts, reacted quickly to not only regain access but to remove the unauthorized party from our environment. Early in our investigation, we believed there was no indication of ransomware or malware. Further into the course of our investigation, alongside Palo Alto Networks Unit42 and other experts, we identified that the threat actor used a malicious file to run commands which allowed them to hide their activity while in our systems. To be clear, this file was not capable of spreading - either inside or outside of our environment. Most importantly, at no point has our investigation identified malicious activity directed towards our customers, …

Open exhibit ↗

Privacy choices

BCS measures page use with Google Analytics using regional consent settings. You can change your preference here. Charts and market data remain available.

Essential functions — always available. Security, navigation, registration and remembering these choices.

Audience analytics

Analytics cookies are off by default for visitors Google identifies in the EEA, UK or Switzerland until allowed. Limited measurement without analytics cookies may still occur under those regional defaults.

TradingView charts, quotes and the economic calendar load automatically as page content. TradingView receives network and browser information and may collect its own usage analytics. This choice controls BCS’s Google Analytics only.

Google advertising is not enabled. Direct sponsor links do not load advertising trackers on BCS.

Turning analytics off stops future Google Analytics activity here. It does not erase information already received by the provider. Read the privacy policy.