OFAC red flags
Cross-Chain Sanctions Evasion: The Red Flag AI Agents Miss
An address can be clean on Ethereum and sanctioned on Tron. Agents that screen only the source chain miss the most common modern evasion pattern: chain-hopping. Here is why it triggers OFAC scrutiny and how to close the gap.
| Red flag | Why it triggers OFAC scrutiny | Risk level |
|---|---|---|
| Rapid ETH → BSC → TRON movement | Funds that cross three chains in minutes match known evasion playbooks. Banking partners and analytics vendors flag the pattern automatically, even when no individual address is listed. | High |
| Agent screens source chain only | If your agent checks the Ethereum address but pays to a bridge that exits on Tron, you have screened the wrong identifier. The destination-chain address is what carries liability. | Critical |
| Bridging to a chain with thinner screening coverage | Some chains have fewer sanctioned addresses listed simply because Treasury has published fewer designations there. That is a coverage gap, not safety. | Medium |
The control: every red flag above is caught by pre-transaction OFAC screening.
SanctionsAI checks the wallet, name, or jurisdiction against the live SDN list in under 100ms,
before the payment is signed. There is no pattern so clever that it bypasses an address check.
What to do if you see one of these
- Stop the transaction. Do not let the agent retry around the screen.
- Log the event with timestamp, subject, and SDN list version (the audit trail is your defense).
- If a payment already executed, preserve evidence and assess voluntary self-disclosure — it can reduce a penalty by up to 50%.
- Review the agent's control path: was the screen on the actual execution path, or only on the happy path?
Block every red flag before the payment signs
Pre-transaction OFAC screening in under 100ms. Free tier: 5 checks/day, no signup.
Screen a wallet free → See pricing