SanctionsLookup

Data last synced:

Trump Sanctions Russian Bank VTB Over Iran Ties: What Your Screening System Will Miss

The bank the Trump administration sanctioned today is VTB Bank, Russia's second-largest lender. The U.S. Treasury's Office of Foreign Assets Control (OFAC) added Iran-related sanctions to VTB's existing designation, accusing the bank of helping Iran evade sanctions. Treasury Secretary Scott Bessent had signaled last week that a large bank would be targeted as part of the pressure campaign on Tehran, now in its seventh month of open conflict with the U.S.

Most coverage will stop there. For compliance teams, the interesting part is in the mechanics of the OFAC action itself.

VTB was not "added" to the SDN List today

VTB has been on the SDN List since 2022, when it was fully blocked under Executive Order 14024 after Russia's invasion of Ukraine. Its sectoral designation goes back to 2014.

What happened today is a modification of an existing SDN record. OFAC published the change in its usual "-to-" format: the old entry, followed by the amended one. The deltas:

  • A new program tag: [IRAN-EO13902], alongside the existing [UKRAINE-EO13662] and [RUSSIA-EO14024] tags
  • A new address: Tehran, Iran
  • A new notation: "Additional Sanctions Information - Subject to Secondary Sanctions"
  • Every former name (f.k.a.) reclassified as a current alias (a.k.a.), from "Vneshtorgbank" to "Bank for Foreign Trade of RSFSR"
  • The parallel entry on the Sectoral Sanctions Identifications (SSI) List was amended the same way

Why modified records are the weak point of sanctions screening

Many screening programs are built around one question: is this counterparty on the list, yes or no? For VTB, the answer was already yes, so today's update changes nothing for them.

But the risk profile did change:

1. Secondary sanctions exposure now runs through Iran authorities. A non-U.S. bank or company that was already avoiding VTB under Russia programs now also faces exposure under EO 13902, which targets Iran's financial sector. If your risk scoring, escalation rules, or licensing analysis are keyed to sanctions programs rather than just list membership, VTB's profile needs to be re-evaluated, not just re-confirmed.

2. Alias handling just got harder. With every historical name promoted from f.k.a. to a.k.a., fuzzy-matching engines that de-weight former names will now score legacy names like "Vneshtorgbank" as live aliases. Expect match-score shifts on anything touching VTB's historical entities, correspondent relationships, and old trade documents.

3. Delta ingestion has to update, not append. If your list pipeline only ingests additions and removals, today's change is invisible. The record's unique ID did not change; its content did. Screening against a stale copy of the entry means screening against the wrong program tags.

What to check today

  1. Re-run screening on existing matches to VTB and its aliases, not just new customers
  2. Confirm your list provider or pipeline picked up the modified record (check the entry's program tags: it should now show three)
  3. Review any Iran-related policies: counterparties cleared under a "Russia-only exposure" rationale involving VTB no longer qualify
  4. If you operate outside the U.S., reassess secondary sanctions risk for any remaining VTB touchpoints, including its Shanghai and New Delhi branches, which are named in the entry

Quick answers

Which bank did Trump sanction?

VTB Bank Public Joint Stock Company, Russia's second-largest bank, on September 14, 2026.

Why was VTB sanctioned again?

Treasury accuses VTB of involvement in Iranian sanctions evasion. The new designation falls under Executive Order 13902, which targets Iran's financial sector.

Wasn't VTB already sanctioned?

Yes, fully blocked since 2022 under Russia authorities. Today's action adds an Iran program tag and secondary sanctions exposure to the existing record.

Also in today's OFAC action

The same release issued Venezuela-related General License 52C, authorizing certain transactions involving PDVSA, along with amended FAQ 1245. Unrelated to VTB, but worth flagging to any client with Venezuela exposure: the license replaces 52B, so payment terms and wind-down language should be re-checked against the new text.

SanctionsLookup ingests OFAC list changes, including modified records, within minutes of publication and flags when an existing match's program tags change. Try the API free.