Medtech Insight published an analysis November 11 arguing that none of 2026's corporate cyberattacks on device makers reached an actual medical device, and that this may be the point rather than a relief. The piece opens with a Stryker executive, Spencer Stiles, describing the morning he got the call, then widens out to a yearlong pattern across the industry.

The timeline runs long. Medtronic disclosed a corporate IT breach in April. Abbott's cancer diagnostics unit was hit in July, the same month Cook Medical disclosed a phishing incident and Baylor Genetics confirmed a breach of its own. Stryker and Boston Scientific both had cyberattacks disrupt manufacturing and order fulfillment over the summer, severe enough that each company cut its 2026 financial guidance by late October.

A security executive the piece identifies as Saunders argues the attackers behind these breaches are not necessarily after the same thing twice. A ransomware crew wants a payout and moves on. A nation-state actor that gets the same foothold inside a device maker's network can instead spend time studying build systems, update pipelines and supplier relationships, looking for how a connected device actually gets designed, built and shipped.

Treat a corporate breach at a device maker as reconnaissance until proven otherwise. An incident response plan that only asks whether patient data left the building is answering last year's question.

Most devices in the field still run compiled C and C++, a detail the piece raises in passing while noting that newer designs are starting to look at Rust. None of 2026's publicized breaches have been tied to a change in a shipped device's firmware or an actual patient-facing product. The piece's point is that the industry's margin for assuming that stays true gets thinner with every incident added to the list.