OFAC Sanctions Shelbit and Aban Tether: What Accounting Firms and CFOs Must Do Now
On Friday, 7 August 2026, the US Treasury's Office of Foreign Assets Control (OFAC) designated two cryptocurrency exchanges, Shelbit and Aban Tether, along with Shelbit's operator Siavash Kayvanpour and several related businesses. The designations target what OFAC described as digital asset exchanges that the Iranian regime relies on to launder billions of dollars, maintain covert access to international financial systems, and support the Islamic Revolutionary Guard Corps (IRGC) and other terrorist groups. For accounting firms, auditors, and CFOs who handle digital asset portfolios, the action creates immediate compliance obligations that require attention now, not at year-end. Firms that use robust crypto accounting software with integrated sanctions screening will be best placed to act fast.
What OFAC Designated and Why
Shelbit: a front exchange for Iranian regime funds
Shelbit presented itself as a conventional crypto exchange, with corporate ties to Poland and Georgia and a LinkedIn profile claiming a Tbilisi headquarters. In practice, blockchain analytics show it operated from Dubai and ran between July 2024 and February 2026. During that window it processed billions of dollars worth of cryptoassets, with the heaviest volume concentrated between July 2025 and January 2026.
Despite running large transaction volumes, Shelbit built no meaningful user community to match them, a pattern consistent with a platform designed to move institutional-scale funds rather than serve retail customers. The exchange went offline around February 2026 with no formal closure announcement; its social media accounts simply went dormant. No public complaints from retail users unable to withdraw funds were identified, which itself suggests the customer base was not retail.
Central Bank of Iran and IRGC wallet interactions
Earlier in 2026, blockchain researchers documented the acquisition of at least $507 million worth of USDT linked to the Central Bank of Iran. Before June 2025, those stablecoins were routed predominantly to Nobitex, Iran's largest crypto exchange. That routing changed sharply after a cyberattack attributed to the pro-Israel group Gonjeshke Darande in mid-2025. Post-June 2025, the funds were moved in a more layered manner, bridged across multiple chains, with approximately $71.8 million of those particular funds eventually deposited into Shelbit.
OFAC's own press release confirmed that IRGC digital currency addresses sent the equivalent of over $1 million in digital assets to Shelbit, and that more than $2 million moved in the opposite direction, from Shelbit addresses to IRGC addresses. On-chain analysis identified roughly $1.68 million flowing from IRGC-attributed addresses into Shelbit deposit addresses, and $2.3 million withdrawn from Shelbit directly to IRGC-attributed addresses.
Alireza Derakhshan and IRGC front company activity
OFAC's action also named Alireza Derakhshan, an Iranian national previously sanctioned by OFAC, who is alleged to have used a network of front companies to transfer cryptoassets in support of IRGC operations. On-chain records show a Tron address that OFAC associated with Derakhshan depositing into Shelbit in September 2025, illustrating how the exchange served as a convergence point for regime-linked fund flows.
Aban Tether: Iran-based exchange without published addresses
The second designation covers Aban Tether, an Iran-based exchange. OFAC's action on Aban Tether did not include specific blockchain addresses in the published designation. However, blockchain analytics providers had already labelled addresses connected to Aban Tether prior to the designation, meaning those addresses can now be recategorised as sanctioned and screened in compliance workflows even without addresses appearing in the official SDN list. This distinction matters for firms: the absence of OFAC-published wallet addresses does not eliminate exposure risk if indirect connections exist.
Compliance Obligations That Activate Immediately
US persons and SDN list exposure
Under the International Emergency Economic Powers Act and relevant Iran-related Executive Orders, US persons are prohibited from engaging in transactions with sanctioned parties. Crucially, the prohibition extends to indirect dealings, including transactions where a sanctioned entity is in the chain of fund flows, even if your client was not the direct counterparty to Shelbit or Aban Tether. Firms advising clients with any USDT or Tron-based stablecoin exposure from mid-2024 onward should treat this as a priority screening event.
Non-US firms are not automatically subject to US primary sanctions but can face secondary-sanctions risk if they facilitate transactions that benefit sanctioned Iranian parties. Given the volume of funds allegedly processed, global AML obligations under FATF recommendations also come into play for virtually all regulated entities.
Transaction screening: retroactive and prospective
The designated addresses for Shelbit were published by OFAC. Firms need to run those addresses through their existing transaction-history data immediately. Any historical transaction that touched a Shelbit wallet, directly or through one hop, warrants escalation to the compliance function and, depending on the dollar value and jurisdiction, possible voluntary self-disclosure to OFAC. Aban Tether's lack of officially published wallet addresses requires a different approach: rely on analytics databases that had already labelled those addresses, and document that screening methodology carefully.
This is exactly the scenario where the quality of a firm's digital asset accounting software becomes a compliance variable, not just an efficiency one. Systems that integrate real-time sanctions lists and can trace multi-hop wallet paths are no longer optional infrastructure.
SARs and STRs: timing and threshold decisions
For US-based firms and their clients subject to Bank Secrecy Act obligations, any identified transaction touching a sanctioned address triggers a Suspicious Activity Report filing requirement under FinCEN regulations, irrespective of dollar amount. The standard 30-calendar-day filing window applies, with a 60-day extension if the subject cannot be identified. Firms should not wait for a definitive determination of direct versus indirect exposure before beginning the documentation process.
Equivalent obligations apply across other jurisdictions: the UK's Suspicious Activity Report regime under the Proceeds of Crime Act, the EU's suspicious transaction reporting requirements under AMLD, and comparable frameworks in the Gulf, Asia-Pacific, and beyond.
Accounting and Financial Reporting Implications
Asset write-down and impairment considerations
Any digital assets held at, or traceable through, Shelbit or Aban Tether are now of uncertain recoverability for sanctions-compliance reasons, regardless of market price. Under both US GAAP (ASC 350-60 for crypto assets) and IFRS (IAS 38 or fair value models under IFRS 9 for financial instruments), an impairment or recoverability assessment is required when events or circumstances indicate that the carrying value may not be recoverable or that a liability has arisen. A sanctions designation by OFAC constitutes exactly that kind of triggering event.
CFOs should discuss with their auditors whether any positions need to be written down, disclosed, or reclassified in interim or annual financial statements. The conversation should happen before the next reporting close, not after.
Disclosure obligations under SEC rules
Publicly listed companies in the US with material digital asset holdings or exposure to sanctioned counterparties have disclosure obligations under SEC rules. If the exposure is material, that determination needs to be made and documented now, because the designation date is 7 August 2026 and any subsequent reporting period will require consideration of whether the event was known or should have been known by management.
Stablecoin-specific risks
The Shelbit and Aban Tether flows were predominantly in USDT, a dollar-denominated stablecoin issued on Tron and other chains. Firms that hold USDT balances or process USDT payments need to review whether any of those balances passed through addresses now on the SDN list. Stablecoins are not exempt from sanctions rules, and the on-chain traceability of USDT makes the evidentiary trail relatively clear. That same traceability works in a firm's favour during a voluntary self-disclosure, provided the firm can demonstrate it screened proactively.
For background on the broader accounting treatment of stablecoins in client portfolios, our earlier analysis of OFAC's Shelbit and Aban Tether designation: initial firm briefing covers the first-response framework, and the pattern of enforcement mirrors what we covered when examining AUSTRAC's suspension of Cryptolink Bitcoin ATMs over reporting failures, where indirect compliance gaps drove enforcement outcomes.
Practical Steps for Accounting Firms and CFOs
Immediate actions: within 72 hours
First, obtain the full list of OFAC-designated wallet addresses for Shelbit from the SDN list and run them against all client transaction histories. Second, engage your analytics provider to screen for Aban Tether addresses using their existing labels, and document the methodology. Third, flag any matches to the compliance function and, where applicable, to legal counsel for a self-disclosure assessment. Fourth, freeze any assets under your control that may be linked to the designated parties, as required by US sanctions law.
Short-term actions: within 30 days
Review client onboarding records for any entity that used Shelbit as a named exchange during 2024 to early 2026. Update your client risk ratings accordingly. Prepare or update SAR/STR filings where thresholds are met. Initiate impairment assessments for affected digital asset positions in financial statements. Communicate with auditors about the designation and its potential impact on the current reporting period.
Ongoing: policy and technology review
This designation underscores that crypto exchanges can operate at significant volumes while appearing superficially legitimate. Firms whose crypto bookkeeping software lacks multi-hop wallet tracing and live sanctions-list integration should treat this event as a prompt to reassess their technology stack. Manual screening processes will not scale to the volume and complexity of on-chain fund flows now characteristic of sanctions evasion cases.
Frequently Asked Questions
Does the Aban Tether designation apply if OFAC did not publish wallet addresses?
Yes. OFAC's SDN designation of Aban Tether is legally effective from the date of publication regardless of whether wallet addresses were included. US persons are prohibited from transacting with the entity. Analytics providers that had already labelled Aban Tether addresses allow firms to screen for exposure even where official addresses are absent; document that screening methodology carefully for your compliance file.
Are non-US firms exposed to these sanctions?
Non-US firms are not directly subject to US primary sanctions but face secondary-sanctions risk if they facilitate transactions that benefit the designated parties. All regulated firms globally also face AML obligations under FATF recommendations that require them to screen against major sanctions lists, including OFAC's SDN list, as part of transaction monitoring.
What if a client's USDT passed through Shelbit indirectly, via a bridge or intermediate wallet?
Indirect exposure can still trigger compliance obligations. US sanctions law prohibits transactions that involve a sanctioned party anywhere in the chain. The appropriate step is to document the full transaction path, assess the proximity to the sanctioned address, escalate to legal counsel, and determine whether voluntary self-disclosure to OFAC is warranted. Proactive disclosure is treated favourably by OFAC in penalty calculations.
How does the Shelbit designation affect the accounting treatment of USDT held by clients?
Any USDT that can be traced to Shelbit or Aban Tether addresses is subject to a recoverability and impairment assessment under the applicable accounting standard, whether ASC 350-60 under US GAAP or the relevant IFRS framework. The OFAC designation constitutes a triggering event for that assessment. CFOs should raise this with their auditors before the next reporting close.
What records should firms retain to demonstrate compliance?
Retain the date-stamped results of every sanctions screen run against the OFAC-published addresses, the methodology used to screen Aban Tether given the absence of official wallet addresses, any internal escalation records, SAR/STR filings and their timestamps, and any legal advice obtained. OFAC's enforcement guidelines treat documented, good-faith compliance programmes as significant mitigating factors in penalty assessments.
Source: US Treasury OFAC