Comparison Overview
BEES Bank Brasil

BEES Bank Brasil
Rua Amauri 227, São Paulo, undefined, 01448-000, BR
Last Update: 26/02/2026
O BEES Bank é uma fintech que, além de fazer parte do ecossistema de Z-Tech, também faz parte do ecossistema de BEES Brasil. Somos especialistas em soluções financeiras que impulsionam milhares de negócios pelo Brasil. Nosso propósito é tornar a vida financeira dos pe...

NCS Group
Singapore, 5 Ang Mo Kio Street 62, NCS Hub, Singapore, SG, 569141
Last Update: 15/09/2026
NCS, a subsidiary of Singtel Group, is a leading technology services firm with presence in Asia Pacific and partners with governments and enterprises to advance communities through technology. Combining the experience and expertise of its 14,000-strong team across 56 sp...
Compliance Ranges Comparison

BEES Bank Brasil







NCS Group






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

BEES Bank Brasil

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