OFAC Sanctions Shelbit and Aban Tether: What Accounting Firms and CFOs Must Do Now

The US Treasury's Office of Foreign Assets Control (OFAC) designated two digital asset exchanges, Shelbit and Aban Tether, on 7 August 2026, citing their roles in laundering cryptocurrency for Iran's Islamic Revolutionary Guard Corps (IRGC). The action also named Iranian national Siavash Kayvanpour and a cluster of wallets and companies tied to him. For any accounting firm, auditor, or CFO whose business touches digital assets, this designation carries immediate compliance obligations, not a future review item.

What OFAC Actually Announced

OFAC's notice identified Shelbit and Aban Tether as exchanges that the Iranian regime relies on to move funds, and it used strong language: the department said it will "hunt down and dismantle the illicit financial networks that keep the regime afloat," quoting Treasury Secretary Scott Bessent directly. The statement signals that further designations in this campaign are likely, not merely possible.

The Specific Financial Flows Alleged

The Treasury set out three concrete transaction threads in its notice:

• IRGC-controlled wallets sent more than $1 million in cryptocurrency to addresses associated with Shelbit.
• Shelbit itself facilitated the transfer of $2 million in crypto to IRGC-controlled wallets, making the exchange a two-way conduit in the alleged laundering chain.
• Wallets linked to Kayvanpour sent $2 million in digital assets to Nobitex, an Iranian exchange that OFAC had already added to the Specially Designated Nationals (SDN) List in June 2026.

Together, the alleged flows account for roughly $5 million in digital assets across these entities. The Nobitex connection is particularly significant for compliance teams: it shows OFAC tracing a multi-hop chain across previously and newly designated entities, which means screening only against the current SDN snapshot is no longer sufficient. Firms need the ability to trace transaction history through intermediary addresses.

How This Fits the Broader Iran Enforcement Campaign

This designation is not an isolated event. OFAC designated digital asset exchanges Zedcex and Zedxio in January 2026 and linked them to Iran in June. The agency also took action against Iranian Central Bank crypto wallets earlier this year, freezing stablecoins in that action. The pattern is consistent: OFAC is systematically working through Iran's crypto-denominated financial infrastructure, and the pace is accelerating. Firms that treated each previous action as a standalone event need to shift their framing: this is a rolling enforcement campaign, and each new designation expands the on-chain footprint of sanctioned addresses that must be screened. For further context on the earlier action, see OFAC's earlier action freezing Iranian Central Bank crypto wallets.

Sanctions Mechanics: Why Strict Liability Matters Here

US sanctions law operates on a strict liability standard for most civil violations. A US person, including a US-incorporated entity or a non-US firm with a US nexus, does not need to have known that a counterparty was on the SDN List to face a penalty. The violation occurs at the point of the prohibited transaction. This is why OFAC designations require action on the day of publication, not on the day of the next compliance cycle.

What Counts as a Prohibited Transaction

Under the Iranian Transactions and Sanctions Regulations (ITSR), US persons are broadly prohibited from dealing with the Government of Iran and entities it owns or controls, including the IRGC. The SDN designation of Shelbit and Aban Tether means that any of the following would constitute a prohibited transaction without a specific OFAC licence:

• Sending or receiving cryptocurrency to or from the designated wallet addresses.
• Processing a payment that passes through an intermediary address linked to these entities.
• Providing software, services, or technology to the designated exchanges or to Kayvanpour's associated companies.
• Holding funds on behalf of, or releasing funds to, any of the designated parties.

For accounting firms acting as service providers to crypto businesses, the last point is directly relevant. If a firm manages treasury functions or has signing authority over client wallets, it needs to confirm that none of those wallets have received funds traceable to the newly designated addresses.

Accounting and Audit Implications

The designation creates several discrete accounting and audit tasks that cannot be deferred.

Balance Sheet and Asset Classification

Any digital asset held by a client that can be traced, even indirectly, to a sanctioned address may need to be reclassified. Under US GAAP, assets subject to legal restrictions on use or transfer are generally not freely usable and must be disclosed accordingly. If a firm cannot demonstrate clean provenance for a digital asset holding, the asset's recoverability becomes a going-concern question in an audit context. The same logic applies to any receivable denominated in crypto where the counterparty's address history has not been screened.

Disclosure and Representation Letters

Audit representation letters typically require management to confirm that there are no undisclosed violations of laws and regulations. Given OFAC's strict liability standard, a firm that has not conducted an affirmative screen of its digital asset transaction history against the updated SDN List cannot make that representation confidently. Auditors should be asking clients for evidence of that screen, not assuming it has been done.

The Role of Digital Asset Accounting Software

Manual screening of on-chain transaction histories is not realistic at scale. Robust crypto accounting software with integrated sanctions-screening capabilities, or a clear workflow connecting the accounting ledger to an on-chain analytics tool, is now a practical necessity rather than a differentiator. Each time OFAC publishes a new designation, the wallet addresses in that notice need to flow into the screening layer without manual intervention. Firms that rely on periodic CSV exports and manual lookups are carrying operational risk that regulators will not treat sympathetically. The same principle applies to digital asset accounting software used for producing financial statements: if the underlying transaction data has not been screened, the statements themselves carry unquantified sanctions exposure.

This operational challenge mirrors issues identified in other recent enforcement actions. The workflow questions raised by how the OFAC Hamas facilitator designations affected TRON address screening are directly applicable here, particularly for firms with exposure to TRON-based stablecoin flows, given Aban Tether's name and apparent focus.

AML Programme Review: Specific Steps for Compliance Teams

Beyond the immediate screening requirement, this designation should prompt a structured review of AML programme adequacy. The following actions are warranted now:

Counterparty and Transaction History Screening

Pull the wallet addresses published in OFAC's 7 August notice and run them against your full transaction history, not just open positions. OFAC has assessed penalties in past cases based on historical transactions that predated a firm's awareness of a designation, so look back as well as forward. Document the date, scope, and outcome of the screen.

Correspondent and Nested Account Review

For accounting firms servicing crypto exchanges or custody providers, review whether any client operates nested accounts that could route through Iranian-linked liquidity. The Nobitex connection in this case shows how funds can move through multiple hops before reaching a US-nexus entity. A surface-level counterparty screen is not enough if nested relationships are in scope.

Escalation and Reporting Protocols

If screening identifies a potential match or historical exposure, the firm needs a clear escalation path to legal counsel and, if warranted, a voluntary self-disclosure to OFAC. Voluntary disclosure is a significant mitigating factor in OFAC's penalty framework. Document every step of the decision-making process, including decisions not to escalate and the reasoning behind them.

Policy and Training Updates

AML policies should reference the current state of the Iran sanctions programme, not a version drafted before the 2026 enforcement campaign began. If the policy still treats Iran exposure as a low-frequency edge case, it needs updating. Training for staff who handle crypto transactions or client onboarding should be refreshed to reflect the expanded SDN footprint.

What to Expect Next

Treasury Secretary Bessent's statement that the government will "continue to increase the economic pressure" is not diplomatic boilerplate in this context. The progression from Zedcex and Zedxio in January, to the Nobitex re-linking in June, to the Shelbit and Aban Tether designations in August shows a methodical campaign that is building toward a more comprehensive blockade of Iran's crypto-denominated financial system. Firms should assume further designations in this series and build that assumption into their compliance planning cadence, rather than treating each action as a discrete event requiring a one-off response.

Frequently Asked Questions

Does this designation affect non-US firms?

It can. Secondary sanctions risk applies to non-US persons who engage in significant transactions with designated entities. While the primary obligation falls on US persons, non-US firms with any US-dollar clearing, US investor base, or US-incorporated subsidiary should take legal advice on their exposure before concluding they are outside the scope of these designations.

What should a CFO do if historical transactions show exposure to these addresses?

Stop any ongoing activity immediately, preserve all records related to the transactions, and seek legal counsel with OFAC sanctions expertise before taking any further action. If the exposure is material, voluntary self-disclosure to OFAC should be evaluated quickly, as it is a significant mitigating factor in the penalty calculation.

Are stablecoin transactions at higher risk given the name "Aban Tether"?

OFAC has not specified which assets Aban Tether handled, but the name suggests a focus on USDT or similar dollar-pegged assets. Given that stablecoins are the dominant medium for sanctions evasion in recent OFAC enforcement actions, firms with high stablecoin transaction volumes should treat this designation as a heightened screening trigger for those flows specifically.

How quickly must screening be completed after a new OFAC designation?

OFAC expects compliance to be effective on the date of designation. There is no grace period built into the regulatory framework. In practice, firms should aim to run a screen and document the outcome on the day the notice is published, or as close to that as their operational capacity allows.

Does existing crypto bookkeeping software automatically update for new OFAC designations?

It depends entirely on the specific tool and its integration architecture. Firms should confirm with their digital asset accounting software provider whether SDN List updates are applied automatically and how frequently. If the answer is periodic batch updates rather than real-time or daily feeds, that gap needs to be addressed with a supplementary manual screen on designation dates.

Source: Cointelegraph