How It Works
This cargo theft scheme starts with business email compromise. Fraudsters enter or mimic correspondence between a shipper and broker, to arrange or confirm a pickup while posing as a real motor carrier.
The credentials used are real: an active USDOT number, a real company name, and a valid driver’s CDL. The truck that shows up at the dock or warehouse is legitimate, but it is not the carrier the shipper hired.
After the freight leaves, the contracted carrier may not discover the theft until days later. Then the second payday begins: the same crew contacts the victim and demands cryptocurrency for the load’s location. The result is both cargo theft and extortion. First, they resell the freight, then they charge the victim for information about it.
Why It Works
The scheme works because dock procedures often confirm that an identity is valid. It does not confirm that it is the correct identity/carrier for the transaction. A real carrier record does not prove the person standing at the dock is authorized for that pickup. Processes that check credentials against a registry without tying back to the contracted party has a hole in it.
How To Respond
When handling these files, ask whether anyone contacted the insured after the theft to offer the freight’s location or demand payment. Preserve email evidence early, including full email headers, suspect domain details, and where fraudulent messages entered the thread. If ransom was demanded, capture wallet addresses, phone numbers, and messages exchanged so they can be compared against other cases.
This theft scheme may involve cargo, crime, and cyber policies, so routing the file to the right teams early is key.
For insureds and clients, emphasize simple controls: verify any change to carrier arrangements using a phone number already on file, use a callback or shared code word before release, and train dispatch on email compromise red flags.
The fix is not better document checking alone. It is confirming the right identity through a trusted channel the fraudster does not control. If a file fits this pattern, or an insured mentions post-theft ransom contact, involve SIU early so the identifiers can be captured.




%20(1).webp)
.webp)