A7A5: Inside the $110 Billion Stablecoin Sanctions Couldn't Stop

In October 2025, the EU did something it had never done before: it placed an explicit transaction ban on a specific cryptocurrency. The asset was A7A5, a ruble-pegged stablecoin barely nine months old at the time. Seven months and two more sanctions packages later, blockchain analytics firm CertiK put cumulative on-chain volume for A7A5 at over $110 billion, with the token holding roughly 43% of the entire non-dollar stablecoin market.

Holder counts didn't dip after the EU designation. They didn't dip after the UK followed with its own package in May 2026 either. According to CertiK's tracking, the number of wallets holding A7A5 rose steadily from around 13,000 in February 2025 to about 29,000 by May 2026 — a climb with no visible interruption at any of the sanctions events along the way.

For compliance teams at CASPs and EMIs, that growth curve is the real story here. It's a live, well-documented case of what happens when a sanctions designation meets an asset built specifically to route around designations. It's worth understanding in detail, because the same structural gaps it exploits apply well beyond this one token.

What A7A5 actually is

A7A5 launched in January 2025, issued through Old Vector LLC, a company registered in Kyrgyzstan. The token was created by Moscow-based A7 LLC, a cross-border payment operator jointly owned by Moldovan businessman Ilan Shor (already under UK sanctions at the time) and Promsvyazbank, a Russian bank with defense-sector ties that is itself sanctioned by the UK and EU. It runs on both Ethereum and TRON, and is backed, according to its issuer, by ruble deposits held at Promsvyazbank.

The design brief was straightforward: give Russian counterparties and their trading partners a settlement instrument that doesn't depend on the US dollar rails where OFAC has the most leverage, and that isn't controlled by an issuer likely to freeze tokens on request — a pointed contrast with Tether, which has increasingly cooperated with US law enforcement freeze requests. A7A5's own executives have been candid about this positioning, describing it as convenient settlement infrastructure for parties that need to keep trading with Russia regardless of what happens to the sanctions list.

Why designation alone didn't move the needle

A direct sanctions listing works well against a target that needs to touch regulated, dollar-denominated infrastructure — a bank account, a major exchange with US exposure, a correspondent banking relationship. A7A5 was built to avoid exactly that dependency, which is what makes it a useful stress test for list-based screening generally:

It doesn't need centralized exchange listings. HTX and other major exchanges publicly rejected A7A5 listing applications, citing secondary sanctions exposure. According to its own executives, this pushed the token's business model further toward DeFi infrastructure rather than away from usability — trading migrated to smaller, Russia-facing venues and decentralized rails instead.

It's cross-chain by design. Running on both Ethereum and TRON means a screening program that only watches one chain, or that treats each chain as an isolated silo, misses the activity that moves between them. This is precisely the bridge-hopping pattern that single-chain screeners are structurally blind to.

The designation targets lag the network. The EU's October 2025 package named the token itself. The EU's 20th package, effective May 2026, expanded to a category of Russian crypto providers and named specific Kyrgyz intermediaries like TengriCoin. The UK's May 2026 package — the first time it applied Regulation 17A of its Russia sanctions framework to cryptoasset exchanges — designated 18 entities and individuals, including HTX, EXMO Exchange, Rapira Group, and Bitpapa. Each package closes specific named doors. The network keeps opening new ones faster than they can be individually listed.

Primary trading venues can disappear and reappear. Grinex, previously the main venue for A7A5 trading, suspended operations in April 2026 following what it described as a cyberattack. Trading activity didn't stop — it redistributed to other platforms. A screening program keyed to specific known venues has to keep re-mapping the network as it reorganizes.

The part that should worry EU and UK compliance teams specifically

A7 has reportedly been opening offices in Nigeria and Zimbabwe, with Togo mentioned as a possible next step, while Promsvyazbank leadership has made visits to Madagascar. None of these jurisdictions have yet been the subject of formal OFAC, HM Treasury, or EU engagement on A7A5-related exposure specifically.

That gap matters for a very concrete reason: any EU or UK institution with correspondent banking relationships, EMI partnerships, or CASP clients touching those markets now carries a secondary sanctions exposure that isn't yet reflected in any published list. This is exactly the kind of risk that a static, list-only screening program is structurally unable to catch — because by definition, there's no entry to match against yet. It only surfaces through behavioral analysis: transaction patterns, counterparty relationships, and geographic risk flags that go beyond "is this exact address or entity on a list today."

What this means for CASP screening programs

A7A5 is an extreme, well-funded example, but the underlying lesson applies to ordinary transaction screening at any CASP or EMI operating under MiCA:

Address and entity matching catches the network's mistakes, not its design. A7A5-adjacent wallets that haven't been individually named will keep passing direct-match checks. The useful signal is exposure — has a wallet interacted with addresses, contracts, or trading venues connected to a sanctioned network — not just whether it appears on a list today.
Cross-chain visibility isn't optional for ruble- or non-dollar-denominated assets. Any screening program that only checks one chain per transaction is missing exactly the kind of bridge activity A7A5's TRON/Ethereum structure relies on.
Sanctions packages should be read for pattern, not just for the new names. Each EU and UK package against the A7 network has targeted a slightly different layer — the token, then category-level providers, then specific exchanges. Compliance programs that only update their block-lists after each package, without adjusting the underlying risk logic, will always be one step behind the next reorganization.
Geographic expansion is a leading indicator. Watching where a sanctioned network is opening new relationships — even before formal designations follow — is part of a defensible risk-based approach under MiCA's AML expectations.

How AML Radar covers this

The AML Radar Wallet Screener checks every address against OFAC, EU, and UK lists, and separately flags cross-chain bridge activity and mixer exposure — the two mechanisms that let networks like A7A5 keep operating around static designations. The Protocol Risk Dashboard tracks centralization and governance risk for the DeFi infrastructure this kind of trading activity increasingly relies on, and the Incident Monitor surfaces new sanctions package activity as it's published, so a designation against a new intermediary doesn't sit undetected in your screening logic for weeks.

Every check — direct match, indirect exposure, cross-chain flag — is logged to the MLRO Audit Trail with a timestamp, so if a supervisor asks why a transaction connected to this kind of network wasn't caught by a name-only check, the answer and the evidence are already on file.

Conclusion

A7A5 is not a one-off curiosity. It's a working demonstration of what a sanctions-evasion network looks like when it's built with screening gaps in mind from day one: cross-chain by design, distributed across venues that can reconstitute quickly, and expanding into jurisdictions ahead of formal designation. Static, list-only screening will keep catching the names on the list — and keep missing the network built to operate around them.

Try the AML Radar Wallet Screener — cross-chain bridge and mixer exposure detection included, free to start.

This article is for informational purposes only and does not constitute legal advice. Always consult a qualified compliance professional for guidance specific to your jurisdiction and business.