Comparison Overview

Q: Between Telekom Malaysia company and yes company, which one has the best AI Cybersecurity Score ?

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

Q: Between Telekom Malaysia company and yes company, which one has experienced more cyber incidents in the past ?

Telekom Malaysia company has historically faced a number of disclosed cyber incidents, whereas yes company has not reported any.

Q: Between Telekom Malaysia company and yes company, which one has experienced more cyber incidents this year ?

In the current year, yes company and Telekom Malaysia company have not reported any cyber incidents.

Q: Between Telekom Malaysia company and yes company, which one has experienced at least one ransomware attack ?

Neither yes company nor Telekom Malaysia company has reported experiencing a ransomware attack publicly.

Q: Between Telekom Malaysia company and yes company, which one has experienced at least one data breach ?

Neither yes company nor Telekom Malaysia company has reported experiencing a data breach publicly.

Q: Between Telekom Malaysia company and yes company, which one has experienced at least one targeted cyberattack ?

Neither yes company nor Telekom Malaysia company has reported experiencing targeted cyberattacks publicly.

Q: Between Telekom Malaysia company and yes company, which one has experienced at least one vulnerability ?

Neither Telekom Malaysia company nor yes company has reported experiencing or disclosing vulnerabilities publicly.

Q: Between Telekom Malaysia company and yes company, which one holds the most compliance certifications ?

Neither Telekom Malaysia nor yes holds any compliance certifications.

Q: Between Telekom Malaysia company and yes company, which one has the most subsidiaries ?

Neither Telekom Malaysia company nor yes company has publicly disclosed detailed information about the number of their subsidiaries.

Telekom Malaysia

Jalan Pantai Baharu, Kuala Lumpur, 50672, MY

Last Update: 2026-01-18

View Profile

Between 700 and 749

https://www.tm.com.my

TM is the national connectivity and digital infrastructure provider and Malaysia’s leading integrated telco; offering a comprehensive suite of communication services and solutions in fixed (telephony and broadband), mobility, content, WiFi, ICT, Cloud and smart services. TM is driven by stakeholder value creation in a highly competitive environment and places, emphasis on delivering an enhanced customer experience via continuous customer service quality improvements and innovations, whilst focusing on increased operational efficiency and productivity. As the enabler of the nation’s Digital Malaysia aspiration, TM has been at the forefront of every telecommunications technology evolution in the country and will continue to do so. It provides the communications backbone of Malaysia with the widest connectivity and convergence network. TM remains committed to expanding its network with a comprehensive digital infrastructure. Moving beyond connectivity services, TM is developing new value-added digital services to cater to a more digital lifestyle and society, digital businesses, and digital government, striving to make “Life and Business Easier, for a better Malaysia.” For further information on TM, visit www.tm.com.my. . SSM: 128740-P

NAICS: 517

NAICS Definition: Telecommunications

Employees: 10,536

Subsidiaries: 0

12-month incidents

0

Known data breaches

0

Attack type number

1

View Profile

yes

Ha-Yozma St 6, Kfar Saba, 4442218, IL

Last Update: 2026-01-21

Between 750 and 799

https://career.yes.co.il/

תכירו את השחקנים הראשיים שלנו: העובדות והעובדים. אנחנו לא עובדים עם תסריט קבוע, חושבים מחוץ לקופסא, ומייצרים ז'אנר משלנו. כש-יס קמה, בשנת 1998, הבאנו את בשורת הלווין אל עולם שידורי הטלוויזיה והיינו הראשונים להציע שידורים דיגיטליים ושירותי טלוויזיה אינטראקטיביים - כשבחירת התכנים היא בידיים של הלקוח, מה שהגדיר מחדש את ענף שידורי הטלוויזיה בישראל. את החדשנות הזאת רואים ברזולוציית HD בכל הצוותים והמחלקות שלנו - מהתוכן שבוחר את התכנים, דרך הטכנאים שמתקינים את התשתית ועד חטיבת השירות שזמינה ללקוחות שלנו עם כל צורך שיצוץ. בשיתוף פעולה שחוצה צוותים ומחלקות, השתמשנו מהרגע הראשון בטכנולוגיות החדשניות ביותר ועליהן הלבשנו את מיטב התכנים. חתמנו על חוזי רכישה עם אולפני הסרטים והמפיצים המובילים בעולם כדי לדאוג למבחר הגדול ביותר של סרטים חדשים באיכות הצפייה החדה ביותר שנראתה עד היום. ואנחנו משתפים פעולה עם ענקיות הסטרימינג הבינלאומיות: דיסני פלוס, דיסקברי פלוס ונטפליקס וכל זה מתאפשר בזכות גיוס הטובים ביותר בעולמות הבידור, הטכנולוגיה והתמיכה תוך מתן דגש על שירות לקוחות שדוגל בהקשבה ובשקיפות. אפילו מכרנו לאחרונה כמה הפקות מקור מובילות בחו"ל. ביניהן "פאודה", עליה נכתב בניו יורק טיימס שהיא אחת הסדרות הבינלאומיות הטובות ביותר לשנת 2017, כמו גם "כבודו" ו-"שטיסל", שנמכרו ל-CBS. ו"מלכת היופי של ירושלים" שנמכרה ל-נטפליקס. לא פלא שכ- 580 אלף משפחות בישראל וכ- 1000 עובדים כבר אמרו לנו כן

NAICS: 517

NAICS Definition: Telecommunications

Employees: 12,971

Subsidiaries: 0

12-month incidents

0

Known data breaches

0

Attack type number

0

Telekom Malaysia

—

ISO 27001

Not verified

—

SOC2 Type 1

Not verified

—

SOC2 Type 2

Not verified

—

GDPR

Not verified

—

PCI DSS

Not verified

—

HIPAA

Not verified

https://images.rankiteo.com/companyimages/yes-dbs-satellite-services-ltd.jpeg

yes

—

ISO 27001

Not verified

—

SOC2 Type 1

Not verified

—

SOC2 Type 2

Not verified

—

GDPR

Not verified

—

PCI DSS

Not verified

—

HIPAA

Not verified

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for Telekom Malaysia in 2026.

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for yes in 2026.

Incident History — Telekom Malaysia (X = Date, Y = Severity)

Telekom Malaysia cyber incidents detection timeline including parent company and subsidiaries

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

yes cyber incidents detection timeline including parent company and subsidiaries

Telekom Malaysia

Incidents

Date Detected: 12/2022

Type:Data Leak

Blog: Blog

yes

Incidents

No Incident

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

Telekom Malaysia company has historically faced a number of disclosed cyber incidents, whereas yes company has not reported any.

In the current year, yes company and Telekom Malaysia company have not reported any cyber incidents.

Neither yes company nor Telekom Malaysia company has reported experiencing a ransomware attack publicly.

Neither yes company nor Telekom Malaysia company has reported experiencing a data breach publicly.

Neither yes company nor Telekom Malaysia company has reported experiencing targeted cyberattacks publicly.

Neither Telekom Malaysia company nor yes company has reported experiencing or disclosing vulnerabilities publicly.

Neither Telekom Malaysia nor yes holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Telekom Malaysia company nor yes company has publicly disclosed detailed information about the number of their subsidiaries.

yes company employs more people globally than Telekom Malaysia company, reflecting its scale as a Telecommunications.

Neither Telekom Malaysia nor yes holds SOC 2 Type 1 certification.

Neither Telekom Malaysia nor yes holds SOC 2 Type 2 certification.

Neither Telekom Malaysia nor yes holds ISO 27001 certification.

Neither Telekom Malaysia nor yes holds PCI DSS certification.

Neither Telekom Malaysia nor yes holds HIPAA certification.

Neither Telekom Malaysia nor yes holds GDPR certification.

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g., execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Published

Date

2026-01-20

Updated

Date

2026-01-20

Risk Information

cvss4

Base: 7.7

Severity: LOW

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/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

References

https://github.com/cloudflare/workers-sdk

Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published

Date

2026-01-20

Updated

Date

2026-01-20

Risk Information

cvss3

Base: 8.2

Severity: LOW

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

References

https://www.oracle.com/security-alerts/cpujan2026.html

Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

Published

Date

2026-01-20

Updated

Date

2026-01-20

Risk Information

cvss3

Base: 8.1

Severity: LOW

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L

References

https://www.oracle.com/security-alerts/cpujan2026.html

Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published

Date

2026-01-20

Updated

Date

2026-01-20

Risk Information

cvss3

Base: 8.2

Severity: LOW

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

References

https://www.oracle.com/security-alerts/cpujan2026.html

Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published

Date

2026-01-20

Updated

Date

2026-01-20

Risk Information

cvss3

Base: 8.2

Severity: LOW

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

References

https://www.oracle.com/security-alerts/cpujan2026.html

Badge your company to reduce your risk score and your cyber insurance costs!

Comparison Overview

Telekom Malaysia

VS

yes

Telekom Malaysia

yes

Compliance Badges Comparison

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Average (This Year)

Incidents vs Telecommunications Industry Average (This Year)

Incident History — Telekom Malaysia (X = Date, Y = Severity)

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

Notable Incidents

No Incident

FAQ

Latest Global CVEs (Not Company-Specific)

CVE-2026-0933

Risk Information

CVE-2026-21990

Risk Information

CVE-2026-21989

Risk Information

CVE-2026-21988

Risk Information

CVE-2026-21987

Risk Information

Badge your company to reduce your risk score and your cyber insurance costs!

Comparison Overview

Telekom Malaysia

VS

yes

Telekom Malaysia

yes

Compliance Badges Comparison

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Average (This Year)

Incidents vs Telecommunications Industry Average (This Year)

Incident History — Telekom Malaysia (X = Date, Y = Severity)

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

Notable Incidents

🔒 Incident : Data Leak TEL2151311222

No Incident

FAQ

Between Telekom Malaysia company and yes company, which one has the best AI Cybersecurity Score ?

Between Telekom Malaysia company and yes company, which one has experienced more cyber incidents in the past ?

Between Telekom Malaysia company and yes company, which one has experienced more cyber incidents this year ?

Between Telekom Malaysia company and yes company, which one has experienced at least one ransomware attack ?

Between Telekom Malaysia company and yes company, which one has experienced at least one data breach ?

Between Telekom Malaysia company and yes company, which one has experienced at least one targeted cyberattack ?

Between Telekom Malaysia company and yes company, which one has experienced at least one vulnerability ?

Between Telekom Malaysia company and yes company, which one holds the most compliance certifications ?

Between Telekom Malaysia company and yes company, which one holds the fewest compliance certifications ?

Between Telekom Malaysia company and yes company, which one has the most subsidiaries ?

Between Telekom Malaysia company and yes company, which one has the largest number of employees ?

Between Telekom Malaysia and yes, which company holds both SOC 2 Type 1 certifications ?

Between Telekom Malaysia and yes, which company holds both SOC 2 Type 2 certifications ?

Which company is ISO 27001 certified — Telekom Malaysia or yes ?

Which company is PCI DSS compliant — Telekom Malaysia or yes ?

Between Telekom Malaysia and yes, which company complies with HIPAA regulations for healthcare data ?

Between Telekom Malaysia and yes, which company complies with GDPR requirements ?

Latest Global CVEs (Not Company-Specific)

CVE-2026-0933

Risk Information

CVE-2026-21990

Risk Information

CVE-2026-21989

Risk Information

CVE-2026-21988

Risk Information

CVE-2026-21987

Risk Information