CryptaCount
EN
EnglishENDeutschDEEspañolESFrançaisFRItalianoIT日本語JA한국어KONederlandsNLPolskiPLPortuguêsPT
Log in Start Free

OFAC Sanctions Iranian Exchange BitBank Over IRGC Bitcoin Transfers

CryptaCount Editorial · · 8 min read
AML / KYC / LICENSING OFAC Sanctions Iranian Exchange BitBankOver IRGC Bitcoin Transfers

The US Treasury Department designated Iranian crypto exchange BitBank on 17 September 2026, alleging it moved hundreds of millions of dollars in bitcoin to the Islamic Revolutionary Guard Corps. The action expands the SDN list by six entries, including BitBank's software developer and three individuals, and sits inside a broader sanctions campaign called Operation Economic Outcast. For accounting firms, auditors, and CFOs running digital asset operations, the designation creates immediate screening obligations and raises pointed questions about the adequacy of existing crypto accounting software controls.

OFAC Sanctions Iranian Exchange BitBank Over IRGC Bitcoin Transfers

What OFAC Actually Designated and Why

The Office of Foreign Assets Control named six parties in Thursday's action:

  • BitBank, the Iranian crypto exchange at the centre of the allegations.
  • Pishtaz Simorgh Electronic Trade Company, identified as BitBank's software developer.
  • Hossein Ali Zaker Hossein, Mohammad Mahdi Zaker Hossein, and Seyed Adel Heidari, named as associates of Iranian financier Babak Zanjani.
  • Zanjani himself was already on the SDN list for operating a network of companies alleged to have laundered money and evaded Iran sanctions.

Treasury Secretary Scott Bessent stated in the release: "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. If you support the Iranian regime, the Department of the Treasury will sanction you."

The Alleged Transaction Flow

According to Treasury, Zanjani used BitBank between June and July 2026 to route hundreds of millions of dollars in bitcoin to the IRGC, a body designated as a terrorist organisation by the US, the European Union, and multiple other governments. A separate entity, the Hormuz Safe Marine Services Authority, is alleged to have used the exchange since June to transfer payments to the Iranian regime.

Hormuz Safe appears to be the formal structure behind a marine insurance platform first reported by Iranian media in May 2026. The platform was promoted as covering vessels transiting the Strait of Hormuz, a commercially sensitive chokepoint, and Iran reportedly targeted more than $10 billion in revenue from the scheme.

Operation Economic Outcast: The Broader Campaign

Thursday's designations are not a standalone action. They extend a campaign called "Economic Fury," which targeted Iran's largest crypto exchange, Nobitex, in June, alongside Wallex, Bitpin, and Ramzinex. Treasury stated at that time that Nobitex processed more than half of Iran's digital asset inflows in 2025 and facilitated transactions involving the IRGC and other sanctioned entities.

Operation Economic Outcast, the successor campaign, was formally launched on 24 August 2026. The BitBank designations are the latest enforcement tranche under that umbrella. The pattern matters for compliance teams: OFAC is systematically working through Iranian digital asset infrastructure, targeting exchanges, their technology vendors, and the individuals who control them.

Why the Developer Designation Is Significant

Designating Pishtaz Simorgh Electronic Trade Company, the entity that built BitBank's software, is a deliberate escalation. It signals that OFAC is prepared to reach behind the exchange itself and target the technical layer enabling sanctions evasion. Firms that provide software, APIs, or infrastructure services to crypto platforms should treat this as a direct warning: supplying technology to a designated exchange carries its own SDN risk.

For firms using digital asset accounting and compliance frameworks, this reinforces the need to conduct vendor due diligence not just on trading counterparties but on the technology providers those counterparties rely upon.

AML Implications for Accounting Firms and CFOs

Every US person and entity is now prohibited from transacting with BitBank, Pishtaz Simorgh, and the three named individuals. Any property or interests in property of those parties within US jurisdiction must be blocked and reported to OFAC. The same blocking obligation extends to entities owned 50 percent or more, directly or indirectly, by any designated party.

Immediate Screening Steps

Compliance officers should take the following steps without delay:

  • Pull the new SDN entries into your screening system and run a retrospective check across all counterparty records, wallet address databases, and transaction histories.
  • Identify any clients or counterparties who may have used BitBank as a fiat on-ramp or off-ramp, even if the exchange was not the direct transaction partner visible in your ledger.
  • Review any vendor contracts that touch Iranian digital asset infrastructure. The Pishtaz Simorgh designation makes software supply chains a live issue, not a theoretical one.
  • Check whether your crypto bookkeeping software or digital asset accounting software provider has updated its sanctions screening lists to include the new addresses associated with this action. If not, escalate to the vendor immediately.

Firms that previously covered the OFAC action freezing USDT linked to Xinbi will recognise the structural parallel: OFAC is consistently targeting the exchange layer, the technical infrastructure, and the human controllers as a combined set of designations rather than singling out individual wallets.

Ledger Implications for Firms Holding or Custodying Bitcoin

If any bitcoin held in custody or on behalf of clients passed through BitBank at any point, firms face two accounting-level problems. First, the regulatory risk of holding tainted assets, even if the firm was an unwitting downstream recipient. Second, the disclosure question: does the firm's audit trail demonstrate it had no knowledge of the origin and took reasonable steps to verify the counterparty chain?

Robust crypto accounting software should allow a firm to reconstruct the full transaction graph for any asset in custody. If your current tooling cannot trace inbound bitcoin to its originating exchange or counterparty cluster, that is a gap that this enforcement action should prompt you to close.

The Iran Sanctions Enforcement Trajectory

Taken together, the Economic Fury and Operation Economic Outcast campaigns represent a sustained, methodical effort to cut Iran's digital asset access. The pattern across 2025 and 2026 is consistent: OFAC identifies a high-volume exchange, documents its IRGC or regime connections, designates the exchange alongside its developers and controllers, and then moves to the next target.

This trajectory has a direct read-across to the risk calculus for any firm with global digital asset exposure. Exchanges operating in or for jurisdictions under comprehensive US sanctions are not a niche compliance edge case; they are an active enforcement priority. Firms relying on passive or infrequent sanctions screening are exposed.

It is also worth placing this alongside the earlier action targeting Iranian oil sanctions evasion, where the US sought a substantial crypto forfeiture. Our earlier coverage of the US forfeiture action tied to Iranian oil sanctions evasion shows the same enforcement machinery at work across different asset classes and transaction types.

What Auditors Should Be Asking Clients Right Now

Audit engagements covering any client with digital asset holdings or crypto-native operations should include updated AML inquiries in light of this designation. Specific questions to raise:

Client-Facing Due Diligence Questions

  • Has the client transacted with any Iranian crypto exchange, including but not limited to those named in the Economic Fury or Operation Economic Outcast campaigns?
  • Does the client's transaction monitoring system cover OFAC SDN updates in real time, or is the screening periodic?
  • If the client holds bitcoin acquired from OTC desks or peer-to-peer channels, what counterparty documentation exists?
  • Has the client's technology vendor confirmed that the newly designated wallet addresses are included in its screening parameters?

The Hormuz Safe connection adds a further wrinkle: if any client operates in shipping, marine insurance, or trade finance and has digital asset exposure, the alleged use of BitBank by Hormuz Safe is a specific red flag that warrants a targeted inquiry.

OFAC Sanctions Iranian Exchange BitBank Over IRGC Bitcoin Transfers

Frequently Asked Questions

What does an OFAC designation mean in practice for a US accounting firm?

Once an entity is added to the SDN list, US persons and firms are prohibited from entering into any transaction with that entity, directly or indirectly. Any assets belonging to the designated party that come into the firm's possession must be blocked and reported to OFAC. Violations can result in civil penalties even if the firm had no knowledge of the sanctions nexus, so real-time screening and documented due diligence are the primary defences.

Does the designation affect firms outside the United States?

Non-US firms do not face the same primary sanctions obligation, but secondary sanctions risk is real. Any non-US entity that facilitates a significant transaction with a designated party may itself become subject to US sanctions, cutting it off from the US financial system. Global firms with US dollar settlement exposure or US counterparties should treat OFAC designations as operationally relevant regardless of their domicile.

Why did OFAC designate a software developer alongside the exchange?

Designating Pishtaz Simorgh extends the blocking obligation to the technical infrastructure enabling BitBank's operations. It also signals that OFAC views technology providers as participants in sanctions evasion, not neutral third parties. Firms that supply software, APIs, or data services to crypto platforms should review their client lists against the SDN database as part of routine vendor management.

How should firms update their crypto accounting software controls after this action?

Firms should verify that their digital asset accounting software provider has ingested the new SDN entries, including any associated wallet addresses published by OFAC. Where the software supports counterparty tagging, BitBank and associated entities should be flagged as prohibited. Firms should also run a retrospective screen of historical transaction data to identify any prior interactions and document the review in their AML files.

What is Operation Economic Outcast and when did it begin?

Operation Economic Outcast is a US Treasury campaign targeting entities that help Iran evade sanctions through digital assets and other financial channels. It was formally launched on 24 August 2026, building on the earlier Economic Fury campaign that targeted Iranian crypto exchanges including Nobitex in June 2026. The BitBank designations on 17 September 2026 are the latest enforcement tranche under this operation.

Source: The Block

USGLOBALGeneralEnforcementAML/KYC & Licensing

Related articles

AML/KYC & Licensing
US Sanctions Iran's BitBank Over IRGC Bitcoin Transfers
AML/KYC & Licensing
Al-Qassam Brigades DOJ Filing: What Crypto Firms Must Know Now
AML/KYC & Licensing
Terrorist Financing Shifts to USDT on TRON: 25 Years After 9/11
AML/KYC & Licensing
US Seizes $61M in Crypto Tied to Iranian Oil Laundering