OFAC sanctions Iran-based BitBank over alleged Hormuz Safe Bitcoin payments to IRGC
Treasury also designated BitBank’s developer and three Babak Zanjani associates tied to alleged sanctions-evasion rails.
The US Treasury’s Office of Foreign Assets Control added Iran-based crypto exchange BitBank to its sanctions list on Sept. 18, alleging the venue processed Strait of Hormuz-linked Bitcoin payments that were routed to Iran’s Islamic Revolutionary Guard Corps. The designation also names BitBank’s developer and Zanjani-linked associates, extending a 2026 enforcement pattern that raises counterparty and compliance risk for traders.
OFAC Adds BitBank to the Iran Crypto Sanctions List, Citing Hormuz Safe BTC Flows
OFAC designated Iran-based crypto exchange BitBank on 2026-09-18, alleging the exchange processed Bitcoin paid by ships transiting the Strait of Hormuz and that those payments were transferred to Iran’s Islamic Revolutionary Guard Corps (IRGC). OFAC is the US Treasury office that administers and enforces sanctions, and a designation typically means US persons are prohibited from dealing with the listed parties.
Treasury said that as of June, the Hormuz Safe Marine Services Authority used BitBank to transfer payments it received to the IRGC. Treasury has previously alleged Hormuz Safe is part of an IRGC-backed maritime scheme that forces vessels to buy insurance for passage through the Strait of Hormuz, including coverage against seizures by Iran itself.
The designations also included BitBank’s developer, Pishtaz Simorgh Electronic Trade Company, and three associates of Iranian financier Babak Zanjani. Treasury described the set as “key components of the Iranian regime’s digital assets-based sanctions evasion infrastructure.”
Treasury Secretary Scott Bessent framed the action as a reach statement aimed at crypto rails, saying: “Today’s designations of Iranian digital asset infrastructure make perfectly clear that efforts to finance the Iranian regime using cryptocurrencies are not beyond OFAC’s reach.”
Operationally, name confusion is part of the risk surface. Treasury’s designation lists the Iranian BitBank as established in 2024 and explicitly distinguishes it from Japan-based bitbank, inc, a separate exchange founded in 2014 that was acquired by SBI Holdings in June.
Why This Matters for Traders: Counterparty Risk, Screening, and Knock-On Freezes
A designation is not a market narrative. It is a compliance event with hard edges. Once an exchange and related entities are listed, counterparties that touch those flows tend to de-risk fast, even outside the US, because the cost of getting screening wrong is asymmetric.
The immediate trader-facing issue is counterparty exposure. Any direct interaction with the designated exchange is the obvious problem, but the second-order risk is indirect: deposits, withdrawals, OTC settlement, and liquidity relationships that unknowingly route through sanctioned infrastructure can get frozen or rejected when they hit a compliant venue or service provider.
Screening friction is also real here because the sanctioned entity shares a name with a Japan-based exchange. Desk ops that rely on ticker-like name matching, headlines-driven triage, or shallow vendor mappings can misclassify exposure in both directions, either blocking the wrong counterparty or missing the sanctioned one.
Treasury also tied BitBank to an alleged pipeline involving maritime payments and Bitcoin, not just stablecoins. That matters because 2026 enforcement has made USDt freezes a visible tool, but this action is a reminder that sanctions risk is being framed as asset-agnostic when the alleged end beneficiary is the IRGC.
Enforcement Trajectory: From Exchange Sanctions to USDt Freezes
This designation lands inside a clear 2026 cadence. Treasury sanctioned four crypto exchanges in June, including Iran’s largest exchange, Nobitex. Treasury sanctioned two more digital asset exchanges in August, Shelbit and Aban Tether, accusing them of assisting the Iranian regime in sanctions evasion.
In July, the US government ordered the freezing of more than $130 million in USDt held in wallets linked to Iran. USDt is Tether’s dollar-pegged stablecoin and a common settlement asset for cross-border crypto flows, so freezes function as a choke point when they can be coordinated.
The open question is how much identifying detail comes next. The packet does not include wallet addresses, domains, or an on-chain trail supporting Treasury’s claim that an “architecture” linked to Zanjani moved “hundreds of millions of dollars in Bitcoin” to the IRGC. Traders should treat the scale as an allegation, while still treating the designation itself as binding reality.
The next signals are mechanical, not rhetorical: whether OFAC publishes additional identifiers tied to BitBank or Pishtaz Simorgh that compliance tools can ingest, whether there are follow-on actions resembling July’s USDt freeze, and whether additional Iran-linked exchange designations follow given the June/August/September tempo. A public response from BitBank or any evidence release addressing the June 2026 Hormuz Safe-to-IRGC transfer allegation would also change how this trades as risk.
My Take: The Message Is Reach, Not Proof—And the Gaps Still Matter
The threshold that matters is not the “hundreds of millions” line. It is whether OFAC turns this into a richer identifier set that forces broad, automated de-risking across exchanges, payment rails, and compliance vendors. That is how a designation becomes market structure.
Right now, the allegation is directional but underspecified. If the identifiers stay thin, the impact concentrates in compliance teams and Iran-adjacent counterparties. If OFAC follows with domains, wallets, and linked entities, the practical effect is wider: more false positives, more blocked flows, and more forced rerouting that changes where liquidity can safely clear.
