A Fake Broker Nearly Redirected $273,000 in Seafood

What police reported

North Arlington police said a refrigerated-truck driver received calls and texts from someone claiming to represent the shipment's freight broker. The driver was told to divert part of the load. About 29,000 pounds of frozen seafood, valued at more than $273,000, was being transferred to a box truck when the transfer was questioned.

Police recovered the seafood and arrested an 18-year-old and a juvenile, according to local reports. The 18-year-old was charged with theft by deception, false representation, conspiracy, and employing a juvenile in a crime. The charges are allegations; the reports do not give the case's final outcome.

The reports do not say how the impersonator learned about the load, and they do not establish that any email, load-board, transportation management system (TMS), or phone account was compromised. The case is evidence of attempted impersonation and load diversion—not proof of a cyberattack.

• Patch: Police stop teen from stealing 14 tons of fish in Bergen County
• The Observer: North Arlington police report of the attempted theft

Verify before the truck moves

Load plans change. A delivery window moves, a facility closes, or freight needs a cross-dock. That makes an urgent, plausible request easy to accept without checking who sent it. A caller's familiarity, caller ID, or knowledge of the load is not authorization.

Make the rule simple: no destination change, freight transfer, trailer release, or substitute carrier based only on an incoming call, text, or email.

1. Pause the move. Keep the truck and freight where they are until dispatch confirms the change.
2. Call dispatch using a saved company number or approved system—not a number or link supplied in the request.
3. Have dispatch confirm with a broker, shipper, or receiver using contact details already on file. FMCSA records can help verify a business, but they do not prove who is on the phone.
4. Require a second approval for changes to destination, custody, or carrier. Match the load number, facility, receiver, and replacement driver or equipment against the original instructions.
5. Record who approved the change. If details conflict or the request cannot be verified, do not proceed.

• FMCSA: Broker and carrier fraud and identity theft
• Cargo theft prevention for small trucking companies
• Freight broker email security: verify load and payment changes

If a transfer cannot be verified

Treat the request as a possible theft in progress. Keep one person coordinating the response and contact people using numbers already on file.

1. Tell the driver not to transfer or release the freight. Contact local law enforcement if theft may be underway.
2. Notify the legitimate broker, shipper, receiver, and insurer under your response procedures.
3. Preserve the original calls, messages, shipment records, and account alerts. Do not delete messages or wipe devices.
4. If an account may be compromised, contact your IT provider, reset credentials from a known-clean device, and revoke active sessions.

• Cargo theft response checklist: the first 60 minutes
• FBI Internet Crime Complaint Center

Make the pause routine

Drivers and dispatchers should know that stopping to verify an unexpected transfer is the right call—not a reason to blame them for a delay. Keep after-hours contacts and approval steps in the dispatch procedure and driver materials.

Account safeguards matter too: use MFA on business email and freight platforms where available, give each worker an individual login, remove access when people leave, and ask your IT provider to review suspicious mailbox rules or sign-ins. These steps reduce account risk but do not replace the callback.

• Your dispatch email was hacked: what to do first
• Security Awareness Training

Related resources

• 10 Safety Precautions to Avoid Trucking Scams
• Cybersecurity for Freight Brokers: Protect Loads and Payments
• FMCSA Motus Phishing: Verify Suspicious Trucking Emails