Comparison Overview
Bitrefill

Bitrefill
55 E 3rd Ave, Stockholm, 111 56, SE
Last Update: 17/03/2026
You earn internet money. We help you spend it. Bitrefill has been turning crypto into everyday purchases since 2014 - giftcards, prepaid cards, and eSIMs in 180+ countries. Because internet money should work everywhere the internet does. Bitrefill has been remote fir...

Fosun 复星
600, ZHONGSHAN NO.2 ROAD(E) SHANGHAI, 200010 PRC, Shanghai, CN, 200010
Last Update: 01/04/2026
Fosun was founded in 1992. After more than 30 years of development, Fosun has become a global innovation-driven consumer group. Adhering to the mission of creating happier lives for families worldwide, Fosun is committed to creating a global happiness ecosystem fulfilli...
Compliance Ranges Comparison

Bitrefill







Fosun 复星






Benchmark & Cyber Underwriting Signals
Incidents vs Consumer Services Industry Avg (This Year)
Bitrefill has 20.63% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Consumer Services Industry Avg (This Year)
No incidents recorded for Fosun 复星 in 2026.
Incident History - Bitrefill (X = Date, Y = Severity)
Bitrefill cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Fosun 复星 (X = Date, Y = Severity)
Fosun 复星 cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Bitrefill

Fosun 复星
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.