---
title: "Bausch Health company-records incident"
description: "Bausch Health reported unauthorized company-record access from June 24 to July 1, 2026, followed by findings that names and contact information were acquired."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-11-21"
canonical_url: "https://www.ally.security/incidents/bausch-health-company-records-incident-2026"
markdown_url: "https://www.ally.security/incidents/bausch-health-company-records-incident-2026.md"
stix_url: "https://www.ally.security/incidents/bausch-health-company-records-incident-2026/stix.json"
---

# Bausch Health company-records incident

Bausch Health reported unauthorized company-record access from June 24 to July 1, 2026, followed by findings that names and contact information were acquired.

Last modified Nov 21, 2026 · 2 sources

## Summary

- **Environment:** Company records
- **Operational impact:** Personal information acquired; total affected population undisclosed
- **Financial impact:** No confirmed incident cost quantified

## What happened

[Bausch Health Companies Inc.](https://www.bauschhealth.com/) detected unauthorized access to company records on July 1, 2026. Its investigation placed the access between June 24 and July 1. [2](#source-2)

## Impact

On October 28, its review identified acquisition of names and contact information. An additional data field is blank in the public sample, so further categories remain unspecified. [2](#source-2)

The notice does not establish a global affected-person count or a quantified incident cost. [2](#source-2)

## Timeline

### June 24, 2026 — Access window begins

The investigation identified this as the start of unauthorized access. [2](#source-2)

### July 1, 2026 — Unauthorized access detected

This was also the end of the identified access window. [2](#source-2)

### October 28, 2026 — Data acquisition identified

The review identified affected personal information. [2](#source-2)

### November 21, 2026 — Briefing updated

This briefing was last reviewed and updated on November 21, 2026.

## Threat Group & Attack Vector

The notice does not identify the attacker or explain how access was gained. [2](#source-2)

### Actors

- No threat actor identity is established in the reviewed evidence.

### TTPs

- No specific MITRE ATT\&CK technique is mapped for this case.

## Response

Bausch Health engaged incident-response specialists, hardened systems and cooperated with law enforcement. [2](#source-2)

California recorded the sample notice filing on November 20, 2026. [1](#source-1)

The sample bears a future November 25, 2026 letter date; it does not establish that mailing had already occurred. [2](#source-2)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/bausch-health-company-records-incident-2026/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### California data breach notification register

regulatory · California Department of Justice

<https://oag.ca.gov/privacy/databreach/list-export>

<a id="source-2"></a>

### Bausch Health sample notification filed November 20, 2026

official · Bausch Health Companies Inc. · Nov 20, 2026

<https://oag.ca.gov/system/files/INDIVIDUAL%20LTR%20SAMPLES%20ATTACHMENT.pdf>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   Data acquisition identified: The review identified affected personal information.
2. **Resulted In · 100% confidence · current**  
   Bausch Health company-records breach: The notice does not establish a global affected-person count or a quantified incident cost.
3. **Affected Organization · 100% confidence · current**  
   Bausch Health company-records breach: Bausch Health Companies Inc.
4. **Resulted In · 100% confidence · current**  
   Bausch Health company-records breach: Bausch Health Companies Inc. detected unauthorized access to company records on July 1, 2026. Its investigation placed the access between June 24 and July 1.
5. **Resulted In · 100% confidence · current**  
   Unauthorized access detected: This was also the end of the identified access window.
6. **Occurred At · 100% confidence · current**  
   Data acquisition identified: 2026-10-28
7. **Resulted In · 100% confidence · current**  
   Bausch Health company-records breach: Bausch Health engaged incident-response specialists, hardened systems and cooperated with law enforcement.
8. **Occurred At · 100% confidence · current**  
   Unauthorized access detected: 2026-07-01
9. **Resulted In · 100% confidence · current**  
   Bausch Health company-records breach: Access window begins
10. **Occurred At · 100% confidence · current**  
   Access window begins: 2026-06-24
11. **Resulted In · 100% confidence · current**  
   Bausch Health company-records breach: Unauthorized access detected
12. **Resulted In · 100% confidence · current**  
   Bausch Health company-records breach: On October 28, its review identified acquisition of names and contact information. An additional data field is blank in the public sample, so further categories remain unspecified.
13. **Resulted In · 100% confidence · current**  
   Bausch Health company-records breach: California recorded the sample notice filing on November 20, 2026.
14. **Resulted In · 100% confidence · current**  
   Bausch Health company-records breach: Data acquisition identified
15. **Resulted In · 100% confidence · current**  
   Bausch Health company-records breach: The notice does not identify the attacker or explain how access was gained.
16. **Resulted In · 100% confidence · current**  
   Access window begins: The investigation identified this as the start of unauthorized access.
17. **Resulted In · 100% confidence · current**  
   Bausch Health company-records breach: The sample bears a future November 25, 2026 letter date; it does not establish that mailing had already occurred.

</details>
