Comparison Overview
MoEngage

MoEngage
315 Montgomery St, San Francisco, California, 94104, US
Last Update: 31/03/2026
MoEngage is an insights-led customer engagement platform for the customer-obsessed marketers and product owners. We help you delight your customers and retain them for longer. With MoEngage you can analyze customer behavior and engage them with personalized communicatio...

Taobao Marketplace
N/A
Last Update: 23/09/2026
Launched in May 2003, Taobao Marketplace (www.taobao.com) is the online shopping destination of choice for Chinese consumers looking for wide selection, value and convenience. Shoppers choose from a wide range of products and services on Taobao Marketplace, which featur...
Compliance Ranges Comparison

MoEngage







Taobao Marketplace






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for MoEngage in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Taobao Marketplace in 2026.
Incident History - MoEngage (X = Date, Y = Severity)
MoEngage cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Taobao Marketplace (X = Date, Y = Severity)
Taobao Marketplace cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

MoEngage

Taobao Marketplace
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.