Law report No. GLW-1354 · filed October 15, 2026

Courts & TribunalsReported case

Dubai Courts Impose Strict Liability on Non-Debtor Third Parties

Dubai courts have imposed strict liability on non-debtor third parties in a ruling dubbed the 'Seven-Day Trap', with warnings for global crypto exchanges.

By Sophie Lindqvist4 min read701 words

Holding

  1. Dubai courts imposed strict liability on non-debtor third parties, per a Lexology commentary
  2. The ruling has been labelled the 'Seven-Day Trap'
  3. The commentary frames the decision as a comparative warning for global crypto exchanges
  4. Strict liability attaches without proof of fault, unlike fault-based regimes
The Seven-Day Trap: Dubai Courts Impose Strict Liability on Non-Debtor Third Parties - A Comparative Warning for Global
PlateThe Seven-Day Trap: Dubai Courts Impose Strict Liability on Non-Debtor Third Parties - A Comparative Warning for Global — AI-generated

By Sophie Lindqvist

Dubai courts have imposed strict liability (liability without proof of fault) on third parties who were never the original debtors, according to a legal analysis published by Lexology. The decision has been labelled the "Seven-Day Trap". It also carries a warning for crypto exchanges operating across borders.

Before going further, a word on sourcing. This article draws on a Lexology commentary titled "The Seven-Day Trap: Dubai Courts Impose Strict Liability on Non-Debtor Third Parties - A Comparative Warning for Global Crypto Exchanges". The underlying commentary headline is itself the primary confirmed detail. What follows unpacks the mechanism that headline describes, and the practical questions it raises for practitioners. Where the source is thin, we say so plainly.

What is the 'Seven-Day Trap'?

The name suggests timing. Seven days is a short window. A trap of that length usually works like this: a party receives notice of an attachment, freeze or court order, and must act within the period. Miss the deadline, or mishandle the frozen assets, and liability attaches regardless of intent.

Strict liability is the key mechanism here. Under a fault-based regime, a claimant must prove negligence or bad intent. Under strict liability, the claimant needs neither. The third party becomes liable simply because it held, moved or failed to preserve the asset. That is a heavy burden, and Dubai's courts have now, per the commentary, applied it to parties who were not the original debtors in the case.

The analogy is useful. Think of a courier who accepts a sealed box, gets told the box is evidence, and then opens it anyway. It doesn't matter that the courier meant no harm. The box was in the courier's hands, and the obligation attached to possession itself.

Why do crypto exchanges care?

The comparative warning in the commentary's title points at digital asset platforms. Exchanges sit in a position that traditional banks know well, but with faster settlement and thinner procedural buffers.

Exchanges hold customer assets. They receive freezing orders from courts in multiple jurisdictions. They are often not parties to the underlying dispute. The Dubai analysis suggests that this non-debtor status may not protect them.

That reframes the risk. A platform that receives an order tied to Dubai proceedings may face strict liability if it does not act within the stated window, even though the platform owes no debt and took no side. The commentary frames this as a warning precisely because many exchanges treat freezing requests as someone else's litigation problem.

What should practitioners take from it?

We flag the practical implications, but with a caveat: the Lexology piece is the source here, and the full judgment details, case reference and date sit behind that commentary. Practitioners should read the analysis directly before relying on any specific holding. That said, the headline alone raises concrete questions:

  • Does your client hold assets traceable to Dubai proceedings, even as a pure custodian?
  • Is there a defined internal route for routing foreign court orders to legal within seven days?
  • Do custody arrangements distinguish customer assets from the platform's own holdings?
  • Does the exchange's terms-of-service language allocate this risk, or silently absorb it?

The comparison the commentary invites is with other jurisdictions that impose quia timet or third-party freezing obligations. The common thread is custodial exposure. The Dubai development, as characterised, fits that pattern while raising the stakes through strict liability rather than fault-based standards.

How firm is this reading?

Honest answer: partially firm. The headline is clear on three points. Dubai courts acted. They imposed strict liability on non-debtor third parties. The authors see a comparative lesson for crypto exchanges globally.

Everything else above is mechanism, not confirmed fact from the ruling itself. Global Law Wire has not independently verified the case name, court instance or decision date. We will update this piece when those details are confirmed. For now, the signal matters: custodians of assets touching Dubai litigation cannot assume that being outside the debt keeps them outside the liability.

That is the trap. It springs in seven days, and it doesn't ask whether you meant to step on it.

via GN Lexology (Source)

Filed under

  • strict-liability
  • dubai
  • crypto-exchanges
  • asset-freezing
  • third-party-liability
Share this article:

More from Sophie Lindqvist

Sophie Lindqvist

Show full bio

News editor covering people, launches and day-to-day practice in International law and legal practice at Global Law Wire.

243 articles

Also before the court

« Previous articleNext article »