Comparison Overview

Rakuten

VS

Shopee

Rakuten

Rakuten Crimson House, 1-14-1 Tamagawa, Setagaya-ku, Tokyo, JP, 158-0094
Last Update: 2025-12-09

Rakuten Group, Inc. (TSE: 4755) is a global technology leader in services that empower individuals, communities, businesses and society. Founded in Tokyo in 1997 as an online marketplace, Rakuten has expanded to offer services in e-commerce, fintech, digital content and communications to 2 billion members around the world. The Rakuten Group has more than 30,000 employees, and operations in 30 countries and regions. For more information visit https://global.rakuten.com/corp/.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 10,677
Subsidiaries: 24
12-month incidents
0
Known data breaches
2
Attack type number
1

Shopee

5 Science Park Dr, Shopee Building, Singapore, Singapore, SG, 118265
Last Update: 2025-12-09
Between 800 and 849

Shopee is the leading e-commerce platform in Southeast Asia and Taiwan. It is a platform tailored for the region, providing customers with an easy, secure and fast online shopping experience through strong payment and logistical support. Shopee aims to continually enhance its platform and become the region’s e-commerce destination of choice via ongoing product optimisation and localised user-centered strategies. Shopee, a Sea company, was first launched in Singapore in 2015, and has since expanded its reach to Malaysia, Thailand, Taiwan, Indonesia, Vietnam and the Philippines. Sea is a leader in digital entertainment, e-commerce and digital financial services across Greater Southeast Asia. Sea's mission is to better the lives of consumers and small businesses with technology, and is listed on the NYSE under the symbol SE. The Shopee team is rapidly expanding across the region and we are constantly on the lookout for talents who have the passion and drive to become part of a fast-moving and dynamic team. Do check out our career website http://careers.shopee.com for our available positions!

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 55,101
Subsidiaries: 4
12-month incidents
0
Known data breaches
0
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/rakuten.jpeg
Rakuten
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/shopee.jpeg
Shopee
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Rakuten
100%
Compliance Rate
0/4 Standards Verified
Shopee
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Rakuten in 2025.

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Shopee in 2025.

Incident History — Rakuten (X = Date, Y = Severity)

Rakuten cyber incidents detection timeline including parent company and subsidiaries

Incident History — Shopee (X = Date, Y = Severity)

Shopee cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/rakuten.jpeg
Rakuten
Incidents

Date Detected: 1/2021
Type:Breach
Attack Vector: Insider Wrongdoing
Blog: Blog

Date Detected: 4/2018
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/shopee.jpeg
Shopee
Incidents

Date Detected: 6/2022
Type:Data Leak
Attack Vector: Phishing emails/messages
Motivation: Financial gain, data theft
Blog: Blog

FAQ

Shopee company demonstrates a stronger AI Cybersecurity Score compared to Rakuten company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Rakuten company has faced a higher number of disclosed cyber incidents historically compared to Shopee company.

In the current year, Shopee company and Rakuten company have not reported any cyber incidents.

Neither Shopee company nor Rakuten company has reported experiencing a ransomware attack publicly.

Rakuten company has disclosed at least one data breach, while the other Shopee company has not reported such incidents publicly.

Neither Shopee company nor Rakuten company has reported experiencing targeted cyberattacks publicly.

Neither Rakuten company nor Shopee company has reported experiencing or disclosing vulnerabilities publicly.

Neither Rakuten nor Shopee holds any compliance certifications.

Neither company holds any compliance certifications.

Rakuten company has more subsidiaries worldwide compared to Shopee company.

Shopee company employs more people globally than Rakuten company, reflecting its scale as a Software Development.

Neither Rakuten nor Shopee holds SOC 2 Type 1 certification.

Neither Rakuten nor Shopee holds SOC 2 Type 2 certification.

Neither Rakuten nor Shopee holds ISO 27001 certification.

Neither Rakuten nor Shopee holds PCI DSS certification.

Neither Rakuten nor Shopee holds HIPAA certification.

Neither Rakuten nor Shopee holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.

Risk Information
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 9.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
Description

Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Description

Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.

Risk Information
cvss3
Base: 8.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
Description

The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.

Risk Information
cvss3
Base: 5.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N