Comparison Overview
HM Insurance Group

HM Insurance Group
501 Penn Avenue, Pittsburgh, PA, 15222, US
Last Update: 02/02/2026
HM Insurance Group (HM) works to protect businesses from the financial risk associated with health care costs. A recognized leader in Employer Stop Loss, the company delivers protection for a range of group sizes. HM also offers assumed accident and health reinsurance s...

Suncorp Group
80 Ann St, Brisbane, 4000, AU
Last Update: 07/09/2026
Suncorp offers insurance products and services through some of Australia and New Zealand’s most recognised brands. Our purpose is to build futures and protect what matters – the focus of our company for more than 100 years. With the passion of our people, and our por...
Compliance Ranges Comparison

HM Insurance Group







Suncorp Group






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

HM Insurance Group

Suncorp Group
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.