[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f2fh2rlese9tx0":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"modifiedDate":12,"contentUpdatedAt":12,"source":13,"sourceUrl":14,"sourceUrls":15,"pwnCount":17,"affectedCount":17,"affectedCountStatus":18,"affectedCountLowerBound":17,"affectedCountUnit":19,"hasEnglishDescription":4,"severity":20,"dataClasses":21,"description":23,"seoTitle":24,"seoTitleEn":8,"seoDescription":24,"seoDescriptionEn":25,"logoUrl":26,"isVerified":4,"isSensitive":4,"isSpamList":27,"isMalware":27,"company":28},"6a6f5c199639728846822be8","Amgen2026","Amgen 2026 Data Breach","amgen-2026","amgen.com","2026-07-01T00:00:00.000Z","2026-08-02T15:02:48.536Z","Official SEC disclosure","https:\u002F\u002Fwww.sec.gov\u002FArchives\u002Fedgar\u002Fdata\u002F318154\u002F000031815426000119\u002Famgn-20260729.htm",[14,16],"https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Famgen-says-cloud-data-breach-exposed-patient-health-proprietary-info\u002F",null,"unknown","people","Unknown",[22],"Protected health information","\u003Cp>\u003Cstrong>The Amgen 2026 data breach\u003C\u002Fstrong> concerns unauthorized activity detected in July 2026 in cloud environments hosted by third-party service providers. In an official SEC filing dated July 29, Amgen confirmed that company data and patient protected health information had been exfiltrated from those environments.\u003C\u002Fp>\n\u003Cp>The company did not disclose how many people were affected or the exact incident day. The catalog therefore does not display zero; the count is marked as not disclosed and the date is recorded only with July 2026 month precision.\u003C\u002Fp>\n\u003Ch2>How Was the Amgen Breach Verified?\u003C\u002Fh2>\n\u003Cp>The primary source is Amgen's Form 8-K filed with the U.S. Securities and Exchange Commission. Based on the company's investigation, it confirms both the unauthorized activity and the exfiltration of data that included patient protected health information.\u003C\u002Fp>\n\u003Cp>BleepingComputer independently reported the official disclosure, the affected cloud environments, and the continuing investigation on July 31. It also noted that the service providers, intrusion method, and affected-person count had not been disclosed.\u003C\u002Fp>\n\u003Ch2>What Happened in July 2026?\u003C\u002Fh2>\n\u003Cp>Amgen identified unauthorized activity involving environments hosted by third-party cloud providers. It activated its cybersecurity response plan, implemented containment measures, and engaged independent forensic specialists.\u003C\u002Fp>\n\u003Cp>The official filing says the activity was identified in July 2026 but does not give a day. July 1 is a technical month placeholder in the catalog; it must not be interpreted as the day of initial access, detection, or exfiltration.\u003C\u002Fp>\n\u003Ch2>What Information Was Exposed?\u003C\u002Fh2>\n\u003Cp>Amgen confirmed that the exfiltrated information included proprietary company data, patient protected health information, and other information. The confirmed user-focused data class in this catalog entry is “Protected health information.”\u003C\u002Fp>\n\u003Cp>The company is also assessing whether additional patient information, confidential business information, intellectual property, and research and development data were accessed or taken. Those categories remain under investigation and are not listed as confirmed data classes.\u003C\u002Fp>\n\u003Ch2>How Many People Were Affected?\u003C\u002Fh2>\n\u003Cp>Amgen has not published a count of affected patients, people, files, or records. On July 29, it classified the incident as material because of the volume of potentially affected files and the possibility that they contained sensitive information.\u003C\u002Fp>\n\u003Cp>Because no public count is available, the affected-person field remains empty rather than being filled with zero. Amgen said it was evaluating legal and regulatory notice requirements and would make required notifications, including to impacted patients, based on its findings.\u003C\u002Fp>\n\u003Ch2>What Is the Known Impact?\u003C\u002Fh2>\n\u003Cp>As of the filing date, Amgen said it had found no impact to products, manufacturing operations, financial reporting systems, or its ability to meet patient needs. It also did not expect a material effect on its financial condition or operating results.\u003C\u002Fp>\n\u003Cp>That business-impact assessment does not change the confirmed exfiltration of health information. Health data can support targeted phishing, medical identity fraud, and highly personalized deception, so this incident is treated as sensitive for individuals.\u003C\u002Fp>\n\u003Ch2>What Should Patients and Other Affected People Do?\u003C\u002Fh2>\n\u003Cp>Anyone receiving an incident notice from Amgen should verify which data and service the notice covers and reach support through the company's official domain. Unexpected messages that know health, prescription, insurance, or reimbursement details should not be trusted automatically.\u003C\u002Fp>\n\u003Cp>If a notice confirms account or contact information was involved, change reused passwords, enable multi-factor authentication, and monitor health and insurance accounts. Report unfamiliar medical activity or insurance claims to the relevant provider and insurer through verified channels.\u003C\u002Fp>","","Amgen confirmed that patient health information was exfiltrated from third-party cloud environments; the affected-person count is undisclosed.","https:\u002F\u002Fwww.google.com\u002Fs2\u002Ffavicons?domain=amgen.com&sz=256",false,{"name":29,"sector":30,"country":31,"website":10,"websiteArchiveUrl":24,"websiteStatus":32,"websiteCheckedAt":12},"Amgen Inc.","Healthcare","United States","active"]