US sanctions two crypto exchanges over Iran-linked money flows

Dubai’s virtual-asset regulator had already fined Shelbit General Trading and ordered it to stop unlicensed activity when the U.S. Treasury moved against the wider exchange network two weeks later. On August 7, the Treasury Department’s Office of Foreign Assets Control designated Shelbit, Aban Tether and associated people and companies under counterterrorism- and Iran-related authorities.

The two-step regulatory record matters. Dubai’s regulator focused on licensing, customer checks and unauthorized marketing; OFAC focused on sanctioned counterparties, corporate control and wallet flows. Read together, the actions show how local compliance failures and cross-border sanctions exposure can surface around the same exchange network. They do not establish that Dubai’s findings caused the transactions described by Treasury, and an OFAC designation is an administrative action rather than a criminal conviction.

What OFAC actually designated

The headline shorthand—two crypto exchanges—covers a larger set of legal entities. OFAC’s August 7 update to the Specially Designated Nationals list names Iran-based Aban Tether Exchange, SHPS Shelbit in Georgia, Shelbit General Trading in the United Arab Emirates and Shelbit Technologies in Poland. It also lists Crypto Home DMCC and NFT Home DMCC in the UAE, along with Siavash Kayvanpour.

That distinction matters for anyone screening a counterparty. A brand name may be only the visible door to a network of companies, managers and wallet addresses. Compliance teams cannot stop at the website in front of the customer. They need to reconcile the trading name with the contracting entity, ownership records, payment accounts and blockchain addresses.

Treasury said Kayvanpour operated a multinational company network supporting illicit digital-currency activity. OFAC designated him under Executive Order 13224 for materially assisting or supporting Iran’s IRGC and Nobitex, both already blocked under that authority. It separately designated Aban Tether under Executive Order 13902 for operating in Iran’s financial sector.

Those are the government’s stated grounds. TECHi has not independently traced the wallets in the designation, and the action does not amount to a court finding against the named parties. That boundary is especially important in crypto reporting, where a wallet can be observable on a public ledger while the attribution of that wallet to a person or organization still depends on evidence readers may not be able to inspect.

The money-flow figures should not be added together

Treasury presented several figures for Shelbit, each tied to a different direction or set of actors. It said addresses belonging to the IRGC sent more than $1 million in digital assets to Shelbit addresses. It also said more than $2 million moved from Shelbit addresses to IRGC addresses. In a separate claim, Treasury said addresses belonging to or controlled by Kayvanpour sent more than $2 million to U.S.-designated Nobitex.

The release also alleges that tens of millions of dollars in digital assets from a Persian-language gambling network were laundered through Shelbit. Treasury said two Iranian influencers ran that network and that the sites retained access to Iran’s tightly regulated online payments systems.

These numbers describe different claims, and Treasury did not say they are mutually exclusive. Adding them into a single total would create a figure the agency never published. The safer reading preserves the direction, attributed owner and destination of each transfer.

Aban Tether sits on another branch of the action. Treasury said the Iran-based exchange processed millions of dollars in transactions involving Nobitex, Wallex, Bitpin and Ramzinex, all previously designated Iranian exchanges. The release does not say Aban Tether directly sent funds to the IRGC. Its exposure, as described by OFAC, comes from operating in Iran’s financial sector and dealing with sanctioned exchange counterparties.

That difference is more than legal fine print. It separates two risk patterns: Treasury-attributed IRGC flows on the Shelbit side, and exchange-to-exchange exposure on the Aban Tether side. Treating both as the same allegation would make the article louder and less accurate.

Dubai acted before Washington

On July 24, Dubai’s Virtual Assets Regulatory Authority said Shelbit General Trading had continued providing virtual-asset services in and from the emirate without a valid license. The VARA notice also said the company onboarded users without mandatory know-your-customer checks and marketed its services without authorization. VARA imposed a fine and directed the company to stop the unlicensed activity.

The regulator’s notice points back to a January 2, 2025 cease-and-desist order. That history turns the July action into more than a paperwork dispute: VARA said activity continued after an earlier intervention. It still does not prove that weak customer checks enabled any specific wallet flow later cited by OFAC.

Licensing is becoming a practical dividing line in crypto markets. Vietnam’s plan to pair domestic crypto exchange licences with restrictions on overseas trading shows a different policy model, but the same operational demand appears underneath it: regulators want to know which legal entity holds the customer relationship and which controls apply.

The TECHi inference is narrower than a causal claim. When one regulator documents unresolved licensing and KYC failures, counterparties have a reason to increase scrutiny. If another authority later identifies sanctioned wallets or entities around the same operation, the earlier compliance record becomes a risk signal. It is not proof of the later allegation; it is evidence that ordinary onboarding should no longer be treated as enough.

Why the designation reaches beyond two websites

The immediate U.S. effect is blocking, not a global seizure. Treasury said property and interests in property of designated people and entities that are in the United States, or held or controlled by U.S. persons, must be blocked and reported. Entities owned 50% or more, directly or indirectly, by one or more blocked persons are also blocked. U.S. persons are generally prohibited from transacting with them unless OFAC authorizes or exempts the activity.

The framework is broader for Iranian exchanges than a casual check of the public SDN list might suggest. In FAQ 1250, OFAC says Iranian digital-asset exchanges meet the definition of Iranian financial institutions and are blocked under Executive Order 13599 and the Iranian Transactions and Sanctions Regulations, even when an exchange has not been individually named on the SDN list.

OFAC’s updated FAQ 1257 makes the non-U.S. risk more explicit. It names Aban Tether and warns that foreign financial institutions and other non-U.S. persons may face sanctions exposure for certain dealings with exchanges designated under Executive Order 13902. “May face” is the operative phrase. The guidance describes possible secondary-sanctions risk, not automatic liability for every customer who ever used a platform.

Sanctions can also move in the opposite direction. When restrictions are lifted, an exchange may reopen a market, as Binance did when it restored crypto services for Syrian users. That contrast shows why exchange access is not only a product decision. It follows changing legal permissions, screening obligations and the exchange’s appetite for compliance risk.

The compliance lesson is entity-and-wallet screening

Crypto businesses often present blockchain surveillance as the hard part. The Shelbit and Aban Tether action points to a messier task: joining wallet intelligence to corporate identity and regulatory status. A transaction-monitoring alert is less useful if the exchange does not know which company contracted with the customer, who controls it, or whether a differently named affiliate is already blocked.

Start with entity resolution. An exchange, bank or payment firm needs to map trade names to legal entities and beneficial owners, then test those records against sanctions lists and the 50% rule. That process must cover counterparties and service providers, not only retail customers.

Wallet analysis also has to preserve direction. The official Shelbit figures distinguish assets going to the exchange from assets leaving it. Screening tools should retain that direction, the time window and the confidence level of attribution. A dashboard that collapses every linked transfer into one risk total may look decisive while erasing the information an investigator needs.

Regulatory history belongs in the same monitoring stack. A licensing fine in one jurisdiction does not create a U.S. sanctions violation. It can, however, justify enhanced diligence before the problem reaches another regulator. VARA’s notice was public before OFAC’s action. Firms that treated it as a local administrative footnote missed a chance to reassess the relationship.

Crypto markets have also been used to express and hedge Iran-related geopolitical risk around the clock. This action is different. It is not about token prices or a weekend market reaction; it targets the infrastructure that moves funds and the counterparties permitted to touch it.

What the two actions say—and what they do not

VARA said Shelbit served Dubai without a valid license, skipped mandatory KYC and marketed without authorization. OFAC separately took an administrative sanctions action, attributing wallet flows and support relationships to named actors and adding people and companies to the SDN List under applicable blocking authorities. Neither action is a criminal judgment.

VARA’s notice was public before OFAC published wallet addresses and corporate links. Compliance teams could act on that chronology only if they monitor regulatory history across jurisdictions and connect it to the entities and addresses in their own systems.

The same precision applies to the published record. Treasury’s figures should remain attached to Treasury, the separate flows should remain separate, and Aban Tether’s exchange exposure should not be rewritten as a direct IRGC-funding allegation. That is how an enforcement story stays useful after the first headline passes.