OFAC Sanctions Iran's Bitcoin-Denominated Hormuz Insurance Racket
Treasury sanctioned HormuzSafe and Persian Gulf Marine Insurance Company on July 29, 2026 for forcing commercial vessels to buy mandatory IRGC-backed 'insurance' to transit the Strait of Hormuz, with Bitcoin accepted as payment to evade sanctions.

Treasury designated two IRGC-backed entities forcing ships to pay Bitcoin premiums just to transit the world's most critical oil chokepoint.
Key takeaways
- OFAC designated HormuzSafe Marine Services Authority and Persian Gulf Marine Insurance Company on July 29, 2026 for operating an extortion scheme that forces commercial vessels to buy mandatory "insurance" to transit the Strait of Hormuz, with Bitcoin explicitly cited as a payment mechanism to evade sanctions.
- Treasury framed both designations as a direct response to Iran's effort to replace revenue lost after Operation Epic Fury, the U.S.-Israeli strikes that began February 28, 2026, embedding Bitcoin payment rails into a live sanctions enforcement case.
- This action is part of a broader 2026 escalation: OFAC has now sanctioned more than 100 shadow-fleet vessels this year and has systematically targeted Iran's crypto infrastructure, including Nobitex and other exchanges designated in June, and central bank wallets.
The U.S. Department of the Treasury's Office of Foreign Assets Control designated two Iranian entities on July 29, 2026 for running what Treasury called an extortion network that forces commercial vessels to purchase mandatory coverage just to pass through the Strait of Hormuz, a waterway carrying roughly 20% of the world's oil supply. Bitcoin was explicitly cited as a payment method, part of a pattern of Iran using permissionless payment rails to route around dollar-based sanctions infrastructure.
The two designated entities are HormuzSafe Marine Services Authority, developed by Iran's Ministry of Economy, and Persian Gulf Marine Insurance Company (PGMIC), established by Central Insurance of the Islamic Republic of Iran. Both were designated under Executive Order 13902, which targets Iran's financial sector. Treasury Secretary Scott Bessent stated: "With its economy in freefall and inflation in the triple digits, the regime is desperate for cash." Bessent added that "The United States will not tolerate Iran holding international commerce hostage" and that "The Iranian regime is exploiting international shipping to fund the IRGC."
The Racket and Who Runs It
HormuzSafe and PGMIC purport to protect vessels from risks in the strait, including seizures. OFAC's position: those risks are overwhelmingly created by Iran itself. The scheme is an extension of the Persian Gulf Strait Authority (PGSA), an IRGC-backed entity previously designated under Executive Order 13224 (terrorism financing) on May 27, 2026.
Iranian financier Babak Morteza Zanjani, himself sanctioned earlier in 2026, promoted HormuzSafe to his social media followers. The scheme's connection to the IRGC runs through the PGSA and is confirmed in Treasury's designation language.
This action also added 8 shipping companies based in China, Hong Kong, and the Marshall Islands, plus 8 tankers, as blocked property for moving Iranian crude and petroleum products. OFAC has now sanctioned more than 100 vessels linked to Iran's shadow fleet since the start of 2026. Prior TFTC coverage tracked how war-risk insurance premiums surged as the Hormuz conflict escalated, and how the war premium reshaped energy and capital markets.
What OFAC Is Actually Asserting
The Iran story is the headline. The regulatory precedent is the story underneath it.
OFAC's designation language explicitly frames Bitcoin payments as the sanctions-evasion mechanism, not a footnote. That framing matters because it embeds BTC payment rails into an SDN enforcement case. Compliance teams at exchanges are already processing what this raises for their screening obligations. The next logical step in this enforcement chain is wallet-address designations tied to HormuzSafe payment flows. Watch the SDN list for those additions. That is how OFAC extended reach over on-chain activity in prior cases, including Tornado Cash.
The falsifiable line here: if OFAC's action stops at entity designations and publishes no associated Bitcoin wallet addresses or guidance on the underlying transaction flows, this is routine sanctions enforcement with a Bitcoin footnote, not a new regulatory doctrine over the protocol. If wallet addresses appear on the SDN list tied to HormuzSafe premiums, the precedent hardens significantly.
Bitcoin's use in this scheme is also worth reading clearly. Iran reached for a permissionless, neutral payment rail precisely because it cannot be unilaterally frozen by a U.S. correspondent bank. That is the feature. A sanctioned state ministry using Bitcoin to route around dollar hegemony is a live demonstration of censorship-resistance working as designed. The policy question that follows, whether the U.S. government should be the entity deciding who gets to use money, does not change based on who today's designated party is. The same surveillance-expansion logic used here will get applied further down the line.
Treasury's framing makes the financial-warfare architecture explicit: Operation Epic Fury degraded Iran's physical capacity, Iran pivoted to Bitcoin-denominated financial rails to replace lost revenue, and OFAC is now targeting those rails. The military instrument and the monetary instrument are operating as one. Prior TFTC coverage of the Shelbit sanctions case showed the same pattern at the exchange layer; this is the same pattern at the insurance and payment layer.
What to Watch
The SDN list update accompanying or following this designation is the most important data point. If OFAC publishes Bitcoin wallet addresses tied to HormuzSafe premium flows, the precedent for asserting regulatory reach over BTC transactions entirely outside U.S. jurisdiction becomes explicit and enforceable. The companion question is whether Treasury issues any supplemental guidance on what this means for non-U.S. shipping operators or exchanges that processed those payments before the designation date. Secondary sanctions exposure for non-U.S. persons dealing with OFAC-designated entities applies regardless of payment currency, and that exposure is not well understood outside compliance circles.
Sources
Frequently Asked Questions
Non-U.S. persons face secondary sanctions risk for dealing with OFAC-designated entities regardless of the payment currency. A vessel that paid Bitcoin premiums to HormuzSafe or PGMIC after the July 29 designation date would be transacting with a blocked party. For payments made before the designation, exposure depends on the timing and the nationality of the parties involved. Shipping operators and their insurers should treat this as a live compliance question, not a theoretical one.
OFAC designated the entities under E.O. 13902. The designation itself does not automatically extend to the underlying Bitcoin transactions or wallets. OFAC's mechanism for reaching on-chain activity directly has historically been wallet-address designations added to the SDN list, as seen with Tornado Cash and prior Iran-linked crypto cases. If HormuzSafe-associated wallet addresses appear on the SDN list, that is OFAC asserting reach over the payment rails themselves. If they do not, the designation remains at the entity level.
Operation Epic Fury refers to the U.S.-Israeli strikes on Iran that began February 28, 2026. Treasury's framing of the HormuzSafe scheme as Iran's revenue-replacement response to those strikes makes the financial and military operations explicitly linked. Iran lost physical capacity and revenue streams through the strikes; HormuzSafe was Iran's attempt to generate hard-currency replacement income through a Bitcoin-denominated toll on the world's most critical oil chokepoint. OFAC is treating the financial disruption as a direct continuation of that military campaign by other means.


