Chess Electrics
Last Update: 2025-03-14 (UTC)
Between 800 and 900
Strong
Electrical Contractor
NAICS: 212
NAICS Definition:
Employees: 51-200
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
Comparison Overview
Chess Electrics
VS
UC RUSAL
UC RUSAL
Last Update: 2025-05-06 (UTC)
Strong
Between 800 and 900
RUSAL is a leading global producer of low-carbon aluminium. More than 90% of the Company's aluminium is produced from renewable electricity, and by implementing innovative and energy-saving technologies RUSAL is able to reduce greenhouse gas emissions at all production stages. This has enabled RUSAL to become one of the first in the world to master the production of 'green' metal under the ALLOW brand. Less than 4 t of CO2 equivalent per 1 tonne of aluminium is the carbon footprint of ALLOW aluminium brand (scope 1 and scope 2) RUSAL operates in 20 countries on 5 continents. The company employs 50,000 people across the globe. In 2020, RUSAL accounted for approximately 5.8% of global production of aluminium and 6.5% of alumina. The Company’s key sales markets are Europe, Russia and the CIS countries, North America, South-East Asia, Japan and South Korea. The major end users are transport, construction, power and packaging industries. RUSAL owns proprietary smelting technologies and is developing new ones, including a revolutionary inert anode technology.
NAICS: 212
NAICS Definition: Mining (except Oil and Gas)
Employees: 10,001+
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
Compliance Badges Comparison
Security & Compliance Standards Overview
Chess Electrics
ISO 27001
Not verified
SOC 2
Not verified
GDPR
No public badge
PCI DSS
No public badge
UC RUSAL
ISO 27001
Not verified
SOC 2
Not verified
GDPR
No public badge
PCI DSS
No public badge
Compliance Summary
Chess Electrics
100%
Compliance Rate
0/4 Standards Verified
UC RUSAL
0%
Compliance Rate
0/4 Standards Verified
Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Average (This Year)
No incidents recorded for Chess Electrics in 2025.
Incidents vs Mining Industry Average (This Year)
No incidents recorded for UC RUSAL in 2025.
Incident History — Chess Electrics (X = Date, Y = Severity)
Chess Electrics cyber incidents detection timeline including parent company and subsidiaries
Incident History — UC RUSAL (X = Date, Y = Severity)
UC RUSAL cyber incidents detection timeline including parent company and subsidiaries
Notable Incidents
Last 3 Security & Risk Events by Company
Chess Electrics
Incidents
No Incident
UC RUSAL
Incidents
No Incident
FAQ
Both Chess Electrics company and UC RUSAL company demonstrate a comparable AI risk posture, with strong governance and monitoring frameworks in place.
Historically, UC RUSAL company has disclosed a higher number of cyber incidents compared to Chess Electrics company.
In the current year, UC RUSAL company and Chess Electrics company have not reported any cyber incidents.
Neither UC RUSAL company nor Chess Electrics company has reported experiencing a ransomware attack publicly.
Neither UC RUSAL company nor Chess Electrics company has reported experiencing a data breach publicly.
Neither UC RUSAL company nor Chess Electrics company has reported experiencing targeted cyberattacks publicly.
Neither Chess Electrics company nor UC RUSAL company has reported experiencing or disclosing vulnerabilities publicly.
Neither Chess Electrics company nor UC RUSAL company has publicly disclosed detailed information about the number of their subsidiaries.
Neither Chess Electrics company nor UC RUSAL company has publicly disclosed the exact number of their employees.
Latest Global CVEs (Not Company-Specific)
Description
Improper Protection Against Voltage and Clock Glitches in FPGA devices, could allow an attacker with physical access to undervolt the platform resulting in a loss of confidentiality.
Risk Information
cvss4
Base: 8.6
Severity: LOW
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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
Malicious code was inserted into the Nx (build system) package and several related plugins. The tampered package was published to the npm software registry, via a supply-chain attack. Affected versions contain code that scans the file system, collects credentials, and posts them to GitHub as a repo under user's accounts.
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
References
- https://access.redhat.com/security/cve/CVE-2025-10894
- https://access.redhat.com/security/supply-chain-attacks-NPM-packages
- https://bugzilla.redhat.com/show_bug.cgi?id=2396282
- https://github.com/nrwl/nx/security/advisories/GHSA-cxm3-wv7p-598c
- https://www.stepsecurity.io/blog/supply-chain-security-alert-popular-nx-build-system-package-compromised-with-data-stealing-malware
- https://www.wiz.io/blog/s1ngularity-supply-chain-attack
Description
Flag Forge is a Capture The Flag (CTF) platform. In versions from 2.1.0 to before 2.3.0, the API endpoint GET /api/problems/:id returns challenge hints in plaintext within the question object, regardless of whether the user has unlocked them via point deduction. Users can view all hints for free, undermining the business logic of the platform and reducing the integrity of the challenge system. This issue has been patched in version 2.3.0.
Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Description
Flag Forge is a Capture The Flag (CTF) platform. In version 2.1.0, the /api/admin/assign-badge endpoint lacks proper access control, allowing any authenticated user to assign high-privilege badges (e.g., Staff) to themselves. This could lead to privilege escalation and impersonation of administrative roles. This issue has been patched in version 2.2.0.
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Description
parse is a package designed to parse JavaScript SDK. A Prototype Pollution vulnerability in the SingleInstanceStateController.initializeState function of parse version 5.3.0 and before allows attackers to inject properties on Object.prototype via supplying a crafted payload, causing denial of service (DoS) as the minimum consequence.
