All Breaches
July 2, 2026 Verified Medical devices

Cook Medical 2026 Data Breach

The 2026 Cook Medical data breach occurred on July 2, 2026, when an employee was deceived by a social-engineering attempt and gave an outside party access to certain company systems.

33.9 Thousand
Affected People
5
Data Types
Medium
Severity
Oct 9, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

5
  • Business contact information for U.S. and Canadian customers
  • Records of communications with Cook employees in Salesforce
  • Employee names
  • Company email addresses
  • Certain internal business files accessed via SharePoint

About This Breach

The medical-device manufacturer said it identified and quickly contained the unauthorized access on the same day and investigated with support from an outside cybersecurity firm.

The official notice says the information involved primarily comprised business contact information for customers in the United States and Canada; records of customer communications with Cook employees in Salesforce; employee names and company email addresses; and certain internal business files accessed through SharePoint. Cook did not publish a more detailed inventory of the files or fields viewed.

Cook said its review had found no evidence that sensitive or protected data was accessed. It notified customers and employees, provided guidance about watching for follow-on scams, and said it would update them as the investigation progressed. Its products, manufacturing, and ability to serve patients and customers were not affected.

The company did not disclose the number of affected customers or employees, and no unique-record total is available. It also did not state the precise duration of access within that day or how many people had each data element. The notice confirms that information was involved and certain files were accessed, but does not support a conclusion of broader data exfiltration or access to additional systems.

Verification and editorial method

LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.

Report missing or incorrect information