FEDERALItem 1.05 · mandatoryHackingHealthcareHealthcareData ExfiltratedCustomer Data InvolvedSupply Chain (3P Vendor)PHIHealth (basic)IP / systemLowActive

AMGEN INC.

bd_e54e82f9afa89d29 · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Jul 31, 2026

To disclose

—

Affected

Not disclosed

Linked

6 filings

Confidence

66%

Full breach record for AMGEN INC. →8 incidents on file

Amgen Inc. filed an 8-K disclosing a material cybersecurity incident in July 2026 involving unauthorized access to third-party cloud environments. Proprietary data and patient protected health information (PHI) were exfiltrated. The investigation is ongoing, and the company has engaged forensic experts and implemented containment measures. No impact to manufacturing or financial reporting was identified.

J jump to incidentP pin to compareR raw source

SEC clockMateriality determined Jul 29, 2026 → Filed Jul 31, 20262d ✓ SEC 4-day OK

⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

Incident timeline

Jul 1, 2026

Begins

Jul 29, 2026

Scope determined

Jul 31, 2026

Filed

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

Illinois State AGbd_77973d7b67ca90fc2026-08-01Candidate
California State AGbd_0a1537a4d218b7b92026-08-17 · +16dVerified
Vermont State AGbd_14aff9cf710510602026-08-17 · +16dVerified
Texas State AGbd_4ed145b595ddfdb32026-08-18 · +17dVerified

Show 1 more filing ↓up to 17d gap

New Hampshire State AGbd_52cbf13bacf252832026-08-18 · +17dVerified

Name: AMGEN INC.
norm: amgen
SEC CIK: 0000318154

Name: AMGEN INC.
norm: amgen
SEC CIK: 0000318154
Industry: Healthcarellm

Discovered: —
Breach occurred: Jul 1, 2026 – Jul 31, 2026
Materiality determined: Jul 29, 2026
Notification sent: Jul 31, 2026
Affected individuals: Not disclosed
Data types: PHIHealth (basic)IP / system
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1195 Supply Chain CompromiseT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Initial access: supply_chain

During the incident: Activated its cybersecurity response plan
Implemented containment measures
Engaged independent cybersecurity forensic experts
Source: Quoted from the filing itself, not independently verified.

Compliance flags: SEC 4-day OK · 2d
Discovery-date grounding: no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.
Clock breakdown: Statute Window Elapsed Threshold Status
SEC
Materiality determined: Jul 29, 2026
→ Filed: Jul 31, 2026
2d cal. 4 business days SEC 4-day OK

Statute	Window	Elapsed	Threshold	Status
SEC	Materiality determined: Jul 29, 2026 → Filed: Jul 31, 2026	2d cal.	4 business days	SEC 4-day OK

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 5 states

View merged incident ↗

SEC 8-KJul 31 · first · this page

Illinois State AGAug 1 · first

California State AG+16d

Vermont State AG+16d

Texas State AG+17d

New Hampshire State AG+17d

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 filing

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

SEC 8-K / victim statementThis record

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

Source URL: https://www.sec.gov/Archives/edgar/data/318154/000031815426000119/amgn-20260729.htm
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Jul 31, 2026
Raw hash: f3983536dd69c55c552b911a3aee0d01f1418fe61fb60c771084e3bb30151261

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html51.7 KB

Download View at source

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityAMGEN INC.

Victim entityAMGEN INC.

IncidentThird-Party / Supply Chain

Stated responseActivated its cybersecurity response plan

ComplianceSEC 4-day OK

Extraction provenanceno artifact recorded

Source provenancewww.sec.gov

Source filing