Comparison Overview
ShopeePay

ShopeePay
1 Rochester Park, Singapore, 139212, SG
Last Update: 27/02/2026
ShopeePay is Monee's mobile wallet, which provides users with easy access to digital payment services. Our mobile wallet provides users with a fast and secure way to make online payments, transfer funds and pay offline at thousands of our merchant partner locations. T...

Credicorp
Calle Centenario 154, Lima, Lima, PE, 12
Last Update: 07/09/2026
Somos el grupo financiero líder en el Perú con una vasta experiencia en el mercado peruano. Contamos con una sólida plataforma de Banca Comercial reforzada por una importante presencia en Banca de Inversión en Latinoamérica destinada a desarrollar el potencial de la reg...
Compliance Ranges Comparison

ShopeePay







Credicorp






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

ShopeePay

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