OFAC Sanctioned Crypto Addresses by Chain
OFAC's sanctions list of Specially Designated Nationals (the SDN list), as published on October 28, 2026, holds 1,075 digital currency address fields on 109 entries, covering 1,058 distinct address strings. By OFAC's own currency label the leaders are XBT (bitcoin) with 534 fields, TRX with 266, ETH with 124 and USDT with 94. An exact match proves a string is listed. A miss does not make an address safe.
Reading OFAC's SDN.CSV file on its own gives a much smaller total: 523 matches, with XBT at 262, TRX at 92 and ETH at 91. That file cuts its remarks column at 1,000 characters, 36 rows reach the cut, and the rest of the text sits in a companion file, SDN_COMMENTS.CSV. Put back together, and checked against OFAC's SDN.XML and SDN_ADVANCED.XML, the data gives the 1,075 above. A count of XBT 262, TRX 92 and ETH 91 matches the SDN.CSV-only parse of this publication exactly.
Every count here comes from a script that parses the ID-type field of each SDN entry, and the parsing rule is stated below so anyone can repeat it. Only the SDN list is counted. OFAC's separate non-SDN consolidated list, published October 19, 2026, has 486 records and no digital currency address fields. The counts are of identifiers OFAC chose to publish. They are not counts of sanctioned wallets, and OFAC says its own address listings are "not likely to be exhaustive."
1,075 Fields on 109 Entries, by OFAC Currency Label
An address field is one identifier inside an SDN entry. In SDN.XML it is an id element whose idType begins with "Digital Currency Address - " and ends with a ticker, such as XBT or ETH; the idNumber is the address string. In the flat CSV files the same item appears inside the remarks text as "Digital Currency Address - ETH" followed by the string, with "alt." in front of the second and later fields of an entry. OFAC's FAQ 563 sets the format:
Digital currency addresses listed on the SDN List include their unique alphanumeric identifier (up to 256 characters) and identify the digital currency to which the address corresponds (e.g., Bitcoin (XBT), Ethereum (ETH), Litecoin (LTC), Neo (NEO), Dash (DASH), Ripple (XRP), Iota (MIOTA), Monero (XMR), and Petro (PTR)). Each digital currency address listed on the SDN list will have its own field: the structure will always begin with "Digital Currency Address", followed by a dash and the digital currency's symbol (e.g., "Digital Currency Address - XBT", "Digital Currency Address - ETH"). This information is followed by the unique alphanumeric identifier of the specific address.
Applying that rule to the October 28, 2026 file finds 20 distinct labels. The table lists all of them. "Distinct strings" counts each address once, with strings that start 0x lowercased before comparing. "Entries" counts the SDN entries that carry at least one field with that label. The last column describes the address format of the strings under each label, which matters for the next section.
| OFAC label | Fields | Distinct strings | Entries | Address formats under the label |
|---|---|---|---|---|
| XBT | 534 | 532 | 65 | Base58 starting 1 or 3 (387); bc1 (146); one string in Tron format (1) |
| TRX | 266 | 266 | 40 | Starts with T, 34 characters (266) |
| ETH | 124 | 123 | 48 | 0x plus 40 hex characters (124) |
| USDT | 94 | 94 | 20 | Starts with T (79); 0x (8); base58 starting 1 or 3 (7) |
| LTC | 14 | 13 | 10 | Base58 starting L or M (13); ltc1 (1) |
| XMR | 11 | 11 | 4 | 95-character Monero form (10); one other form (1) |
| BCH | 7 | 7 | 4 | CashAddr (6); base58 starting 1 or 3 (1) |
| DASH | 5 | 5 | 4 | Starts with X (5) |
| SOL | 4 | 4 | 3 | Base58, 32 to 44 characters (4) |
| ZEC | 4 | 4 | 4 | Starts with t1 (4) |
| DOGE | 2 | 2 | 1 | Starts with D (2) |
| USDC | 2 | 2 | 2 | 0x (2) |
| ARB | 1 | 1 | 1 | 0x (1) |
| BNB | 1 | 1 | 1 | Other form (1) |
| BSC | 1 | 1 | 1 | 0x (1) |
| BSV | 1 | 1 | 1 | Base58 starting 1 or 3 (1) |
| BTG | 1 | 1 | 1 | Base58, 32 to 44 characters (1) |
| ETC | 1 | 1 | 1 | 0x (1) |
| XRP | 1 | 1 | 1 | Base58, 32 to 44 characters (1) |
| XVG | 1 | 1 | 1 | Starts with D (1) |
| All labels | 1,075 | 1,058 | 109 | 17 fields repeat a string already counted |
Computed from OFAC's SDN.XML, Publish_Date October 28, 2026, downloaded November 3, 2026. The Entries column does not add to 109 because entries often carry several labels. Format classes are pattern checks on the string, not on-chain validation. The Distinct strings column adds to 1,071 rather than 1,058 because 10 strings are listed under more than one label and are counted once under each label they carry.
Bitcoin-labelled and Tron-labelled fields together make up 800 of the 1,075 (74.4%). XBT alone is 49.7%, TRX 24.7%, ETH 11.5% and USDT 8.7%. The four largest labels account for 1,018 fields (94.7%), and the other 16 labels share the remaining 57. Most of those 16 are single fields on single entries, so a count "by chain" past the first four labels is a list of individual cases rather than a distribution.
The label set is open-ended. FAQ 563 names Neo (NEO), Iota (MIOTA) and Petro (PTR) as examples, and none of the three appears in the October 28 file. XRP appears once. ARB and BSC sit on strings in the same 0x format as ETH, a first hint that a label and a blockchain are not the same thing.
The 523 Trap: What SDN.CSV Alone Leaves Out
OFAC publishes the SDN list in several formats. The legacy flat-file series is four linked CSV files: SDN.CSV for the entries, ADD.CSV for addresses, ALT.CSV for aliases and SDN_COMMENTS.CSV for text that did not fit. Digital currency addresses live in the remarks column of SDN.CSV, and that column stops at 1,000 characters. OFAC's tutorial on the legacy files says what happens past that point:
The SDN_COMMENTS.CSV (remarks field spill over) file contains additional remarks field data that exceeds the 1000-character limit of the remarks column in the SDN.CSV file. The SDN_COMMENTS file (and other files like it for OFAC's other sanctions lists) was created in August 2013. Users should be downloading this file as well or they risk missing identifiers that are typically stored in the remarks field.
The same tutorial states the general risk: "If users only download one of the files (for example SDN.CSV) they will be missing large amounts of list data and may be at greater risk of doing business with an SDN or other sanctioned entity."
In the October 28, 2026 download the longest remarks value in SDN.CSV is exactly 1,000 characters, and 36 rows reach that length. In 21 of those 36 entries the spill file holds at least one address field. Four ways of reading the same publication give two different answers:
| Method | What is parsed | Address fields |
|---|---|---|
| SDN.CSV only | Remarks column, pattern "Digital Currency Address - LABEL string" | 523 |
| SDN.CSV plus SDN_COMMENTS.CSV | Remarks with the spill text appended | 1,075 |
| SDN.XML | idType and idNumber of every id element | 1,075 |
| SDN_ADVANCED.XML | Features whose type is one of the 20 digital currency address types | 1,075 |
The three complete methods agree field for field: the CSV-plus-spill result and the SDN.XML result are identical as lists of label and string, and the advanced file matches by label. The CSV-only result of 523 is 48.7% of the true total, and it is worse than a plain undercount. Of the 523 matches, 13 are fragments cut off by the 1,000-character limit, such as an address string that stops partway or a label with nothing after it. They look like addresses and will never match anything. Only 510 are intact, which means a screening list built from SDN.CSV alone is missing 565 real fields (52.6%) and contains 13 strings that are not real addresses.
The loss is uneven because it falls on the entries with the longest remarks:
| OFAC label | Complete file | SDN.CSV only | SDN.CSV share |
|---|---|---|---|
| XBT | 534 | 262 | 49.1% |
| TRX | 266 | 92 | 34.6% |
| ETH | 124 | 91 | 73.4% |
| USDT | 94 | 43 | 45.7% |
| LTC | 14 | 8 | 57.1% |
| XMR | 11 | 6 | 54.5% |
| BCH | 7 | 2 | 28.6% |
| SOL | 4 | 2 | 50.0% |
| ZEC | 4 | 3 | 75.0% |
SDN.CSV-only figures are raw pattern matches, including the 13 cut-off fragments. Four labels in the complete file, ARB, BSC, BSV and XRP, do not appear in the CSV-only parse at all.
Among the four large labels, Tron fares worst: 92 of its 266 fields, about a third, are visible in the single file. ETH is the best preserved at 91 of 124, so an Ethereum-only check built on SDN.CSV can look reasonable and still miss 33 listed ETH fields.
A Currency Label Is Not a Chain
The label in the ID-type field names a digital currency, as FAQ 563 puts it, "the digital currency to which the address corresponds". It does not name a network. For some labels the two coincide. For others the file itself shows they do not, because the address format under a label varies. Grouping the same 1,075 fields by what the string looks like gives a different picture:
| Address format | Fields | Distinct strings | Labels carrying it |
|---|---|---|---|
| Base58 starting 1 or 3 | 396 | 390 | XBT 387, USDT 7, BCH 1, BSV 1 |
| Starts with T, 34 characters | 346 | 346 | TRX 266, USDT 79, XBT 1 |
| Bech32 starting bc1 | 146 | 146 | XBT 146 |
| 0x plus 40 hex characters | 137 | 127 | ETH 124, USDT 8, USDC 2, ARB 1, BSC 1, ETC 1 |
| All other formats | 50 | 49 | LTC, XMR, BCH, SOL, ZEC, DASH, DOGE, XVG, XRP, BTG, BNB |
Format classes are regular-expression checks on the string. A match shows the string looks like that kind of address; it does not show on which network the address has been used.
Three things follow. First, USDT is split three ways: 79 of its 94 fields are in the Tron format, 8 are in the 0x format and 7 look like legacy Bitcoin addresses. A count that treats "USDT" as one network would misstate every one of those groups. Second, a string in the 0x format is valid on every network that uses that address format, and the file attaches nothing to it but a label. The 137 fields in that format sit on 51 entries, and ETH, USDT, USDC, ARB, BSC and ETC are all labels over 0x strings. For the EVM family the honest unit is the address string, 127 of them, and not a per-chain tally. Third, the label can disagree with the format. One XBT-labelled field holds a string in Tron format; the file does not say why, and the count above keeps it under the label OFAC printed.
The practical rule for screening is to compare the string and ignore the label. The label is useful for reporting, and a hit on a string tells you which entry lists it. Screening only the strings that match the network you use is a mistake, because the file does not promise that the label matches the network.
Counting Rules and the Edge Cases That Move the Totals
The headline figures depend on a handful of choices. Each is stated here so the counts can be reproduced.
id element in SDN.XML whose idType starts with "Digital Currency Address - ". The label is the text after the dash. The address is the trimmed idNumber. No address in the file contains whitespace, and the longest is 95 characters, well under the 256 characters FAQ 563 allows.sdnEntry. The list holds 19,484 of them, and 109 (0.56%) carry at least one address field: 76 individuals and 33 entities.Repeats come in three kinds, and a screening script needs to handle all of them without double-counting or dropping entries:
The reason a table that sums labels overstates the number of addresses is visible in the label overlap. If you add 534 (XBT) and 94 (USDT) you count the four XBT-and-USDT strings twice. A label total answers "how many fields carry this label", and it is not a count of addresses.
Entries differ in how they use labels. Sixty entries use a single label, 20 use two, and 29 use three or more, with a maximum of eight labels on one entry. That is 49 multi-label entries, or 45% of the 109. The most common combinations are XBT alone (26 entries), TRX alone (16), USDT alone (10), ETH alone (8), and ETH with TRX (7).
Which total answers which question:
| Quantity | Count |
|---|---|
| Address fields published by OFAC | 1,075 |
| Distinct address strings | 1,058 |
| SDN entries carrying any address field | 109 |
| Distinct strings in the 0x format | 127 |
| Entries listing more than one currency label | 49 |
| Fields visible in SDN.CSV alone, intact | 510 |
Who the Addresses Belong To: Entries, Not Wallets
An address count is a count of identifiers OFAC published. It is not a count of sanctioned wallets and it is not a measure of how much illicit activity exists. FAQ 562 says so directly, and its wording is the reason to treat every count on this page as a floor:
OFAC may add digital currency addresses to the SDN List to alert the public of specific digital currency identifiers associated with a blocked person. OFAC's digital currency address listings are not likely to be exhaustive. Parties who identify digital currency identifiers or wallets that they believe are owned by, or otherwise associated with, an SDN and hold such property should take the necessary steps to block the relevant digital currency and file a report with OFAC that includes information about the wallet's or address's ownership, and any other relevant details.
The distribution across entries is lopsided. The median entry carries 4 fields, and 31 entries (28.4%) carry exactly one. At the other end, 22 entries carry ten or more, four carry 50 or more, and the five largest carry 134, 117, 53, 52 and 49 fields, which is 405 fields or 37.7% of the total. The two largest entries alone hold 251 fields (23.3%). A change to one large entry can move every total in this article by several percent, which is why counts taken a few weeks apart can differ without any contradiction.
The program tags on those entries show what kind of conduct the listings address, in OFAC's own categories. The tags come from the file's programList for each entry, and the categories come from OFAC's Program Tag Definitions page. An entry can carry several tags, so the rows overlap:
| OFAC category | Entries with at least one tag in the category | Tags seen |
|---|---|---|
| Cyber | 40 | CYBER2, CYBER3, CYBER4 |
| Terrorism | 24 | SDGT, FTO |
| Narcotics | 21 | ILLICIT-DRUGS-EO14059, SDNTK |
| North Korea | 15 | DPRK2, DPRK3, DPRK4 |
| Russia | 11 | RUSSIA-EO14024 |
| CAATSA | 2 | CAATSA - RUSSIA |
| Iran | 10 | IFSR, IRGC, HRIT-IR, IRAN, IRAN-EO13902 |
| Criminal Orgs | 9 | TCO |
| Elections | 6 | ELECTION-EO13848 |
| Non-Proliferation | 2 | NPWMD |
| Ukraine/Russia | 1 | UKRAINE-EO13661 |
Entries counted from the programList of each of the 109 entries; 21 distinct tags in all. Thirty entries carry tags from more than one category. Seventy-seven carry exactly one tag.
The table describes the list and supports no claim about which category produces the most illicit volume. Cyber tags lead by entry count, and the SDN list has no field for volume, losses or time of activity.
How Current Is "Current": the October 28 Publication
Three timestamps sit around the file. The Publish_Date field inside SDN.XML reads 10/28/2026, with a record count of 19,484, which matches the number of entries parsed. The download service stores the file under a folder and a "preview date" stamped October 27, 2026, and the file's Last-Modified header reads October 28, 2026, 14:03 GMT. The first of these is the one to cite, since it is the date OFAC puts in the data. It also fits the content: OFAC's Recent Actions notice dated October 28, 2026 added three entries with digital currency addresses, nine address fields in all, and all nine are in the file.
The most recent Recent Actions listings, checked on November 3, 2026, show a general license issued October 29 and no sanctions list update after October 28. The file downloaded that day was therefore the latest published list, and the counts here describe it as of November 3, 2026. The nine fields added by the October 28 notice are 0.84% of the total, which shows the scale of one ordinary update. A larger action can add or remove far more.
State the date whenever you quote a count. "1,075 fields on the SDN list published October 28, 2026" is a checkable claim; "OFAC lists 1,075 addresses" is not, because it will be wrong the next time OFAC changes the list. For history, OFAC's Sanctions List Service links an archive of changes to the SDN list and archived delta files by year, which are the places to look when you need the list as it stood on an earlier date.
Running the Lookup Yourself
There are two routes, and they answer the same question in different ways.
Route 1: OFAC's Sanctions List Search tool. FAQ 594 describes it:
Yes, it is possible to query for digital currency addresses using OFAC's Sanctions List Search tool. Users of the tool may search for digital currency addresses by inputting the hash value into the "ID #" field and then clicking "Search." The ID # field does not use fuzzy logic, so only exact matches will be returned when searching for digital currency addresses with the Sanctions List Search tool.
The steps are short.
sanctionssearch.ofac.treas.gov, paste the string into the "ID #" field, leave the name field empty and click Search.Two details from OFAC's other FAQs matter. FAQ 246 says that only the name field uses fuzzy logic and that the other fields use character matching. FAQ 253 says the ID field "uses exact character matching" and advises searching "both with and without any non-alphanumeric characters" to get the broadest results. Neither FAQ says how the tool treats upper and lower case, so the web tool is not the place to assume case-insensitivity. A name search is the wrong instrument for an address, and it can mislead on names as well. A text search of the October 28 file for "tornado" turns up a weak alias on an unrelated individual's record and an email domain inside one entry, and no entry whose primary name is Tornado Cash.
Route 2: the file. This route is better when you have more than a handful of addresses, and it returns the counts above as a check.
SDN.XML from the Sanctions List Service. Use the single XML file, or download all four legacy CSV files and join them. A script that reads SDN.CSV alone will report about half of the fields.id element, keep those whose idType begins with "Digital Currency Address - ". Store the label, the idNumber and the entry's uid.SDN.CSV was loaded.Publish_Date with every result, and re-run after each list update. OFAC's guidance notes that "you can sign up to receive email notifications whenever OFAC updates its SDN List."Two cautions apply to both routes. A hit means a string is identical to a listed identifier, and what to do next depends on who you are, where you are and what you hold. That is the point at which general information runs out and qualified advice begins. And the consolidated non-SDN list, which the web tool also searches, carried no address fields in its October 19, 2026 publication, so a clean ID # result there tells you nothing beyond the SDN list result.
The related guides on this site cover the checks that come before the lookup. Reading a blockchain transaction on an explorer shows where an address came from and where it sent funds, and bitcoin address types explains the legacy, SegWit and Taproot formats that appear in the XBT rows above. The travel rule guide covers the identity questions an exchange asks when you withdraw.
Why No Match Is Not a Clearance
The sanction attaches to a person, not to an address. FAQ 561 describes the role addresses play: OFAC "may include as identifiers on the SDN List specific digital currency addresses associated with blocked persons." An address entry is evidence of who a listed person is and what they use, in the same way a passport number or an email address in the same record is. The listed person is the subject of the blocking rules. FAQ 560 asks whether compliance obligations are the same regardless of whether a transaction is denominated in digital currency or fiat currency, and answers: "Yes, the obligations are the same. U.S. persons (and persons otherwise subject to OFAC jurisdiction) must ensure that they block the property and interests in property of persons named on OFAC's SDN List or any entity owned in the aggregate, directly or indirectly, 50 percent or more by one or more blocked persons, and that they do not engage in trade or other transactions with such persons."
That structure produces six reasons a clean lookup proves less than it appears to.
| Reason | What the OFAC text says | What a clean result leaves open |
|---|---|---|
| Listings are partial | FAQ 562: address listings "are not likely to be exhaustive" | Other addresses of a listed person may not be in the file |
| Wallets hold many addresses | FAQ 559: "A wallet holds the user's digital currency addresses" | The file matches strings, not wallets |
| Ownership is covered without a listing | Guidance: lists "do not separately list the names of all entities owned 50 percent or more by blocked persons" | An entity can be blocked without any address or name on the list |
| The list changes | Nine fields were added in one October 28 notice | A string clean today can be listed after the next update |
| Association can reach unlisted addresses | Guidance on shared wallets and past transactions | An unlisted address may still carry risk |
| Matching is exact | FAQ 594: only exact matches are returned | A typo, truncation or wrong copy returns nothing, silently |
The guidance document that OFAC published for the virtual currency industry on October 15, 2021 is the main source for the fifth row. It states that OFAC's inclusion of addresses "may assist the industry in identifying other virtual currency addresses that may be associated with blocked persons or otherwise pose sanctions risk, even if those other addresses are not explicitly listed on the SDN List," and continues: "For example, unlisted virtual currency addresses that share a wallet with a listed virtual currency address may pose sanctions risk because the sharing of a wallet may indicate an association with a blocked person. Similarly, virtual currency companies may consider conducting a historic lookback of transactional activity after OFAC lists a virtual currency address on the SDN List to identify connections to the listed address." The language is addressed to companies and uses "may" throughout; it describes risk indicators, and it does not say that every such address is blocked.
Strict liability is the other part of the picture for U.S. persons. The same guidance says: "OFAC may impose civil penalties for sanctions violations generally based on a strict liability legal standard. This means that, in many cases, a U.S. person may be held civilly liable for sanctions violations even without having knowledge or reason to know it was engaging in such a violation. As a general matter, however, OFAC takes into consideration the totality of facts and circumstances surrounding an apparent violation to determine the appropriate enforcement response." The paragraph goes on to name a risk-based compliance program and remedial measures as mitigating factors. It also says who is covered: "All U.S. persons are required to comply with OFAC regulations," including U.S. citizens and lawful permanent residents wherever located, all individuals and entities within the United States, and U.S.-organized entities, with others covered under particular programs.
A company and an individual ask different things of a lookup. For a company, the guidance treats list screening as one control among several, next to geolocation, customer information, transaction monitoring and blockchain analytics, and it says OFAC "does not require the virtual currency industry to use any particular in-house or third-party software." For an individual checking one address, a clean result answers only the narrow question it poses: whether that exact string is in that exact file on that date.
The wrong-copy risk in the last row is not hypothetical. The 13 cut-off fragments in the SDN.CSV parse are strings that look like addresses and fail to match anything. A truncated copy from a chat window, a screenshot read by eye or a pasted string with a changed character behaves the same way: it is a different string, and the lookup honestly reports no match. Address poisoning scams rely on that same habit of checking only the first and last few characters. When an address matters, compare the whole string.
A hit carries its own weight. Blocked virtual currency has reporting duties: the guidance states that "Blocked virtual currency must be reported to OFAC within 10 business days, and thereafter on an annual basis, so long as the virtual currency remains blocked." That is another reason to treat a hit as a matter for counsel or OFAC and not as something to resolve alone.
Tornado Cash: Three Notices and What a Delisting Changes in a Lookup
Tornado Cash is a listing with addresses that later came off the SDN list, and three OFAC notices show how that looks in the data. The facts below come from OFAC's Recent Actions notices and Treasury's press releases for the three dates, and the counts come from the address fields printed in those notices.
| Date | OFAC action | Address fields in the notice |
|---|---|---|
| August 8, 2022 | Tornado Cash added to the SDN list as an entity | 45 fields: 39 ETH and 6 USDC; 38 distinct ETH strings, and all 6 USDC strings repeat ETH strings |
| November 8, 2022 | Earlier listing deleted (the deletion section prints the record under each of its names: Tornado Cash, Tornado Cash Classic and Tornado Cash Nova) and Tornado Cash added again | Deleted record: the same 45 fields under each name; new entry: 90 ETH fields |
| March 21, 2025 | Tornado Cash entry deleted ("Tornado Cash Delisting") | 90 ETH fields removed |
Field counts parsed from the address text in the three Recent Actions notices. Individual addresses are not reproduced here.
August 8, 2022. Treasury announced that OFAC "sanctioned virtual currency mixer Tornado Cash, which has been used to launder more than $7 billion worth of virtual currency since its creation in 2019," and that the action was taken under Executive Order 13694, as amended. The release described the consequence for U.S. persons: "all property and interests in property of the entity above, Tornado Cash, that is in the United States or in the possession or control of U.S. persons is blocked and must be reported to OFAC." The 6 USDC fields in that listing repeat 6 of the ETH strings, a small real example of one address appearing under two labels, as in the ten repeated strings counted earlier.
November 8, 2022. The Treasury release says OFAC "delisted and simultaneously redesignated Tornado Cash under Executive Order (E.O.) 13722 and E.O. 13694, as amended," adding a basis tied to support for North Korea's activities. It states: "Effective immediately, the August 8, 2022 designation of Tornado Cash is no longer operative, and it is wholly replaced by today's action." In file terms, a delisting can be a replacement. The older entry came off and a new entry went on with 90 ETH fields, 37 of which repeat strings from the 38 distinct ETH strings in the August listing. A lookup of one of those 37 strings the day after would have hit a different entry, tagged DPRK3 and CYBER2, where the August entry carried CYBER2 alone.
March 21, 2025. Treasury's statement reads: "Based on the Administration's review of the novel legal and policy issues raised by use of financial sanctions against financial and commercial activity occurring within evolving technology and legal environments, we have exercised our discretion to remove the economic sanctions against Tornado Cash as reflected in Treasury's Monday filing in Van Loon v. Department of the Treasury." The removal did not close the North Korea concern. The same statement continues: "Treasury will continue to monitor closely any transactions that may benefit malicious cyber actors or the DPRK, and U.S. persons should exercise caution before engaging in transactions that present such risks." OFAC's notice for the day lists the Tornado Cash entry, with its 90 ETH fields, under deletions.
What the delisting did to the file. The October 28, 2026 file has no entry whose primary name is Tornado Cash. That is the whole effect of the deletion, and the file shows its limits. One individual's entry, whose email fields include an address at the tornado.cash domain, is still on the list with 8 ETH address fields and the DPRK3 program tag. The March 21, 2025 notice changed that entry in one respect: the tags before the change were DPRK3 and CYBER2, and after it only DPRK3. The delisting removed one entry and left other entries as they were.
Four lessons for lookups follow from the three notices:
OFAC's FAQ 897 describes the administrative route by which a listed party can ask for removal, called administrative reconsideration, and says that when a petition is granted the person or property is removed and the delisting is published in the Federal Register. Treasury's March 2025 statement describes a discretionary removal instead, so the Tornado Cash delisting does not show how long a petition takes or how often one succeeds. It shows that removals happen, and that the file changes when they do.
For the loss-and-reporting side of crypto risk, the guides on what to do if a wallet is drained and how to report a crypto scam cover reporting channels, and the regulation hub lists the other rule-by-rule explainers.
Frequently Asked Questions
How many crypto addresses are on OFAC's sanctions list?
On the SDN list published October 28, 2026, there are 1,075 digital currency address fields on 109 entries, covering 1,058 distinct address strings. The largest labels are XBT with 534 fields, TRX with 266, ETH with 124 and USDT with 94. The figure changes whenever OFAC updates the list, so quote it with the publication date.
Why does SDN.CSV alone show 523 addresses instead of 1,075?
Reading only the SDN.CSV file gives 523 matches, because its remarks column is cut at 1,000 characters and the remainder is in SDN_COMMENTS.CSV. Thirteen of the 523 are cut-off fragments. OFAC's tutorial on the legacy files tells users to download all four files in the series, and SDN.XML holds the complete data in one file.
How do I check whether a wallet address is on the OFAC list?
Paste the exact string into the "ID #" field of OFAC's Sanctions List Search tool, which returns only exact matches for that field, or parse the "Digital Currency Address" fields in SDN.XML and compare whole strings, lowercasing the ones that start 0x. Record the date and the list's publication date with the result.
Does a clean result mean an address is safe to send to?
No. It means that exact string is not in that file on that date. OFAC says its address listings "are not likely to be exhaustive," a wallet can hold many addresses, entities owned 50 percent or more by blocked persons are covered without being listed, and the list changes. This is general information, not legal advice.
Is each coin or blockchain counted separately on the list?
By currency label, yes: OFAC prints a ticker such as XBT, TRX or ETH on each field. Labels are not chains, though. The USDT label covers strings in three different formats, and 0x-format strings carry labels such as ETH, USDT, USDC, ARB and BSC. For screening, compare the string and ignore the label.
Is Tornado Cash still sanctioned?
OFAC deleted the Tornado Cash entry on March 21, 2025, and the October 28, 2026 file has no entry whose primary name is Tornado Cash. Other entries remain, including one individual's entry that still lists 8 ETH addresses under the DPRK3 tag. Treasury's statement kept a caution about transactions that may benefit North Korean or malicious cyber actors. Whether a given activity is permitted is a question for counsel.
Can an address be removed from the list?
Yes. Addresses leave the file when OFAC deletes or replaces the entry that lists them, either on a petition for administrative reconsideration, which FAQ 897 describes, or at OFAC's initiative, as in the March 2025 Tornado Cash notice. A removed string is no longer in the current file, and it may still appear in the archive of changes.
Counting and explanation, not legal, tax or investment advice. Nothing on this page recommends any service or product. Counts are computed from OFAC's published SDN files for the publication dated October 28, 2026; the list changes without notice, so check OFAC directly before relying on any figure.
Sources
Primary documents, market context, and methodology references behind this article.
Data behind every count. SDN.XML Publish_Date 10/28/2026, 19,484 records, 29,271,441 bytes, SHA-256 0213f3a0...f1a8; SDN.CSV 5,750,799 bytes, SHA-256 5f240bed...509d. Downloaded November 3, 2026.
Publish_Date 10/19/2026, 486 records, no digital currency address fields. Downloaded November 3, 2026.
SDN list update that added three entries with nine digital currency address fields. Checked November 3, 2026, when the Recent Actions index showed the latest list update on October 28 and a general license on October 29.
FAQ 562 (listings not likely to be exhaustive) and FAQ 563 (field structure and labels, up to 256 characters; https://ofac.treasury.gov/faqs/563). Checked November 3, 2026.
ID # field, exact matches only. Released May 18, 2021. Checked November 3, 2026.
Search logic (246, 253), definitions (559), compliance obligations (560), use of SDN identifiers (561), removal petitions (897; https://ofac.treasury.gov/faqs/897). Checked November 3, 2026.