FEDERALItem 7.01 · voluntary (Reg FD)HackingManufacturingManufacturingDelayed DiscoveryData ExfiltratedLowActive

STRYKER CORPORATION

bd_c87b99b6ff25cc9d · schema v1 · pii pii-v1

Severity

Low

Discovered

Mar 11, 2026

Filed

Mar 12, 2026

To disclose

≤1 day

Affected

Not disclosed

Linked

6 records

Confidence

68%

Full breach record for STRYKER CORPORATION →3 incidents on file

Stryker Corporation filed an 8-K on March 12, 2026, reporting a cybersecurity incident discovered on or about March 11, 2026, that disrupted its Microsoft environment globally. Operations including order processing, manufacturing, and shipping were affected, though patient services and connected products were reportedly unimpacted. The investigation is ongoing, and the full scope and financial impact remain unknown.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · ≤1 day / 1 days

Mar 11, 2026

Discovered

Mar 12, 2026

Filed

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

Linked disclosures

Why this link?

Ransomware claims (2)

Leak Sitehandalabd_751e0ea8a9c0d90f2026-03-16 · +4dVerified by operator
Leak Sitehandalabd_d1d4621eed75ab262026-03-11Verified by operator

Regulatory filings (3) · sorted by filing gap

SEC 8-Kbd_3ed946969c210ebc2026-03-11 · +1dVerified by operator
SEC 8-Kbd_03469b079de9afb32026-03-23 · +11dVerified by operator
SEC 8-Kbd_e07a8a38defcef8d2026-04-09 · +28dVerified 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: Manufacturingllm

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

During the incident: Provided an update to certain of the Company's customers and other members of the cybersecurity community regarding the ongoing cybersecurity incident
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings

View merged incident ↗

SEC 8-KMar 11 · first

SEC 8-K+1d · this page

SEC 8-K+12d

SEC 8-K+29d

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/000119312526104431/d101097d8k.htm
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Mar 12, 2026
Raw hash: d1dfc4d4e49c064ac1bd4df9b05337b3e09e117ed925256a71ecf036ad3ee208

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/html38.4 KB

Download View at source

Linked disclosures

Ransomware claims (2)

Regulatory filings (3) · sorted by filing gap

Reporting entitySTRYKER CORPORATION

Victim entitySTRYKER CORPORATION

Incidentdiscovered Mar 11, 2026

Stated responseProvided an update to certain of the Company's customers and other members of the cybersecurity community regarding the ongoing cybersecurity incident

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancewww.sec.gov

Source filing