Local media in Ireland reported that thousands of staff at Boston Scientific’s Cork campus were sent home Tuesday once network communications were severed across the company. Details like that say more about how serious a cyberattack is than any regulatory paperwork ever will.
The paperwork arrived regardless. The Massachusetts-based medical device maker confirmed in a Wednesday disclosure to the U.S. Securities and Exchange Commission that a cyberattack is behind an ongoing “global disruption” to its operations.
What the company has actually said
By its own account, Boston Scientific started seeing “disruptions and limitations of access” to its IT systems and business applications on Tuesday. Those systems are central to how the company runs.
Shipping and order processing have both been hit, the company said. Left unaddressed is whether the fallout extends to customers who rely on its medical devices and implants.
That silence matters. Pacemakers and defibrillators are among the implanted devices Boston Scientific manufactures, and its website puts the number of patients it treats at roughly 48 million a year.
The questions nobody’s answering
We put three questions to Boston Scientific spokesperson Chanel Hastings: are patients affected, what should patients do, and what kind of incident is this? Hastings passed along the company’s public statement and declined to comment on any part of it.
Per that statement, the investigation remains open and there is no known timeline yet for bringing systems back.
What triggered the attack remains unclear.
Health tech keeps getting hit
Boston Scientific joins a growing list of health technology firms breached this year. Fellow medical device manufacturers Abbott Laboratories and Medtronic were both compromised.
A cyberattack on U.S. medical device maker Stryker earlier this year was pinned on Iranian-backed hackers. Those intruders abused a centralized device management portal supplied by Microsoft to remotely wipe tens of thousands of employee devices across the company’s Windows network.
Worth knowing: public internet records indicate Boston Scientific leans heavily on Microsoft and Amazon Web Services for its corporate infrastructure. That proves nothing about the cause here, but it is the same variety of centralized corporate plumbing that scaled the Stryker breach into a mass-wipe event instead of a contained one.
What to watch next
Anyone carrying a Boston Scientific implant has been told nothing about whether they are affected, and the company refused to say what patients should do. Until that changes, the practical step is taking questions to your clinician rather than waiting on a corporate advisory that may never land.
The shipping backlog is the other figure to follow. Order processing is already down, no restoration timeline exists, and hospitals buy pacemakers and defibrillators on schedules that don’t wait for an incident response to wrap up.