Comparison Overview
幣託集團 BitoGroup
幣託集團 BitoGroup
37F., No. 7, Sec. 5, Xinyi Rd., Xinyi Dist., Taipei City, TW
Last Update: 02/04/2026
幣託集團（BitoGroup）成立於2014年，致力於用最簡單的方式讓區塊鏈進入每個人的日常生活，並協助企業與消費者進入Web3時代。幣託集團致力於運用區塊鏈和高頻交易技術，積極打造創新的金融基礎設施。集團旗下擁有多元化業務，包括BitoPro加密貨幣交易所、NFT賦能平台BELS，以及O2 META。 BitoPro為全臺第一家安全、穩定且易於使用的加密貨幣交易所，BitoPro提供加密貨幣錢包和交易所的區塊鏈服務。此外，亦支援在超商購買或點數兌換加密貨幣。BitoPro支援多種主流幣種，如ETH（以太幣）、USDT（泰達幣）、DO...
Bloomberg
731 Lexington Ave., New York, NY, US, 10022
Last Update: 13/09/2026
Bloomberg is a global leader in business and financial information, delivering trusted data, news, and insights that bring transparency and efficiency, and fairness to markets. We help connect influential communities across the global financial ecosystem via reliable te...
Compliance Ranges Comparison
幣託集團 BitoGroup
Bloomberg
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for 幣託集團 BitoGroup in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Bloomberg in 2026.
Incident History - 幣託集團 BitoGroup (X = Date, Y = Severity)
幣託集團 BitoGroup cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bloomberg (X = Date, Y = Severity)
Bloomberg cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
幣託集團 BitoGroup
Bloomberg
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.