Comparison Overview
YTL Power International

YTL Power International
Menara YTL, 205 Jalan Bukit Bintang, Bukit Bintang, 55100, MY
Last Update: 04/12/2025
YTL Power International Berhad [199601034332 (4066684-H)] is an international multi-utility owner and operator, active across key segments of the utilities industry, with operations, investments and projects under development in Malaysia, Singapore, the United Kingdom, ...

Dominion Energy
120 Tredegar Street, Richmond, VA, US, 23219
Last Update: 09/10/2026
Dominion Energy (NYSE: D), headquartered in Richmond, Va., provides regulated electricity service to 3.6 million homes and businesses in Virginia, North Carolina, and South Carolina, and regulated natural gas service to 500,000 customers in South Carolina. The company i...
Compliance Ranges Comparison

YTL Power International







Dominion Energy






Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for YTL Power International in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Dominion Energy in 2026.
Incident History - YTL Power International (X = Date, Y = Severity)
YTL Power International cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dominion Energy (X = Date, Y = Severity)
Dominion Energy cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

YTL Power International

Dominion Energy
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.