Comparison Overview
GeneYouIn Inc.

GeneYouIn Inc.
Toronto, M2N 7E9, CA
Last Update: 03/12/2025
Founded in 2012, GeneYouIn, the provider of Pillcheck, helps individuals and their healthcare providers choose the right medications to feel better sooner. Many health plans partner with Pillcheck to bring the positive health impacts of precision medicine to their membe...

Regeneron
777 Old Saw Mill River Road, Tarrytown, 10591, US
Last Update: 06/10/2026
At Regeneron we believe that when the right idea finds the right team, powerful change is possible. As we work across our expanding global network to invent, develop and commercialize life-transforming medicines for people with serious diseases, we’re establishing new w...
Compliance Ranges Comparison

GeneYouIn Inc.







Regeneron






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

GeneYouIn Inc.

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