AMGEN INC.
bd_0a1537a4d218b7b9 · schema v1 · pii pii-v2
Full breach record for AMGEN INC. →8 incidents on fileAmgen 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.
J jump to incidentP pin to compareR raw source
Incident timeline
Jul 2, 2026
Discovered
Aug 17, 2026
Filed
vs. sector median
6 wks faster
Linked disclosures
Why this link?Regulatory filings (5) · sorted by filing gap
- Vermont State AGbd_14aff9cf710510602026-08-17Verified
- Texas State AGbd_4ed145b595ddfdb32026-08-18 · +1dVerified
- New Hampshire State AGbd_52cbf13bacf252832026-08-18 · +1dVerified
- Illinois State AGbd_77973d7b67ca90fc2026-08-01 · +16dCandidate
Show 1 more filing ↓Show fewer ↑up to 16d gap
- SEC 8-Kbd_e54e82f9afa89d292026-07-31 · +16dVerified
Filing propagation · 6 filings · 5 states
View merged incident ↗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
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.