Comparison Overview
The Mistaken Identity Project

The Mistaken Identity Project
N/A
Last Update: 20/03/2026
We're Amazon (not that Amazon), and we've had our share of mix-ups with Amazon.com. So we created the Mistaken Identity Project: stories of everyday people whose names are famous, even if they're not.

Ogilvy
175 Greenwich St, New York, NY, US, 10007
Last Update: 20/09/2026
Ogilvy has been creating impact for brands through iconic, culture-changing, value-driving ideas since the company was founded by David Ogilvy 75 years ago. We build on that rich legacy through Borderless Creativity – innovating at the intersections of its advertising, ...
Compliance Ranges Comparison

The Mistaken Identity Project







Ogilvy






Benchmark & Cyber Underwriting Signals
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for The Mistaken Identity Project in 2026.
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Ogilvy in 2026.
Incident History - The Mistaken Identity Project (X = Date, Y = Severity)
The Mistaken Identity Project cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ogilvy (X = Date, Y = Severity)
Ogilvy cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

The Mistaken Identity Project

Ogilvy
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.