One linked filing — more sources may join as they report · filed Jul 31, 2026. View entity profile → Other incidents for this victim →
incident inc_9e790fa1fa244160 · merge_method deterministic
Materiality determination to SEC 8-K filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · Filing span — no leak-site claim in this cluster; needs two dated filings.
PHI · Health (basic) · IP / system
FEDERAL
all SEC 8-K
Earliest sighting first · deep chronology in Litigation Timeline
Jul 1, 2026 → Jul 31, 2026
When the intrusion reportedly occurred, per the linked filings
Jul 29, 2026
Registrant determined the incident material — starts the SEC 4-business-day clock
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
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.