Boston Scientific cyber incident: What happened and what it disrupted

Boston Scientific disclosed on August 26 that it had identified a cybersecurity incident the previous day, August 25, affecting certain information-technology systems. The incident caused a global network outage and disrupted parts of the medical-device company’s operations, including systems and applications used to process customer orders and ship products. 1

The company said it had activated its incident-response procedures, engaged third-party cybersecurity specialists and begun investigating, containing and recovering from the event. But as of the filing, Boston Scientific said the scope, nature, operational effects and financial consequences were still being assessed. 1

What the Boston Scientific cyber incident affected

Boston Scientific did not describe every affected system or identify the attacker in the disclosures provided. It did say that access to certain operating systems and business applications was disrupted or limited. The most concrete business impact was on functions supporting customer-order processing and shipments. 178

The company warned that the disruption was expected to continue while it worked to restore affected systems and functions. It had not provided a timetable for full restoration by August 26. 1411

That distinction matters: the public information confirms an operationally significant incident, but does not yet establish the full extent of delayed orders, missed shipments, manufacturing effects or customer impact.

What happened at the Irish facilities?

Boston Scientific employs more than 7,000 people across its Irish operations in Cork, Clonmel and Galway. Employees were informed about a global network outage affecting communications across the company’s Ireland sites and other locations worldwide. 29

Reports said staff at the Cork plant were sent home and told to work remotely. Galway employees were also told to work from home for the remainder of the day. While reporting confirmed that the three Irish sites were affected by the wider outage, the available public information did not clearly specify a separate, site-specific work arrangement for Clonmel. 3910

How did Boston Scientific respond?

The company said it activated its incident-response protocols as soon as it detected the incident. It brought in external cybersecurity experts to help investigate and contain the threat, while local and global IT teams worked to restore network communications and affected business functions. 1316

As of the August 26 disclosure, the investigation and recovery process was ongoing. Boston Scientific had not said when all systems would be restored, and it had not quantified the operational or financial impact. 114

What did the company say about its financial outlook?

Boston Scientific did not quantify a loss or announce a change to its financial guidance in the disclosure. It said it had not yet determined whether the incident was reasonably likely to have a material effect on the company. 114

The disclosure nevertheless affected investor sentiment. Reports placed the initial share-price decline at about 4% in premarket trading, while a later market report cited a 4.6% fall to $47.57. These figures describe the market reaction at different points in trading rather than a finalized measure of the incident’s financial cost. 818

What risks did Boston Scientific disclose?

Boston Scientific’s filing outlined potential consequences rather than confirming that each had occurred. The risks included:

• prolonged difficulty restoring systems or data;
• inadequate workarounds for affected processes;
• unauthorized release or impairment of confidential or third-party information;
• fraud or criminal misuse of information;
• business interruption and financial harm;
• management distraction and recovery costs;
• litigation and regulatory scrutiny; and
• damage to customer, supplier and employee relationships or to the company’s reputation. 1

At the time of the filing, the company had not publicly confirmed a data breach, specific data theft, ransomware demand or a named threat actor. Those questions remained part of the investigation rather than established facts.

How this compares with other 2026 medtech attacks

The Boston Scientific incident arrived amid a series of cyber events affecting medical-device companies in 2026. Stryker previously reported a global disruption after its Microsoft environment was targeted; reporting said the incident affected ordering, shipping and manufacturing and that recovery continued for weeks. An Iran-linked group claimed responsibility, although that claim does not establish that the same actor was involved in the Boston Scientific incident.

Medtronic’s separate incident had a different reported profile. Security reporting said unauthorized access to certain corporate IT systems exposed personal and medical information relating to approximately 3.8 million people, while products and operations were reported unaffected.

The contrast is important. A cyber incident at a medical-device company can primarily disrupt business continuity, as Boston Scientific reported; it can affect manufacturing and fulfillment, as reported in the Stryker case; or it can create a major data-protection issue without reported product or operational disruption, as in the Medtronic case.

The broader threat environment

Check Point Research reported an average of 2,336 weekly cyberattacks per organization globally in July 2026—3% higher than in June and 16% higher than a year earlier. Separate reporting identified healthcare and medical organizations among the sectors facing elevated risk.

That trend provides context, not proof of a common campaign. The available evidence does not link the Boston Scientific, Stryker and Medtronic incidents to one another or show that they shared an attacker or technique. What it does show is why medical-device companies must treat corporate networks, order systems, manufacturing environments and sensitive health data as connected business risks.

What is still unknown?

As of August 26, the key unanswered questions were:

• when Boston Scientific would fully restore affected systems;
• how many orders or shipments were delayed;
• whether manufacturing or product availability was affected;
• whether confidential or personal data was accessed or exfiltrated;
• whether the incident would materially affect results or guidance; and
• who was responsible and what method was used.

Boston Scientific’s initial filing established the outage and its operational consequences, but not the final scope of the event. Further company updates and regulatory disclosures will be needed before its full business impact can be assessed.