Comparison Overview
Amgen Netherlands

Amgen Netherlands
Minervum 7061, Breda, 4817 ZK, NL
Last Update: 25/03/2026
At Amgen, our mission is to serve patients. We dedicate our days to turning the tide on serious, life-interrupting illnesses—pushing the boundaries of science to transform medicine and our focus on the treatment results. Please consult our community guidelines: www.amg...

Eurofins
Val Fleuri 23, Luxembourg, 1526, LU
Last Update: 11/09/2026
Since 1987, Eurofins has grown from one laboratory in Nantes, France to over 65,000 staff across a network of independent companies in 60 countries, operating over 950 laboratories. Performing over 450 million tests every year, Eurofins offers a portfolio of over 200...
Compliance Ranges Comparison

Amgen Netherlands







Eurofins






Benchmark & Cyber Underwriting Signals
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Amgen Netherlands in 2026.
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Eurofins in 2026.
Incident History - Amgen Netherlands (X = Date, Y = Severity)
Amgen Netherlands cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Eurofins (X = Date, Y = Severity)
Eurofins cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Amgen Netherlands

Eurofins
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.