Comparison Overview
Digital Recovery

Digital Recovery
Poweline RD , Pompano Beach , 33073, US
Last Update: 03/04/2026
Founded in 1998, Digital Recovery emerged in the aftermath of the Chernobyl virus (Win32/CIH), with a clear mission: to deliver advanced data recovery solutions. Our journey began through a strategic partnership with a U.S.-based data recovery lab, allowing us to acquir...

LTIMindtree
L&T Infotech, Technology Tower. Gate No. 5, Saki Vihar Road, Powai, Mumbai, Maharashtra 400072, IN, Mumbai, MH, IN, 400072
Last Update: 05/04/2026
LTIMindtree is a global technology consulting and digital solutions company that partners with enterprises across industries to reimagine business models, accelerate innovation, and drive AI-centric growth. Trusted by more than 700 clients worldwide, we use advanced tec...
Compliance Ranges Comparison

Digital Recovery







LTIMindtree






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Digital Recovery in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for LTIMindtree in 2026.
Incident History - Digital Recovery (X = Date, Y = Severity)
Digital Recovery cyber incidents detection timeline including parent company and subsidiaries.
Incident History - LTIMindtree (X = Date, Y = Severity)
LTIMindtree cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Digital Recovery

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