Treasury delists 76 stale SDN entries in sanctions modernization push

What happened

On 18 June 2026, the US Department of the Treasury removed 76 outdated targets from its sanctions list. Treasury acted through OFAC, the US Office of Foreign Assets Control. The list in question is the Specially Designated Nationals and Blocked Persons (SDN) List, the core dataset that screening systems run names against.

Treasury grouped the removals into four categories. They covered deceased individuals, scrapped or decommissioned vessels, and persons tied to illicit financial networks that no longer exist. The fourth category covered individuals designated more than 10 years ago who lack sufficient identifiers for continued screening and do not appear to pose an ongoing threat.

Treasury framed the action as the start of a broader sanctions modernization initiative. Treasury Secretary Scott Bessent discussed the initiative at the No Money for Terror ministerial conference in Paris, held on 19 May 2026. Per Treasury, the most effective sanctions are “aggressive and targeted, with defined timelines.”

Why it matters

A delisting is a screening event, not a quiet administrative footnote. Most teams build their list-management discipline around additions, where a new designation triggers an immediate rescreen. Removals deserve the same rigor, and they rarely get it.

The interpretation here is straightforward. Clearing 76 stale entries should cut false positives, because deceased people, scrapped ships, and defunct networks generate matches that waste analyst time. That benefit only lands if the removals reach your live screening and your historical alert backlog. If your refresh lags, you keep alerting on names Treasury has already retired.

The fourth category carries a quieter signal. Treasury removed people designated more than 10 years ago whose identifiers were too weak to screen against reliably. That is a reminder about your own match logic. Loose matching against thin identifiers is what manufactures the false positives a delisting is supposed to clear.

Practitioner angle

Treat this delisting as a live screening task, not a news item to file.

• Confirm your SDN refresh captures removals same-day, not just additions. Many feeds prioritize new designations and treat deletions as lower urgency.
• Clear the 76 delisted targets from live screening and work them out of the historical alert backlog, so analysts stop reviewing alerts Treasury has retired.
• Audit any open alerts tied to the removed categories: deceased individuals, decommissioned vessels, and defunct networks. These are the most likely to be orphaned false positives.
• Pressure-test your match logic against thin-identifier records. If a future delisting leaves orphaned hits, your fuzzy matching is too loose for the data behind it.

The single most important action: verify today that your sanctions feed applies removals as fast as it applies additions, then reconcile the 76 cleared names through both live screening and the backlog.