Latest / Federal (SEC) / March 2026
STRYKER CORP
STRYKER CORP notified SEC Form 8-K on Mar 23, 2026 of a data breach, which occurred on Mar 11, 2026.
All 4 filings by STRYKER CORP, state by state · Case file (dates, days to notice against the statute, what the letter offers, prior incidents)
- Organization
- STRYKER CORP
- Source
- SEC Form 8-K · source record
- Date reported
- Mar 23, 2026
- Date(s) of breach
- March 11, 2026
- Residents affected
- Not published by this source
- Data exposed
- Not stated in the source listing
- Notice letter
- Form 8-K filing
- Days to notice
- 12 days from the end of the breach window (Mar 11, 2026, no discovery date in the letter) to the Federal (SEC) record (Mar 23, 2026).
- Third party
- The letter attributes the incident to a vendor or service provider
- First seen by BreachTally
- 2026-11-12 23:17 UTC
- Ticker
- SYK
Dates and counts as filed by the organization with the agency. The breach window and the report date often differ by months.
Item 7.01 excerpt
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
Other filings by STRYKER CORP
| Organization | State | Reported | Residents affected |
|---|---|---|---|
| STRYKER CORP Item 1.05 Material Cybersecurity Incidents. As previously disclosed in the Original Report and as further reported on two... |
US | Apr 9, 2026 | Not published |
| STRYKER CORP Item 7.01 Regulation FD Disclosure. As previously reported on March 11, 2026, Stryker Corporation (“we” or the “Company”) identified a cyber... |
US | Mar 12, 2026 | Not published |
| STRYKER CORP Item 8.01 Other Events. On March 11, 2026, Stryker Corporation (“we” or the “Company”) identified a cybersecurity incident affecting certain... |
US | Mar 11, 2026 | Not published |
Data reproduced from a public government filing. Spot an error? Email support@breachtally.com with the record link. Corrections are applied and noted.