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

US Sanctions Iran's Entire Crypto Sector Over $100M in Oil Payments

CryptaCount Editorial · · 9 min read
AML / KYC / LICENSING US Sanctions Iran's Entire CryptoSector Over $100M in Oil Payments

The US Treasury's Office of Foreign Assets Control has issued a sectoral sanctions determination that brings Iran's entire digital asset industry within its enforcement perimeter. Unlike previous actions that targeted specific exchanges or wallets, this determination means that any person or entity found to operate in, or provide services supporting, Iran's digital asset sector can now be sanctioned, without needing to be individually named first. For compliance officers, CFOs, and accounting firms handling digital asset clients, the practical implications are immediate.

US Sanctions Iran's Entire Crypto Sector Over $100M in Oil Payments

What OFAC Actually Did on 25 August 2026

On 25 August 2026, OFAC issued sectoral sanctions determinations covering six areas of Iran's economy: digital assets, technology, gold, aviation, shipping, and related services. Simultaneously, the agency sanctioned close to 60 entities, individuals, and vessels across Iran's nuclear, missile, cyber, and oil networks.

The Digital Asset Determination in Plain Terms

The digital asset component is significant precisely because of its breadth. Previous Iran-related crypto enforcement had focused on named platforms: OFAC's January 2026 action was its first-ever designation of Iranian digital asset exchanges, and a further round in early June 2026 caught the country's largest platform, Nobitex. The August determination goes further. It establishes that participation in Iran's digital asset sector, as a category, is now a sanctionable activity under Executive Order 13902. OFAC does not need to identify a specific transaction or named entity before acting; operating in the sector is itself sufficient grounds for designation.

The Treasury stated the determination "significantly expands" its authority to sanction foreign individuals and companies operating in or providing services to the covered sectors. Secondary consequences for non-US banks are also explicit: foreign financial institutions that facilitate significant transactions for designated parties risk losing access to US correspondent accounts.

The UAE-Based Broker at the Centre of the Case

OFAC's accompanying designations named Ivan Obukhov, described as a UAE-based Ukrainian broker, and his UAE-registered company Foscom FZE. The agency alleged that since 2023 Obukhov processed more than $100 million in crypto payments to facilitate Iranian oil sales on behalf of the Islamic Revolutionary Guard Corps' Quds Force. Both Obukhov and Foscom FZE are now designated, meaning any US-linked property they hold must be blocked and US persons are prohibited from transacting with them.

The UAE angle matters for firms operating in the Gulf. Dubai and Abu Dhabi have become significant hubs for licensed virtual asset activity, and the presence of a designated entity registered within a UAE free zone is a reminder that regulatory licensing in the UAE does not insulate a counterparty from US sanctions exposure.

Context: A Coordinated Escalation, Not an Isolated Move

The August determination did not emerge in isolation. Treasury Secretary Scott Bessent had publicly stated, shortly before the action, that the US had seized cryptocurrency from Iranian exchanges and wallets, signalling that enforcement was accelerating. The June 2026 action against Nobitex followed. On 7 August 2026, OFAC added further parties alleged to have facilitated a combined $5 million in digital assets connected to Iran. The 25 August sectoral determination is therefore the capstone of a structured escalation, moving from named actors to sector-wide liability.

The Treasury's stated rationale is that Iran has made crypto a "tool of choice for sanctions evasion," with usage linked to the IRGC and government insiders. Whether or not the sums involved are large relative to global crypto volumes, the enforcement signal is clear: the US intends to treat crypto-denominated sanctions evasion with the same seriousness as fiat-based evasion.

Accounting and Compliance Implications for Firms

Counterparty Screening Must Now Cover Sector Participation

The shift from named-entity sanctions to sectoral sanctions changes the compliance calculus. Under a named-entity regime, a firm's screening obligation is primarily to check whether a counterparty appears on OFAC's Specially Designated Nationals list. Under a sectoral determination, firms also need to assess whether a counterparty operates in, or provides material support to, the covered sector, even if that party is not yet individually listed.

For accounting firms and CFOs managing digital asset treasury functions, this means the due diligence questionnaire for any crypto-facing counterparty, exchange, OTC desk, payment processor, or custodian needs an explicit question about Iranian nexus: clients served, jurisdictions of operation, and the geographic origin of funds routed through the platform. Firms should also document that assessment, because in a secondary sanctions dispute, evidence of good-faith inquiry matters.

The UAE Free Zone Dimension

Foscom FZE's registration in a UAE free zone is a data point that compliance teams operating in or around the Gulf should absorb carefully. The Virtual Assets Regulatory Authority (VARA) in Dubai has been actively licensing virtual asset service providers, and the SCA and VARA have created a unified UAE VASP register. Licensing under VARA does not, however, screen out US sanctions exposure. A VARA-licensed firm that onboards a client operating in Iran's digital asset sector could itself face designation. The lesson is that VARA compliance and OFAC compliance are parallel obligations, not substitutes for each other.

This is particularly relevant for accounting firms advising UAE-based VASPs. Any client that processed crypto flows involving Iranian oil revenues, IRGC-connected parties, or Obukhov's network faces potential blocking of US-linked assets and, if a foreign bank, potential loss of US correspondent access. Firms should review whether any client falls within that exposure perimeter, and document the review.

Balance Sheet and Booking Considerations

When OFAC designates a counterparty, any assets held with or owed by that party become "blocked property" for US persons. For a firm using crypto bookkeeping software or digital asset accounting software to manage treasury positions, the practical question is whether existing receivables or custodied balances are now frozen. Firms need a clear workflow: identify the exposure, apply a blocking entry in the ledger, notify legal and compliance, and retain records. Blocked property cannot simply be written off; it must be reported to OFAC and held separately until a licence is granted or the designation is lifted.

For audit teams, the existence of a sectoral determination rather than a named-entity list creates a higher standard of evidence around Iran-nexus testing. The question is no longer only "is this address on the SDN list?" It is also "does the economic substance of this transaction suggest participation in Iran's digital asset sector?" That requires on-chain analytics and geographic attribution, not just a name-screen.

What Good-Faith Compliance Looks Like Right Now

OFAC guidance consistently emphasises that the strength of a firm's compliance programme is a mitigating factor in enforcement decisions. Given the scale and explicitness of this determination, the baseline expectation for any firm with crypto exposure has moved. The steps that matter are practical and sequenced.

First, run a fresh sanctions screen across all active digital asset counterparties against the latest SDN additions, including Obukhov and Foscom FZE. Second, review any counterparties registered or operating in jurisdictions with known Iran-nexus risk, the UAE being a relevant geography given the facts of this case. Third, update your transaction monitoring parameters to flag volumes or patterns consistent with oil-linked crypto payments. Fourth, confirm that your crypto accounting software or digital asset accounting software has a mechanism to flag and segregate blocked-property entries. Fifth, brief senior leadership: the Treasury's explicit linkage of crypto to IRGC activity means that any subsequent enforcement action will attract scrutiny of what a firm knew and when.

For clients who need to understand how continuous monitoring differs from one-time screening, our piece on how continuous monitoring closes the post-screening risk gap in crypto AML sets out the framework in detail. The earlier analysis of OFAC's earlier sanctions on ISKP-linked crypto addresses also provides useful context on how OFAC structures terrorist-financing designations in the crypto space.

Secondary Sanctions Risk for Non-US Firms

A point that often gets underweighted in non-US jurisdictions: the secondary sanctions dimension of this determination is real. Foreign banks and financial institutions, including those in the EU, UAE, and Asia, that facilitate "significant transactions" for designated parties risk being cut off from US correspondent banking. In practical terms, that means losing the ability to clear US dollar transactions, which remains existential for most international financial institutions.

For accounting firms advising banks or fintechs outside the US that handle crypto flows: the risk is not hypothetical. The Treasury has used secondary sanctions in this manner before, and the explicit language in the August 2026 determination repeats that threat. Any institution that provides custody, payment processing, or exchange services to a party operating in Iran's digital asset sector now carries that secondary risk, regardless of where it is incorporated.

US Sanctions Iran's Entire Crypto Sector Over $100M in Oil Payments

Frequently Asked Questions

Does the sectoral determination mean all crypto transactions involving Iran are now automatically blocked?

Not automatically, but practically the bar is very high. Any person or entity determined to operate in Iran's digital asset sector becomes subject to sanctions under Executive Order 13902. US persons are prohibited from transacting with them, and their US-linked property must be blocked. Non-US firms face secondary sanctions risk if they facilitate significant transactions for designated parties. The determination gives OFAC authority to act broadly; it does not require individual transactions to be pre-identified before a designation is issued.

Foscom FZE is registered in the UAE. Does that create risk for other UAE-registered crypto firms?

Not automatically, but it is a material compliance signal. A UAE registration, including a VARA licence, does not insulate a firm from US sanctions exposure. Firms operating in the UAE should confirm that their counterparty screening covers US sanctions lists and that their onboarding process identifies any Iran-nexus in a prospective client's business model.

What does "blocking" mean in practice for accounting teams?

When OFAC designates a party, any US person holding assets with or owed by that party must freeze those assets immediately, report the blocked property to OFAC, and hold it separately. The assets cannot be written off the balance sheet as a loss without further OFAC authorisation. Crypto accounting software should have a workflow to flag, segregate, and report blocked positions. If your current system lacks this, that is a gap to address now.

Does this determination affect firms that have never transacted with Iran directly?

Yes, indirectly. A firm that processes transactions on behalf of a counterparty that itself operates in Iran's digital asset sector could be facilitating a sanctions violation, even without direct Iranian contact. The due diligence obligation extends to understanding what your counterparties do and who they serve. That is why counterparty onboarding and periodic re-screening matter, not just initial name-checks.

How does this interact with existing AML obligations under FinCEN rules?

They are separate but reinforcing. FinCEN's Bank Secrecy Act obligations require suspicious activity reporting and transaction monitoring. OFAC's sanctions obligations require blocking and non-facilitation. A transaction that triggers an AML flag, for example a large crypto payment with no clear commercial purpose routed through a high-risk geography, may also warrant a sanctions review. Compliance frameworks should treat both as live simultaneously, not as sequential steps.

Source: Cointelegraph

USAEGLOBALGeneralEnforcementAML/KYC & Licensing

Related articles

AML/KYC & Licensing
AI Governance in Compliance: The Accountability and Control Gap Regulators Are Already Watching
AML/KYC & Licensing
Dubai VARA Rolls Out Digital Asset Framework Including Privacy Coin Ban
AML/KYC & Licensing
Three Lines of Defense: The Governance Model Regulated Crypto Firms Already Need
AML/KYC & Licensing
OFAC Designates Iran's Digital Assets Sector in Historic Sanctions Move