DisclosureLens
FEDERALItem 1.05 · mandatoryHackingHealthcareManufacturingHealthcareData ExfiltratedDelayed DiscoveryMulti-Stage ChainPIIOtherLowActive

BOSTON SCIENTIFIC CORPORATION

bd_576500572de7e15c · schema v1 · pii pii-v2

Severity

Low

Discovered

Aug 25, 2026

Filed

Sep 8, 2026

To disclose

14 days

Affected

Not disclosed

Confidence

67%
Full breach record for BOSTON SCIENTIFIC CORPORATION3 incidents on file

Boston Scientific filed an 8-K on Sept 8, 2026, reporting a cybersecurity incident discovered on Aug 25, 2026. The incident caused a global network outage disrupting manufacturing and shipping. The company activated incident response protocols and engaged third-party experts. No evidence of ongoing unauthorized access was found as of filing, but investigation remains active. Material financial impact expected for Q3 and FY 2026.

SEC clockMateriality determined Sep 7, 2026Filed Sep 8, 20261d SEC 4-day OK14 days discovery → filing
occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

Incident timeline

discovery → filing · 14 days

Aug 25, 2026

Begins

Aug 25, 2026

Discovered

Sep 7, 2026

Scope determined

Sep 8, 2026

Filed

vs. sector median

10 wks faster

Tracked as a single-filing incident — the only disclosure on record for this event so far.ConfirmedView incident

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statementThis record

Unlocks: materiality, stated response, full audit trail. Ceiling removed.