Comparison Overview
Liquid

Liquid
80 Robinson Road, Singapore, 068898, SG
Last Update: 01/04/2026
Founded in 2014, Liquid Group Inc. and its subsidiaries operate Liquid.com (“Liquid”), a leading global cryptocurrency platform that provides trading, exchange, and next generation financial services powered by blockchain technology. With offices in Japan, Singapore, an...

Guaranty Trust
Plot 635, Akin Adesola, Victoria Island, Lagos State, Nigeria, Lagos, NG
Last Update: 07/09/2026
We are Guaranty Trust. Founded in 1990, we own and operate one of Africa's best managed banking franchises, serving over 24 million customers across 10 African countries and the United Kingdom. We are Proudly African and Truly International. We believe in getting it r...
Compliance Ranges Comparison

Liquid







Guaranty Trust






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Liquid in 2026.
Incidents vs Financial Services Industry Avg (This Year)
Guaranty Trust has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Liquid (X = Date, Y = Severity)
Liquid cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Guaranty Trust (X = Date, Y = Severity)
Guaranty Trust cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Liquid

Guaranty Trust
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)