MKT
Centralised exchange

Phemex

Lost $70m or more in January 2025, and its own incident timeline does not contain the word compensation. Its insurance balance page reads "No Data".

Founded
2019
Registered
Singapore

The short answer

Two facts decide this one. It lost $70m or more in January 2025, and its own published incident timeline does not contain the word compensation — not a denial, an absence. And the "insurance fund" it advertises is explicitly a derivatives liquidation backstop whose public balance page renders "No Data". There is no theft cover. A $10,000 bitcoin buy cost 0.1001%, and the API took 911 ms to answer.

Key facts

January 2025 hack$70m or more. Phemex’s own incident timeline does not contain the word compensation.as of 14 Jul 2026
"Insurance fund"Explicitly a derivatives liquidation backstop, and its public balance page renders "No Data"as of 14 Jul 2026
Theft coverNoneas of 14 Jul 2026
Proof of reservesMonthly Merkle proof covering liabilities with a self-verification tool, and no independent attestor. Custody sits with Fireblocks — but a custodian is not an auditor, and the ratios are Phemex’s own arithmetic.as of 14 Jul 2026
Custody score3 out of 10as of 14 Jul 2026
Effective cost, $10,000 BTC buy (measured by us)0.1001%; 0.1185% at $100,000as of 14 Jul 2026
Order-book depth within 0.1% (measured by us)28.5 BTCas of 14 Jul 2026
API response latency (measured by us)911 ms — second slowest in our runas of 14 Jul 2026

A hack, and a timeline that never mentions compensation

Phemex lost $70m or more in January 2025. What makes this entry unusual is not the amount but the documentation: the company published an incident timeline, and the word compensation does not appear in it. That is not a refusal to pay, which would at least be a position. It is an absence, and eighteen months later the absence is the record.

There is also nothing that could have paid. The "insurance fund" Phemex advertises is explicitly a derivatives liquidation backstop — it exists to absorb losses from bankrupt leveraged positions, not to reimburse a user whose assets were stolen. Its public balance page renders "No Data", so even the backstop’s size is unknown.

On reserves, Phemex publishes a monthly Merkle proof covering liabilities with a self-verification tool, which is real machinery. No independent attestor signs it. Custody is with Fireblocks, and that is worth something and is frequently misrepresented: a custodian holds keys, it does not verify that the exchange’s stated reserves match its liabilities. The ratios are Phemex’s own arithmetic.

We score custody 3 out of 10. A venue that has already been hacked, has no theft fund, and has never stated what happened to the people affected is at the bottom of this rating for reasons that need no further interpretation.

Cheap trades, slow infrastructure

A $10,000 bitcoin buy cost 0.1001% on 14 July 2026, in the cheapest tier, though the curve steepens faster than its peers: 0.1185% at $100,000 against 0.1005% at OKX and 0.10% at Binance. Depth measured 28.5 BTC within 0.1% of best ask, on the thin side.

API response latency measured 911 ms, the second slowest venue in the run behind Gate.io’s 3,028 ms and roughly five times Coinbase’s 183 ms.

KYC scores 8 out of 10, with clearly published tiers, which is the strongest part of the card.

The pricing is competitive and nothing else here is, and the section above is the reason the pricing should not be the deciding factor.

Incident record

DateTypeAmountWere users made whole?
23 Jan 2025Hack or exploit$70,000,000Unknown, and the silence is the finding. Phemex’s own published incident timeline does not contain the word compensation — not a refusal, an absence. No theft fund exists to have paid from.source

In our ratings

Compared with

Our coverage of Phemex

Questions people ask

Is Phemex safe?

Custody scores 3 out of 10, among the lowest in our rating. It lost $70m or more in January 2025 and its own incident timeline does not contain the word compensation. There is no theft fund — the advertised insurance is a derivatives backstop whose balance page reads "No Data".

Were Phemex users compensated after the 2025 hack?

Unknown, and the silence is the finding. Phemex published an incident timeline that never mentions compensation — not a refusal, an absence. No theft fund exists that could have paid.

Does Fireblocks custody make Phemex safe?

It helps and it is widely overstated. Fireblocks holds keys; it does not audit whether Phemex’s stated reserves match its liabilities. The reserve ratios remain Phemex’s own arithmetic with no independent attestor.

Is Phemex’s insurance fund real?

It exists and it is not theft cover. Phemex describes it explicitly as a derivatives liquidation backstop for bankrupt leveraged positions, and its public balance page renders "No Data", so even that figure is unavailable.

What changed

  • 27 Sept 2026 — Profile published.