whogothacked

Boston Scientific Corp. cybersecurity incident record

What is on record for Boston Scientific Corp.?

There is one cybersecurity incident disclosed under Item 1.05 of Form 8-K on record for Boston Scientific Corp., disclosed to the SEC on September 8, 2026.

Disclosed to the SEC on Form 8-K.

How many
No source on record gives a number.
Data listed
Not itemized. The description quoted below may name the data involved.
Source record
Open this record at sec.gov
What to do
If you received a notice letter, start with the letter: keep it, use any free monitoring it offers, and check that the letter is real.

Get a daily email of new incidents

Email alerts

We use your address only for these alerts and to run and test the service (privacy). Want only SEC filings? Sign up on the alerts page.

Also filed as
BOSTON SCIENTIFIC CORP
Sector
Surgical & Medical Instruments & Apparatus
State
Massachusetts
Ticker
BSX as of its latest SEC filing on record (shown to identify the company; nothing on this page is investment advice)

Was Boston Scientific Corp. hacked?

Boston Scientific Corp. disclosed a cybersecurity incident in a Form 8-K under Item 1.05, first filed on September 8, 2026.

The company's Form 8-K filing describes what happened in its own words. That description is quoted with the incident below.

A filing shows who notified the regulator. The filer is sometimes a vendor or a customer of the firm whose systems were affected, so a filing on its own does not establish whose systems were broken into.

The incident on record

Form 8-K Item 1.05 filed with the SEC

Official record

1 source record

Boston Scientific Corp. filed a Form 8-K under Item 1.05 (Material Cybersecurity Incidents) disclosing a cybersecurity incident to the US Securities and Exchange Commission on September 8, 2026.

The record behind this entry

  1. First record

    Form 8-K Item 1.05 filed with the SEC under the name BOSTON SCIENTIFIC CORP.

    In the company's own words, from its Form 8-K under Item 1.05 (Material Cybersecurity Incidents)

    As previously disclosed in a Current Report on Form 8-K filed on August 26, 2026 with the Securities and Exchange Commission, on August 25, 2026, Boston Scientific Corporation (the “Company”) identified a cybersecurity incident that affected certain of its information technology systems and resulted in a global disruption to the Company’s operations.

    Show the rest of this text (378 more words)Hide the rest of this text

    Upon detection, the Company activated its incident response protocols, and since then has been working, with the assistance of third-party cybersecurity experts, to investigate, assess and contain the impact of the incident and to restore operations.

    The incident involved unauthorized activity on certain of the Company’s systems that resulted in a network outage affecting access to certain operating systems and business applications, which impacted the Company’s ability to manufacture as well as process and ship customer orders. As of the date of this Current Report on Form 8-K, the Company has not identified evidence of ongoing unauthorized access to its systems. The Company’s investigation of the incident remains ongoing.

    The Company continues to make progress in restoring many of the affected systems, including substantial restoration of its distribution network, with major distribution centers now processing and shipping customer orders at or above normal operating levels. Additionally, the Company’s sterilization facilities are now operational and manufacturing has resumed across most facilities globally. While the timeline for a full operational recovery is uncertain, the Company continues to work diligently to fully restore all affected systems.

    Based on the information currently available as of the date of this Current Report on Form 8-K, the Company has determined that the incident is likely to have a material impact on the Company’s results of operations for the third quarter and full year 2026. As a result, the Company believes that it is unlikely to meet the net sales growth and adjusted EPS guidance ranges for the third quarter and full year 2026 that the Company previously provided on July 29, 2026. The Company anticipates recovering some portion of the impacted revenue as it continues to ramp operations globally, fulfill customer orders and reduce remaining backlogs, however the full impacts are not yet known. The Company intends to provide an update on its operational and financial outlook for the remainder of fiscal year 2026, incorporating the anticipated impact of the incident, during its planned conference call to discuss financial results and business highlights for the third quarter 2026 to be held on Wednesday, October 28, 2026. As of the date of this Current Report on Form 8-K, the Company does not expect the incident will have a material impact on its long-term financial condition.

What to do if this involved you

This entry has no itemized list of the kinds of data involved. The description quoted above may name them, and a notice letter, if you received one, is the place to look. What to do with a notice letter

If you received a notice letter

  • Keep the letter

    It names the incident and lists which of your details were involved. The letter, not this page, is the authority on what happened to your data.

  • Use any free monitoring it offers

    Many notices include free credit monitoring with an enrollment code and a deadline. Enroll using the instructions printed in the letter, not a link from an email or text.

  • Check that the letter is real

    Compare it with the source records linked on this page. If you are unsure, contact the organization using a phone number or address from its own website, not one printed in a message you were sent.

  • If your identity is misused, report it

    The Federal Trade Commission's IdentityTheft.gov gives you a recovery plan and the forms to send.

    Report identity theft at IdentityTheft.gov

About this record

Official record: A regulator filing or the organization's own disclosure exists.

Being on record here is not a finding that Boston Scientific Corp. did anything wrong or broke any law. This page reports what the source records say, and no more.

Every fact on this page comes from the source records linked above. The steps for people who received a letter are general guidance, not part of the record. How records are verified

Something wrong here? See how to dispute an entry, or write to corrections@whogothacked.com.

The same record for software: /api/v1/orgs/boston-scientific-corp