A new name, the same identifiers: The Pegasus OFAC settlement and what it means for freight forwarders
A renamed supplier kept its listed email and telephone details. Pegasus missed those matches, continued after a customs detention notice and then failed to produce complete subpoena records.
Sanctions · 10 Oct 2026
A sugar packet-filling machine intended for legitimate commercial use became the subject of a sanctions settlement. The supplier was blocked; the machinery's intended use did not resolve that counterparty problem. For a freight forwarder, importer or company arranging a U.S. shipment, the case presents a concrete operational question: does your review connect the supplier's name with the other identifying information already in your records? In Pegasus's case, a changed name defeated a manual name check even though the supplier's listed telephone number and email address remained available.
What happened
On October 9, 2026, OFAC announced a $175,015 settlement with Pegasus Worldwide Logistics, a California logistics company and freight forwarder. The announcement identifies four apparent counter-narcotics violations and six apparent reporting violations. Pegasus agreed to settle its potential civil liability; the facts below are OFAC's account of the apparent violations.
According to OFAC's enforcement release, October 9, 2026, pp. 1–3, Pegasus had about a dozen employees. A U.S. nutritional supplement company engaged it in August 2023 to coordinate the purchase and shipment of a customized sugar packet-filling machine worth $5,950. OFAC's investigation found that the intended purpose was legitimate commercial activity.
The supplier, Youli Technology Development Co., Ltd., had been designated on May 30, 2023. After designation it changed its name to Huizhou Youli Fushi Co., Ltd., while other identifiers remained unchanged. Pegasus communicated with the supplier through an email address listed by OFAC and received shipping documents containing its listed telephone number. Those details did not lead to a match because Pegasus screened the new name alone.
The screening instruction that did not reach the transaction
Pegasus's policy called for comparing names, addresses, email addresses, telephone numbers and other transaction information against OFAC's list. The employee's name-only check departed from that policy. OFAC says screening the other identifiers would have identified Youli.
Timing compounded the problem. The procedure did not specify when to screen. Pegasus waited until shortly before the machine was to leave China, after it had already engaged in conduct OFAC described as prohibited. By September 12, 2023, it had instructed Youli to arrange shipment through a Chinese shipping agent. On or after September 28 it paid that agent $146.33 for transportation.
The machine reached Long Beach on October 11, 2023. On November 3, Customs and Border Protection notified Pegasus of detention and identified OFAC as the responsible agency. Pegasus did not investigate further. It subsequently paid a $1,463.55 duties-and-fees invoice and received $2,358.62 covering those charges and its forwarding fees. CBP seized the machine as blocked property on December 6.
Firm control observation: A screening policy needs an operational trigger and a way to reconcile inconsistent identifiers. If a supplier changes its name while retaining a familiar email address or telephone number, route that discrepancy for review before further instructions or payments. A customs detention referring to OFAC should trigger a documented assessment of the transaction and any proposed next step. These are practical recommendations drawn from the case, not additional legal requirements announced by the firm.
A missing records search became a separate problem
OFAC's administrative subpoena supplied three name variations and other identifiers for Youli. On February 1, 2024, Pegasus certified that it had no responsive information. OFAC then supplied an arrival notice demonstrating Pegasus's involvement. Only afterward did Pegasus locate responsive records. It also told OFAC that it had not given its attorney all the necessary information when the response was prepared.
On August 8, 2024, six months after the initial certified response, Pegasus supplied a revised response describing its involvement. OFAC identifies six reporting violations for the failure to furnish complete information over that period. The reporting issue therefore had its own penalty significance; it was not merely a missed opportunity for mitigation.
Firm control observation: Before a company certifies a response, identify the relevant staff, shipment files, communications, invoices and payment records, and search using the names and other identifiers supplied in the request. Record what was searched and resolve gaps with counsel. Giving counsel only the records initially found does not establish that the company conducted a complete inquiry.
The penalty — and why it landed where it did
OFAC classified the apparent violations as non-egregious and not voluntarily self-disclosed. The release states a $205,900 base civil monetary penalty, representing the applicable schedule amounts, and a $175,015 settlement after consideration of the agency's factors. The base amount and the final settlement are different figures.
The aggravating factors concerned Pegasus's screening and failure to investigate the detention; its awareness of dealings with a supplier it had reason to know was sanctioned; support for the supplier's continued exports and profit, together with delay to OFAC's investigation; and the sanctions attention warranted by its international logistics role.
The mitigating factors included no OFAC enforcement action during the five years preceding the earliest relevant transaction, the company's small size and relatively low-value transactions, and extensive agreed remedial measures. Those measures included outside sanctions expertise and regular, detailed reports to OFAC over an extended period. The release does not assign a numerical reduction to each factor or provide a formula for another company's settlement.
What this means for you
For a European company using U.S. logistics or arranging U.S. imports, the relevant lesson is to review the actual parties, records and transaction path. This article does not assume that every European contract is subject to U.S. sanctions.
Ask whether your process can answer three case-specific questions: Who checks the identifiers before the company commits to a shipment? Who evaluates a detention notice before another payment or instruction? Who confirms that the records sent to counsel address the full information request? A written policy is useful only when those responsibilities reach the people handling the transaction.
Building the program you can actually stand behind
You can scope a bounded review around one shipment, the counterparty identifiers and the company's escalation and records process. That gives management a specific set of decisions to examine rather than an assumed assurance that a name check resolved the risk. Contact Zimmermann Law to discuss a company-side U.S. sanctions review of that defined issue.
This post provides general information, not legal advice. Sanctions analysis is fact-specific and changes over time.
Sources: OFAC, “Pegasus Worldwide Logistics Settles with OFAC for $175,015 for Apparent Violations of Counter Narcotics Sanctions,” enforcement release, October 9, 2026, pp. 1–5 (original `20261009_pegasus.pdf`); OFAC, October 9, 2026 settlement announcement, Pegasus paragraphs. Both read October 10, 2026. These primary U.S. federal agency sources establish OFAC's settlement announcement and its account of apparent violations; the enforcement observations are persuasive compliance guidance, not a judicial determination or a substitute for mandatory governing law. Practical control observations are the firm's recommendations. This dated account does not independently verify current regulations, transaction-specific permission or foreign law.
This post is for general information and is not legal advice.
Attorney Advertising. Zimmermann Law PLLC · New York · +1 (917) 426-4625 · contact@zimmermann-law.com