Skip to content
cisonews.net

Incident · 8-K Item 1.05

Amgen data breach: patient health information taken from third-party cloud environments, 39,594 people

Compiled from public records. Updated 2026-11-13. By the cisonews.net Desk.

The Amgen data breach affected 39,594 people, the total Amgen Inc reported to Indiana's attorney general for notices sent on August 17, 2026, for a breach dated July 1, 2026. Amgen Inc. told the SEC in a Form 8-K Item 1.05 filing dated July 31, 2026 that unauthorized activity in cloud environments hosted by third-party providers, identified in July 2026, led to data being exfiltrated. The data included proprietary data and patient protected health information; the filing does not say how many people are affected, but Indiana's attorney general records 39,594 people affected in total.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.

What happened at Amgen, and when?

Amgen says it identified the activity in July 2026 and gives no more specific discovery date. The company then activated its cybersecurity response plan, put containment measures in place and hired independent forensic experts.

On July 29, 2026, Amgen decided the incident was material. It tied that decision to the volume of files that appear to have been affected and to the possibility that the information in them is sensitive.

What patient data was taken from Amgen?

The filing names three groups of exfiltrated data: proprietary data, patient protected health information, and other information. It does not list specific data fields such as names or identifiers, and it does not name the cloud providers.

Amgen is still working out the reach of the incident. It continues to assess whether, and to what extent, patient, confidential business, intellectual property, or research and development information may have been accessed, acquired, or exfiltrated.

Did the breach affect Amgen's business?

As of the filing, Amgen reported no identified effect on its products, manufacturing operations, financial reporting systems, or its ability to meet patient needs. It also believes the incident is not reasonably likely to have a material impact on its financial condition or results of operations.

How many people were affected by the Amgen breach?

Indiana's attorney general lists Amgen Inc in its 2026 breach report, with notice sent on August 17, 2026 for a breach that occurred on July 1, 2026: 935 Indiana residents and 39,594 people affected in total. The total is the figure the organization reported to Indiana.

How many Texans were affected?

Texas's attorney general lists a report from Amgen Inc., published on its website on August 18, 2026, with 6,714 Texans affected. That figure counts Texas residents only; the public list gives no national total.

How many Massachusetts residents were affected?

Massachusetts' Office of Consumer Affairs and Business Regulation lists a report from Amgen Inc. dated August 18, 2026 (breach 2026-1386): 354 Massachusetts residents affected. The categories it marks as breached are Social Security numbers and medical records. That count covers Massachusetts residents only.

What do Amgen's later filings say?

So far, nothing specific. Amgen has not amended the July 31, 2026 8-K, and its two quarterly reports since then do not name the July incident. The 10-Q filed on August 5, 2026, five days after the 8-K, discusses breaches at third-party service providers in its risk factors and gives a November 2025 vendor incident as its example. The same passage says supplier data breaches have not had material adverse effects on the business. The 10-Q for the quarter ended September 30, 2026, filed on November 4, 2026, does not mention cybersecurity at all.

FiledFilingWhat it says about the July 2026 incident
July 31, 2026Form 8-K, Item 1.05Cloud environments at third-party providers; proprietary data and patient PHI exfiltrated
August 5, 2026Form 10-Q, quarter ended June 30, 2026Not named; cites a November 2025 vendor incident as an example
November 4, 2026Form 10-Q, quarter ended September 30, 2026Nothing

The next place to look is Item 1C of Amgen's annual report for 2026. The guide to what later 10-Qs and 10-Ks report shows how other companies answered there.

What is still unknown?

Amgen says it is still weighing its notification duties and will notify affected patients where required, but the filing sets no notification date, no letter details, and no offer of services to patients.

The company states that the investigation is ongoing and that it will amend the report when missing Item 1.05 information is determined or becomes available. No amended filing is on record here.

The rule behind an Item 1.05 filing

Form 8-K Item 1.05 is where a public company reports a cybersecurity incident it has determined to be material. Under the rule the SEC adopted on July 26, 2023, the filing is generally due four business days after the company determines that the incident is material. Source: U.S. Securities and Exchange Commission, press release 2023-139. The guide What is SEC Form 8-K Item 1.05, and what counts as a disclosed cyber incident? reads the rule in full, and the glossary defines Form 8-K Item 1.05.

Other life sciences & medical devices incidents on cisonews.net

All life sciences & medical devices incidents

Sources

  1. 2026-11-05 · AIndiana Attorney General, data breach year-to-date report (2026), published November 5, 2026
  2. 2026-07-31 · AAmgen Inc., Form 8-K (SEC EDGAR), published July 31, 2026
  3. 2026-11-06 · ATexas Attorney General, data security breach reports, published November 6, 2026
  4. 2026-08-05 · AAmgen Inc., Form 10-Q for the quarter ended June 30, 2026 (SEC EDGAR), published August 5, 2026
  5. 2026-11-04 · AAmgen Inc., Form 10-Q for the quarter ended September 30, 2026 (SEC EDGAR), published November 4, 2026
  6. 2026-11-09 · AMassachusetts Office of Consumer Affairs and Business Regulation, 2026 Data Breach Notification Report, published November 9, 2026
  7. 2023-07-26 · AU.S. Securities and Exchange Commission, press release 2023-139, published July 26, 2023

Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.