FEDERALItem 1.05 · mandatoryUnknownHealthcareManufacturingManufacturingMedical InstrumentsCustomer Data InvolvedLowActive

STRYKER CORPORATION

bd_e07a8a38defcef8d · schema v1 · pii pii-v1

Severity

Low

Discovered

Mar 11, 2026

Filed

Apr 9, 2026

To disclose

29 days

Affected

Not disclosed

Linked

4 filings

Confidence

67%

Full breach record for STRYKER CORPORATION →6 incidents on file

Stryker Corporation filed an amended 8-K (Amendment No. 1) on April 9, 2026, regarding a cybersecurity incident identified on March 11, 2026. The company determined the incident had a material impact on its operations and Q1 2026 financial results, though not on full-year 2026 guidance. Operations have been restored, but the investigation remains ongoing. No specific attack vector, data types affected, or individual counts were disclosed in this filing.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 29 days

Mar 11, 2026

Discovered

Apr 9, 2026

Filed

vs. sector median

7 wks faster

This filing is one of 4 about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (2)

Leak Sitehandalabd_751e0ea8a9c0d90f2026-03-16 · +24dVerified by operator
Leak Sitehandalabd_d1d4621eed75ab262026-03-11 · +28dVerified by operator

Regulatory filings (1) · sorted by filing gap

SEC 8-Kbd_3ed946969c210ebc2026-03-11 · +29dVerified by operator

Name: STRYKER CORPORATION
norm: stryker
SEC CIK: 0000310764
Domain: stryker.com

Name: STRYKER CORPORATION
norm: stryker
SEC CIK: 0000310764
Domain: stryker.com
Industry: Healthcarenaics mapManufacturingnaics map
NAICS 339112 · Surgical and Medical Instrument Manufacturing

Discovered: Mar 11, 2026
Materiality determined: Apr 9, 2026
Notification sent: —
Affected individuals: Not disclosed
Data types: —
Attack vector: Unknown

During the incident: Worked diligently, together with third-party experts and law enforcement, to contain and neutralize the impact of the incident and restore operations
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 29 days(29 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings

View merged incident ↗

SEC 8-KMar 11 · first

SEC 8-K+29d · this page

Pattern: first filing Mar 11, last Apr 9 — a 29-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statementThis record

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://www.sec.gov/Archives/edgar/data/310764/000119312526149607/d112875d8ka.htm
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Apr 9, 2026
Raw hash: bafcc1869568baf7b3d18cb2f5edf96b32aea495c7be5bc87dc6b04bdbcb2e26

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html45.5 KB

Download View at source

Linked disclosures

Ransomware claims (2)

Regulatory filings (1) · sorted by filing gap

Reporting entitySTRYKER CORPORATION

Victim entitySTRYKER CORPORATION

Incidentdiscovered Mar 11, 2026

Stated responseWorked diligently, together with third-party experts and law enforcement, to contain and neutralize the impact of the incident and restore operations

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancewww.sec.gov

Source filing