Comparison Overview
AREA 23 on Hudson | An IPG Health Company

AREA 23 on Hudson | An IPG Health Company
N/A
Last Update: 16/01/2026
AREA 23 on Hudson, an IPG Health Company, is a team of creative problem-solvers who don’t believe in a cookie-cutter approach to medical communications. Driven by a shared vision with our client partners, we innovate solutions to create lasting impact with HCPs. We do...

Eli Lilly and Company
Lilly Corporate Center, Indianapolis, Indiana, US, 46285
Last Update: 07/10/2026
We're a medicine company turning science into healing to make life better for people around the world. It all started nearly 150 years ago with a clear vision from founder Colonel Eli Lilly: "Take what you find here and make it better and better." Harnessing the power o...
Compliance Ranges Comparison

AREA 23 on Hudson | An IPG Health Company







Eli Lilly and Company






Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for AREA 23 on Hudson | An IPG Health Company in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Eli Lilly and Company in 2026.
Incident History - AREA 23 on Hudson | An IPG Health Company (X = Date, Y = Severity)
AREA 23 on Hudson | An IPG Health Company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Eli Lilly and Company (X = Date, Y = Severity)
Eli Lilly and Company cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

AREA 23 on Hudson | An IPG Health Company

Eli Lilly and Company
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.