Comparison Overview
TECO Electric & Machinery Co., Ltd.

TECO Electric & Machinery Co., Ltd.
南港區三重路19之9號5樓, 台北市, undefined, 115, TW
Last Update: 05/05/2026
東元電機創立於西元1956年,初期從事馬達生產,至今東元集團已跨入重電、家電、資訊、通訊、電子關鍵零組件、基礎工程建設、金融投資及餐飲、服務等多面向的發展領域,更積極參與國家重大工程建設,目前事業版圖橫跨全球五大洲四十餘國、百餘城市。未來,東元將持續深耕核心事業,將以願景「成為全球電氣化、智能化與綠色能源的核心發展驅動者」為發展主軸,強化數位轉型目標,精實營銷及生產智動化,並健全商業智能系統(BI),以提升精準市場營銷進而引導成長,建構一個宏觀、高品質的世界級品牌。 【願景】 成為全球電氣化、智能化與綠色能源的核心發展驅動者 【價...

Foxconn
US
Last Update: 12/09/2026
Established in Taiwan in 1974, Hon Hai Technology Group (Foxconn) (2317: Taiwan) is the world’s largest electronics manufacturer. Foxconn is also the leading technological solution provider, and it continuously leverages its expertise in software and hardware to integra...
Compliance Ranges Comparison

TECO Electric & Machinery Co., Ltd.







Foxconn






Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for TECO Electric & Machinery Co., Ltd. in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
Foxconn has 288.35% more incidents than the average of all companies with at least one recorded incident.
Incident History - TECO Electric & Machinery Co., Ltd. (X = Date, Y = Severity)
TECO Electric & Machinery Co., Ltd. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Foxconn (X = Date, Y = Severity)
Foxconn cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

TECO Electric & Machinery Co., Ltd.

Foxconn
FAQ
Latest Global CVEs
A flaw has been found in OpenClaw up to 2026.9.5. Affected is the function createCanvasHostHandler of the file extensions/canvas/src/host/server.ts of the component Canvas Host Route. Executing a manipulation can lead to denial of service. The attack can be launched remotely. The exploit has been published and may be used. Fix suggestion's "streaming/size-limit" was never shipped - latest 2026.9.5 still buffers the whole file via readFile() (src/canvas/serve.runtime.ts:17,114), unlike the sibling WS path which caps at 64KB. The vendor was contacted early about this disclosure.
A security vulnerability has been detected in DLR-RM stable-baselines3 up to 2.9.0. This affects the function PPO.load/load_replay_buffer/VecNormalize.load of the file save_util.py. Such manipulation leads to deserialization. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. In v2.9.0 the PyTorch tensor load path is hardened (weights_only=True), but that hardening was later reverted on master via PR #1913 "Hotfix: revert loading with weights_only=True" [blocked] to fix PyTorch 1.13 compat - so even the one "safe" path is inconsistent across versions. #2281 was closed as a duplicate of #1831 since both are unsafe pickle deserialization - but #1831's fix (PR #41) only gated the Hugging Face Hub loader in the separate huggingface_sb3 package. This finding covers the core stable_baselines3 load APIs (PPO.load, load_replay_buffer, VecNormalize.load), which have no safe mode or gate and remained exploitable in v2.9.0 until the outstanding hardening (PR #2264) ships.
A vulnerability was detected in dmlc dgl up to 2.1.0. This impacts the function load_info/_read_torch_data of the file utils.py. Performing a manipulation of the argument path results in deserialization. The attack can be initiated remotely. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
A weakness has been identified in piskvorky gensim up to 4.4.0. The impacted element is the function Load of the file gensim/utils.py of the component Model Loader. This manipulation of the argument fname causes deserialization. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. Maintainer closed #3663 same-day with no comment, PR, or fix; repo's last push (2025-11-01) predates the report, so the unsafe pickle.load in SaveLoad.load remains unguarded at develop HEAD.
A security flaw has been discovered in JusticeRage Manalyze 1.0.0. The affected element is the function PE::_parse_debug of the file manape/pe.cpp of the component PE Parser. The manipulation of the argument misc.Length results in integer underflow. The attack may be performed from remote. The patch is identified as 3e299685759f4f767088871de58c5d07f98ee382. A patch should be applied to remediate this issue.