Skip to content
RiverCore
Treasury Sanctions BitBank as Iran's Bitcoin Pipeline Grows
Iran bitcoin sanctionsOFACBitBankIran crypto exchange bitcoin launderingOperation Economic Outcast crypto

Treasury Sanctions BitBank as Iran's Bitcoin Pipeline Grows

19 Sep 20267 min readSarah Chen

The U.S. Treasury added another node to its Iran sanctions graph on Thursday, designating BitBank, an Iranian crypto exchange that Treasury says has been routing bitcoin to the regime since June. The move sits inside Operation Economic Outcast, the Trump Administration's whole-of-government pressure campaign, and it targets not just the exchange but the human and software layers behind it: financier Babak Zanjani, his developer shop Pishtaz Simorgh Electronic Trade Company, and three named associates.

What makes this designation analytically interesting is the asset choice. In July, OFAC's headline seizure numbers were dominated by Tether's USDT, which Tether itself can blacklist at the contract level. Bitcoin cannot. This is the first Iran-focused designation where the underlying rail is explicitly BTC, and that changes what "sanctioned" actually means in practice.

What Happened

According to a Thursday statement from the Department of the Treasury, as Bitcoin Magazine reported, BitBank was designated alongside Zanjani, Pishtaz Simorgh, and three individuals: Hossein Ali Zaker Hossein, Mohammad Mahdi Zaker Hossein, and Seyed Adel Heidari. Treasury frames the action as an attack on the "architecture Zanjani built to launder funds", language that signals OFAC is thinking in systems, not single accounts.

The operational timeline matters. Since June, the Iranian Hormuz Safe Marine Services Authority has been using BitBank to move bitcoin to the regime. Hormuz Safe itself was designated earlier this year after OFAC disclosed in July that it "accepts payment in Bitcoin and other digital assets" from ships transiting the Strait of Hormuz, a workaround for the maritime insurance and port service payments Iran can no longer clear through dollar rails. Iran also stood up a bitcoin-backed insurance service for its shipping companies earlier in 2026, which suggests the state has been treating BTC as a strategic settlement layer, not an ad hoc dodge.

Secretary Scott Bessent's public message was blunt: "If you support the Iranian regime, the Department of the Treasury will sanction you." He added that "efforts to finance the Iranian regime using cryptocurrencies are not beyond OFAC's reach." Treasury also flagged that it will pursue "international entities and actors which help facilitate" the Iranian digital asset ecosystem, which is the sentence that should be read most carefully by any non-Iranian exchange, OTC desk, or custody provider with even indirect flow exposure.

Technical Anatomy

The core asymmetry in this story is the difference between a permissioned token and a permissionless one. In July, when the U.S. froze crypto linked to the Iranian regime, most of it was USDT, because Tether Limited can call a blacklist function on the issuing contract and render specific addresses unable to transfer. That is a governance capability baked into the token's smart contract layer, and it is why stablecoin issuers effectively operate as sanctioned-list enforcement agents.

Bitcoin has no such function. There is no admin key, no issuer, no upgradeable contract, no equivalent of an ERC-20 blacklist. A designation against a BTC address is a designation against a string of characters. It changes the legal risk for any regulated counterparty that touches coins traceable to that address, but it does not stop the coins from moving on-chain. That is the entire design goal of the base layer, and it is why Treasury is targeting the human and corporate perimeter (exchanges, developers, financiers) rather than the protocol.

Enforcement therefore becomes a chain-analysis problem. OFAC and its contractors need to cluster BitBank-controlled addresses, tag outputs, and push those attributions to every regulated venue globally so that deposits from tainted UTXOs get rejected or frozen at the fiat off-ramp. The Hormuz Safe flow, ship pays BTC, BTC is aggregated through BitBank, BTC is eventually converted into something the regime can spend, has multiple choke points, but almost all of them are outside U.S. jurisdiction. Mixers, non-KYC swap services, and OTC desks in permissive jurisdictions are the obvious pressure release valves.

The source does not disclose the on-chain volume BitBank has moved since June, which is the single number that would let us judge whether this designation is symbolic or materially disruptive. A useful public bound: if the flow is under roughly 100 BTC per month, Treasury is fighting a signaling battle; if it's an order of magnitude larger, we should see visible clustering activity from firms like Chainalysis and TRM within weeks.

Who Gets Burned

The most exposed cohort is non-U.S. exchanges with weak sanctions screening on BTC deposits. Treasury explicitly warned it will pursue "international entities and actors which help facilitate" the Iranian ecosystem, and secondary sanctions have historically been the mechanism that turns a domestic designation into a global compliance event. Any exchange in the Gulf, Turkey, or Southeast Asia that has processed deposits traceable to BitBank clusters now has a discovery problem and a remediation problem, both on a compressed timeline.

Custodians and prime brokers serving institutional bitcoin allocators are the second ring. If a regulated fund accidentally receives coins with BitBank taint through a market maker or an OTC fill, the fund's custodian is the entity that has to freeze, report, and eventually justify the exposure. Expect custody agreements to get amended in the next quarter with more aggressive taint-lookback clauses.

Stablecoin issuers, particularly Tether, are in an odd position. They have been the primary enforcement surface for OFAC on the Iran file, which has made them politically useful but also concentrated their regulatory risk. If Iran is deliberately migrating flows to BTC precisely because USDT is freezable, Tether gets to look cooperative while losing volume; that's a rare win for an issuer that usually loses on both axes.

Chain-analysis vendors get a business boost. Every designation of this type generates fresh attribution work, and the named entities (Pishtaz Simorgh as a software developer, three individual associates) give investigators identity anchors to pivot from. We do not know from the source what infrastructure Pishtaz Simorgh actually built, which matters because if the shop authored BitBank's matching engine or wallet software, the code artifacts themselves become intelligence.

Testable prediction: within 90 days, expect at least one non-U.S. exchange to announce a delisting or geo-block tied specifically to BitBank-linked addresses, and at least one secondary designation of a foreign intermediary.

Playbook for Crypto and DeFi

For any team touching bitcoin flows in a regulated capacity, three concrete actions belong on this week's sprint.

First, run a taint audit against the newly designated cluster as soon as vendor attributions are published. That means pulling deposit histories back at least to June 2026 (when Hormuz Safe began routing through BitBank), flagging any address matches, and preparing SAR filings or equivalent reports in your jurisdiction. Do not wait for a subpoena; voluntary disclosure has been the difference between fines and enforcement actions in prior OFAC crypto cases.

Second, tighten deposit screening thresholds on BTC specifically. Most exchanges have been operating with looser BTC taint rules than USDT rules, on the implicit theory that stablecoin freezes catch the worst actors. That theory is now stale. If Iran is deliberately routing to BTC to avoid issuer-level blacklists, the compliance load shifts back to the venue layer, and screening rules need to reflect that.

Third, for DeFi teams building bridges, wrapped BTC products, or BTC-collateralized lending, review your minting and redemption paths. Wrapped BTC issuers have historically been softer on source-of-funds than centralized exchanges, and any protocol that accepts BTC deposits and issues an ERC-20 or SPL token is a natural laundering candidate. The EVM and Solana ecosystems both host meaningful wrapped-BTC liquidity, and both are now in-scope for the "international entities and actors" language.

For crypto-native founders considering fiat on-ramp partnerships, expect banking partners to add BitBank-cluster attestations to their onboarding questionnaires within the next quarter.

Key Takeaways

  • Treasury designated BitBank, Babak Zanjani, Pishtaz Simorgh, and three associates under Operation Economic Outcast, targeting a bitcoin pipeline active since June 2026.
  • This is the first major Iran-focused designation where the primary rail is BTC, not USDT, because BTC has no issuer-level freeze function.
  • The source does not disclose transaction volume, so enforcement impact hinges on chain-analysis attribution speed at non-U.S. venues.
  • Secondary sanctions language ("international entities and actors") puts foreign exchanges, OTC desks, and wrapped-BTC bridges on notice.
  • Prediction: within 90 days, expect at least one non-U.S. venue delisting tied to BitBank clusters and one secondary designation of a foreign intermediary.

Frequently Asked Questions

Q: Why did the U.S. sanction BitBank specifically?

Treasury says BitBank has been used by the Iranian Hormuz Safe Marine Services Authority since June 2026 to move bitcoin to the regime. The designation targets what OFAC calls the "architecture Zanjani built to launder funds", meaning the exchange, its developer, its financier, and named associates.

Q: Can OFAC actually freeze the sanctioned bitcoin?

No, not directly. Bitcoin has no issuer and no admin function to blacklist addresses, unlike Tether's USDT, which can be frozen at the contract level. Enforcement instead relies on regulated exchanges and custodians globally refusing deposits from tainted addresses.

Q: What should compliance teams at crypto exchanges do this week?

Run a deposit history audit back to June 2026 against BitBank-linked address clusters as soon as chain-analysis vendors publish attributions, tighten BTC-specific screening rules, and review wrapped-BTC or bridge minting paths for source-of-funds gaps.

SC
Sarah Chen
RiverCore Analyst · Dublin, Ireland
SHARE
// RELATED ARTICLES
HomeSolutionsWorkAboutContact
News06
Dublin, Ireland · EUGMT+1
LinkedIn
🇬🇧EN▾