Summary
- Environment: Medical device manufacturing; on-premises IT infrastructure
- Operational impact: Manufacturing, orders, shipping and new remote monitoring activations disrupted; phased recovery reported in September
- Financial impact: Material Q3 and full-year 2026 impact expected; prior sales growth and adjusted EPS guidance unlikely to be met
- Record status: Developing record. Reviewed October 7, 2026; updated as evidence emerges.
What happened
Boston Scientific detected a cyber incident on August 25, 2026. Its initial notice reported a network outage affecting operating systems and business applications. The company disclosed the incident publicly and in an SEC filing on August 26. [2][6]
The outage disrupted product manufacturing, order processing and shipping. New cardiac-device remote monitoring activations were also affected. [5]
Impact
- Manufacturing and order fulfillment were disrupted. Customers could submit electronic orders, but these were queued for later fulfillment. [5]
- New remote monitoring communicators could not be activated. Newly implanted insertable cardiac monitors could record episodes after clinic activation, but could not pair with the patient app for remote transmission; in-person interrogation remained available. [5]
- Boston Scientific reported no impact to implanted cardiac-device function or previously established remote monitoring and clinician access to that data. It also reported no evidence of increased cybersecurity risk to hospital networks using its devices. [4][5]
- In its September 8 Form 8-K, the company said material effects on Q3 and full-year 2026 results were likely and that it was unlikely to meet prior net sales growth and adjusted earnings-per-share guidance. It did not expect a material impact on its long-term financial condition. [2]
- The September 22 investigation update reported no evidence of compromise or data access, staging or exfiltration in the listed cloud, manufacturing-maintenance, development, device-maintenance, HR, benefits and SCADA systems, including customer or patient data in those systems. This finding has a defined scope. [1]
Timeline
Incident detected
The company detected the incident and activated its response.
[6]Order disruption disclosed
The initial update and first SEC filing disclosed the incident.
[2][6]Manufacturing and monitoring impacts described
A company update detailed manufacturing disruption and problems activating new remote monitoring.
[5]Shipping restoration begins
The shipping update said restoration had begun for most products at major global distribution centers. Backlogs remained.
[4]Broader operations resume
The archived recovery update reported manufacturing had resumed at most facilities and all sterilization facilities were operating.
[3]Monitoring restored; financial impact disclosed
A company update confirmed remote monitoring activation was restored. The SEC filing described expected material financial effects.
[2][3]Investigation findings published
The final update summarized CrowdStrike’s conclusions.
[1]Briefing updated
This briefing was last reviewed and updated on October 7, 2026.
Threat Group & Attack Vector
Boston Scientific said CrowdStrike traced access through an external-facing network device into a limited on-premises environment. The notice does not name an exploited vulnerability. [1]
Actors
- No threat actor group is established in the retained notices.
TTPs
- No specific MITRE ATT&CK technique is currently mapped for this case.
Response
The company activated incident response and engaged external investigators. The final update reported no evidence of continuing actor activity after August 25 containment. [1][6]
By September 5, major distribution centers were processing and shipping at or above normal levels, while teams continued reducing backlogs and restoring remaining manufacturing capabilities. Remote monitoring activation was restored by September 8. [3]
The September filing said the full recovery timeline and financial impact remained uncertain. Boston Scientific planned to update its 2026 outlook with its October 28 quarterly results call. [2]