DisclosureLens
HackingHealthcareHealthcareData ExfiltratedCustomer Data InvolvedSupply Chain (3P Vendor)PHIIdentity (basic)Government IDHealth (basic)Financial accountMinorMediumContained

AMGEN INC.

bd_0a1537a4d218b7b9 · schema v1 · pii pii-v2

Severity

Medium

Discovered

Jul 2, 2026

Filed

Aug 17, 2026

To disclose

7 weeks

Affected

Not disclosed

Linked

6 filings

Confidence

66%
Full breach record for AMGEN INC.8 incidents on file

Amgen Inc. notified patients of a cybersecurity incident where an unauthorized third party accessed cloud-hosted systems. On July 2, 2026, Amgen became aware of the access. By July 18, 2026, it was confirmed that files containing patient personal information, health information, government IDs, and some financial data were acquired. Amgen engaged forensic experts, contained the incident, and offered 24 months of identity monitoring via Kroll.

Incident timeline

discovery → filing · 7 weeks / 46 days

Jul 2, 2026

Discovered

Aug 17, 2026

Filed

vs. sector median

6 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

Show 1 more filingup to 16d gap

Filing propagation · 6 filings · 5 states

View merged incident ↗
SEC 8-KJul 31 · first
Illinois State AGAug 1 · first
California State AG+16d · this page

Pattern: first filing Jul 31, last Aug 18 (NH) — a 17-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.