HackingHealthcareManufacturingHealthcareVulnerability ExploitCapture Stored DataData ExfiltratedCustomer Data InvolvedSupply Chain (3P Vendor)Identity (basic)Government IDMediumContained

BRISTOL-MYERS SQUIBB COMPANY

bd_333dbf505a7fad0d · schema v1 · pii pii-v1

Severity

Medium

Discovered

May 31, 2023

Filed

Jul 3, 2023

To disclose

5 weeks

Affected

5state residents only

Linked

4 filings

Confidence

66%

Full breach record for BRISTOL-MYERS SQUIBB COMPANY →7 incidents on file

Bristol Myers Squibb notified New Hampshire AG of a MOVEit vulnerability exploitation. Unauthorized access occurred as early as May 27, 2023. Data of 5 NH residents, including SSNs and names, was exfiltrated. BMS engaged law enforcement, patched the vulnerability, and offered 24 months of credit monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 4 days

discovery → filing · 5 weeks / 33 days

May 27, 2023

Begins

May 31, 2023

Discovered

Jun 1, 2023

Scope determined

Jul 3, 2023

Filed

vs. sector median

7 wks faster

This filing is one of 4 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (3) · sorted by filing gap

Massachusetts State AGbd_fd0e0b317e579e4b2023-07-05 · +2dVerified
Washington State AGbd_c7f73efea8f4322f2023-06-30 · +3dCandidate
Montana State AGbd_27d9a6315eb19d822023-06-29 · +4dVerified

Name: BRISTOL-MYERS SQUIBB COMPANY
norm: bristol myers squibb
Domain: bms.com

Name: BRISTOL-MYERS SQUIBB COMPANY
norm: bristol myers squibb
Domain: bms.com
Industry: HealthcarellmManufacturingllm

Discovered: May 31, 2023
Breach occurred: May 27, 2023
Undetected for: 4 daysoccurrence → discovery
Materiality determined: Jun 1, 2023
Notification sent: Jun 29, 2023
Affected individuals: 5state-resident count only
Data types: Identity (basic)Government ID
Data elements: Social Security numberDate of birth
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: Engaged U.S. law enforcementNotified data protection authorities, where applicable
Initial access: exploit_public_facing

During the incident: Initiated an investigation with the assistance of third-party cybersecurity experts
Implemented vendor-recommended actions
Engaged U.S. law enforcement
Took the application offline
Notified data protection authorities, where applicable
Promptly patched the vulnerability
Changes made: Working to further enhance its security controls
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 5 weeks(33 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

Montana State AGJun 29 · first

Washington State AG+1d

New Hampshire State AG+4d · this page

Massachusetts State AG+6d

Pattern: first filing Jun 29 (MT), last Jul 5 (MA) — a 6-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

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 filingThis record

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

SEC 8-K / victim statement

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

Source URL: https://mm.nh.gov/files/uploads/doj/remote-docs/bristol-myers-squibb-20230703.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jul 3, 2023
Raw hash: ab2c020f089bbcad54a73bab1d55e864656860b39a611fac668fe9a8e3caded3

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entityBRISTOL-MYERS SQUIBB COMPANY

Victim entityBRISTOL-MYERS SQUIBB COMPANY

Incidentdiscovered May 31, 2023

Stated responseInitiated an investigation with the assistance of third-party cybersecurity experts

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov