Comparison Overview

GSMA - Security and Fraud

VS

Totalplay

GSMA - Security and Fraud

1 Angel Lane, London, EC4R 3AB, GB
Last Update: 2025-12-22

The GSMA Security and Fraud team supports the wider mobile industry against emerging cyber threats and provide the means for all to converge around common solutions.

NAICS: 517
NAICS Definition: Telecommunications
Employees: None
Subsidiaries: 25
12-month incidents
1
Known data breaches
0
Attack type number
1

Totalplay

Avenida San Jerónimo 252 Álvaro Obregón, Mexico City 01090, MX
Last Update: 2025-12-17
Between 750 and 799

Somos una empresa orgullosamente mexicana, líder en tecnología, telecomunicaciones y entretenimiento. Estamos siempre a la vanguardia con el objetivo de llevar a nuestros clientes lo mejor en conectividad, ya sea para que estén cerca de los que más quieren ó puedan alcanzar el éxito profesional gracias a la velocidad que brinda la tecnología de fibra óptica. Nuestro impulso es el equipo que hemos formado, personas con talento, iniciativa, entusiastas y apasionados, que buscan siempre caminar unidos para llevar a más de 20 ciudades de la República Mexicana un servicio de excelencia. Queremos que nuestros clientes sean parte del camino al futuro y vivan al máximo la experiencia de la plataforma de conectividad y entretenimiento total.

NAICS: 517
NAICS Definition:
Employees: 10,001
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/gsma-security-and-fraud.jpeg
GSMA - Security and Fraud
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/totalplay.jpeg
Totalplay
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
GSMA - Security and Fraud
100%
Compliance Rate
0/4 Standards Verified
Totalplay
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Average (This Year)

GSMA - Security and Fraud has 25.0% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for Totalplay in 2025.

Incident History — GSMA - Security and Fraud (X = Date, Y = Severity)

GSMA - Security and Fraud cyber incidents detection timeline including parent company and subsidiaries

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

Totalplay cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/gsma-security-and-fraud.jpeg
GSMA - Security and Fraud
Incidents

Date Detected: 6/2025
Type:Cyber Attack
Motivation: Financial gain through resale of stolen devices
Blog: Blog
https://images.rankiteo.com/companyimages/totalplay.jpeg
Totalplay
Incidents

No Incident

FAQ

Totalplay company demonstrates a stronger AI Cybersecurity Score compared to GSMA - Security and Fraud company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

GSMA - Security and Fraud company has historically faced a number of disclosed cyber incidents, whereas Totalplay company has not reported any.

In the current year, GSMA - Security and Fraud company has reported more cyber incidents than Totalplay company.

Neither Totalplay company nor GSMA - Security and Fraud company has reported experiencing a ransomware attack publicly.

Neither Totalplay company nor GSMA - Security and Fraud company has reported experiencing a data breach publicly.

GSMA - Security and Fraud company has reported targeted cyberattacks, while Totalplay company has not reported such incidents publicly.

Neither GSMA - Security and Fraud company nor Totalplay company has reported experiencing or disclosing vulnerabilities publicly.

Neither GSMA - Security and Fraud nor Totalplay holds any compliance certifications.

Neither company holds any compliance certifications.

GSMA - Security and Fraud company has more subsidiaries worldwide compared to Totalplay company.

Neither GSMA - Security and Fraud nor Totalplay holds SOC 2 Type 1 certification.

Neither GSMA - Security and Fraud nor Totalplay holds SOC 2 Type 2 certification.

Neither GSMA - Security and Fraud nor Totalplay holds ISO 27001 certification.

Neither GSMA - Security and Fraud nor Totalplay holds PCI DSS certification.

Neither GSMA - Security and Fraud nor Totalplay holds HIPAA certification.

Neither GSMA - Security and Fraud nor Totalplay holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.

Risk Information
cvss4
Base: 8.8
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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

5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.

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

continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.

Risk Information
cvss4
Base: 9.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:L/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

LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3

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

LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.

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