Shadow Fleet Sanctions Red Flags: 15 Checks Before You Fix, Lift, or Pay

If you are fixing a fixture, lifting a cargo, or sending a payment, “shadow fleet” risk usually shows up in patterns that look small in isolation, but become hard to explain later if a bank, insurer, or regulator asks why you were comfortable. This checklist is built for commercial reality: quick signals, the proof you want in hand, and the places disputes and claim denials tend to start when the file gets reviewed months later.
Not legal adviceThis checklist is for general information and operational screening. It is not legal advice and does not create an attorney client relationship.
Sanctions rules and enforcement expectations can change quickly and vary by jurisdiction. Use this as a trigger list to tighten documentation and escalate internally, including to counsel and compliance, before fixing, lifting, or paying.
🚩 Shadow Fleet Sanctions Red Flags
Use these as pre-fixture and pre-payment screens. Focus: fast signals, the proof you want on file, and where commercial arguments usually break down later.
| # | Screening Check | Signal Strength | Proof Pack to Gather | Dispute and Claim Exposure | Practical Move |
|---|---|---|---|---|---|
| 1 |
AIS silence windows on risk-prone routes
Unexplained gaps, long off periods, or repeated dark stretches across multiple voyages.
|
High if repeated
A single gap can be innocent. Patterns are what get scrutinized.
|
|
|
Treat repeated gaps as a trigger for enhanced screening and a timeline note you can hand to a bank or insurer without rework. |
| 2 |
AIS track anomalies and identity inconsistencies
Impossible jumps, odd coordinates, or identity fields that do not align with the vessel’s IMO profile.
|
High
Often treated as an integrity signal rather than a technical glitch.
|
|
|
Pause deal flow until identity fields and track logic are reconciled and documented in a short, dated note. |
| 3 |
Ship-to-ship activity with thin commercial rationale
STS events outside expected zones or without a clean custody story tied to cargo quantity and timing.
|
High
Risk rises sharply when documentation does not match movement data.
|
|
|
Require a simple chain-of-custody narrative that matches timestamps and quantities before funds move. |
| 4 |
Successive STS chain behavior
Two or more STS transfers in a short sequence, especially when the route becomes opaque between events.
|
High
Commonly viewed as an origin masking pattern when the chain cannot be explained cleanly.
|
|
|
Escalate to enhanced due diligence and treat missing links as a stop signal for payment timing. |
| 5 |
Voyage behavior that does not fit the stated trade
Loitering, repeated deviations, unusual anchoring, or short calls that do not align with the declared operational plan.
|
Medium alone
Becomes high when paired with AIS issues, STS activity, or opaque ownership signals.
|
|
|
Build a clean timeline note now. Later reconstruction is where positions get weak fast. |
🚩 Shadow Fleet Sanctions Red Flags Continued
| # | Screening Check | Signal Strength | Proof Pack to Gather | Dispute and Claim Exposure | Practical Move |
|---|---|---|---|---|---|
| 6 |
Flag hopping and registry credibility concerns
Recent flag changes, inconsistent registration details, or a registry trail that looks thin or irregular.
|
Medium alone
Moves toward high when paired with AIS anomalies, STS chains, or opaque ownership signals.
|
|
|
Require screenshots or confirmations from authoritative sources and file them with the fixture documentation. |
| 7 |
Ownership opacity and control that cannot be explained quickly
Layered entities, nominee structures, or unclear beneficial owner and control relationships.
|
High
This is one of the most common triggers for enhanced diligence by banks and insurers.
|
|
|
Build a one-page control map you can attach to the file and reuse if the vessel appears again. |
| 8 |
Rapid rotation of owner, operator, or ISM manager
Frequent changes in the entities that control operations or compliance responsibilities.
|
Medium to high
The faster the churn, the more questions you can expect from counterparties and compliance teams.
|
|
|
Treat churn as a prompt to refresh screening and lock down who is authorized to instruct and approve. |
| 9 |
Unusual payment routes, intermediaries, or invoice structures
Payments to unexpected entities, last-minute account changes, or routing through unrelated intermediaries.
|
High
High friction area for banks. Also a common source of later allegations around intent and knowledge.
|
|
|
Put a hard rule in place: account changes require independent confirmation through a trusted channel, not email replies. |
| 10 |
Documentation integrity problems and internal contradictions
Edits, mismatched dates, inconsistent names, or clean paperwork that conflicts with voyage behavior or custody events.
|
High
This is the point where files fail under scrutiny because the story cannot be reconciled.
|
|
|
If the paper trail cannot be reconciled in one page, do not rely on it. Escalate and tighten before proceeding. |
🚩 Shadow Fleet Sanctions Red Flags Continued
| # | Screening Check | Signal Strength | Proof Pack to Gather | Dispute and Claim Exposure | Practical Move |
|---|---|---|---|---|---|
| 11 |
Sudden destination or consignee changes late in the chain
Late switches to discharge, final buyer, or receiving entity that do not match the original commercial plan.
|
Medium to high
Risk rises when the change is paired with new intermediaries or unusual payment routing.
|
|
|
Treat last-minute switches as a formal re-screen trigger and document the rationale in writing before performance continues. |
| 12 |
Cargo origin proof that does not reconcile cleanly
Bills of lading, certificates, and voyage history that do not align into a single consistent story.
|
High
Origin ambiguity is one of the fastest ways to trigger enhanced diligence or blocked payments.
|
|
|
If the origin story cannot be summarized in one page with matching dates, escalate and tighten before lifting or paying. |
| 13 |
Price and commercial terms that do not pass a normal market test
Deep discounts, unusual premiums, or fees that appear designed to move value through side channels.
|
Medium
Becomes high when paired with opaque intermediaries or third-party payment arrangements.
|
|
|
Put the rationale on paper. A short memo explaining pricing logic can prevent a lot of downstream friction. |
| 14 |
Counterparty reluctance to answer routine diligence questions
Stonewalling on basic requests like ownership, instructions, documentation versions, or screening confirmations.
|
High
A refusal pattern is often treated as a risk indicator by compliance teams and banks.
|
|
|
Make non-cooperation a defined stop signal. If you proceed, document the senior-level approval and why. |
| 15 |
Insurance and compliance clauses that quietly shift sanctions risk to you
Sanctions exclusions, warranties, or contractual pass-throughs that leave your side holding the bag if a payment or voyage is blocked.
|
Medium to high
This is less about the vessel and more about the paper that governs disputes and recoveries.
|
|
|
Before fixing, write a one-paragraph risk allocation summary internally: who carries the sanctions and payment-block risk and under what triggers. |
This checklist is meant to keep commercial teams out of “we should have seen that coming” territory. Most shadow fleet exposure is not one dramatic signal, it is a cluster of small inconsistencies across tracking, ownership, documentation, and payments. Catching those early can prevent delayed settlements, denied cover, terminated fixtures, and the time sink of rebuilding a file after the fact.
At the same time, this is just a screening tool, not a verdict. AIS gaps can be benign, routing can change for operational reasons, and paperwork issues are sometimes simple admin errors. The point is to flag patterns that deserve a tighter proof pack and an internal escalation, so if a bank, insurer, auditor, or regulator asks questions later, you can show a reasonable, documented process rather than a reconstructed story.
We welcome your feedback, suggestions, corrections, and ideas for enhancements. Please click here to get in touch.