DHS Orders DeepSeek Out of Every US Civilian Agency -- Including Third-Party Products 'Developed Using DeepSeek Implementations', Which Turns Model Lineage Into a Procurement Question

The US Department of Homeland Security filed a notice on October 19, 2026, published in the Federal Register on October 20 as document 2026-21447 under docket DHS-2026-0628, announcing that the Secretary has issued an order with two parts. First, it excludes "information technology products and services developed by Hangzhou DeepSeek Artificial Intelligence Co., Ltd (DeepSeek)", including affiliates as defined in 48 CFR 2.101, from federal civilian agency procurements. Second, it orders the removal of "all DeepSeek and DeepSeek-affiliate products, and third-party products and services developed using DeepSeek implementations, from civilian agency information technology."

The legal route

The order uses the Federal Acquisition Supply Chain Security Act of 2018 (41 U.S.C. 1321-1328) and its regulations at 41 CFR 201-1, and follows "review of the Federal Acquisition Security Council Recommendation and affiliated evidence." That makes it a supply-chain exclusion and removal order, binding on civilian executive-branch agencies, rather than guidance. Implementation questions go to a FASCSA order team in CISA's Cybersecurity Division. The signed order itself sits in an appendix and on regulations.gov; the published notice is a summary signed by DHS General Counsel James H. Percival II.

The stated reasons

Reuters, as carried by The Economic Times, reported that DHS said DeepSeek models pose "multiple threat vectors" and that use "may result in the transfer of sensitive data to the PRC if used by US government employees or vendors." DHS also said, per the same report, that agency use "could produce actionable intelligence on US persons and/or government agencies. The models themselves may contain malware or other security vulnerabilities." A July memo made public on Monday had told agencies to monitor traffic to and from government websites for DeepSeek-related risk. Earlier bans by Commerce and the Navy, and by states including New York, Tennessee and Virginia, covered use on government devices; this order covers procurement and removal across civilian agencies.

What remains uncertain. We have read the Federal Register notice, not the signed order in its appendix, so we cannot confirm its deadlines, exception process or exact definition of "DeepSeek implementations". Secondary reports disagree on whether removal is immediate. National security systems fall under a different FASCSA track. The order does not reach private companies, but federal contractors will meet it through their customers.

Analysis: The third-party clause is the engineering story. DeepSeek publishes its weights under permissive licences -- this digest covered the MIT-licensed V4.1-Flash update on October 18 -- and those weights have been fine-tuned, distilled into smaller models and embedded in products whose model cards do not always say so. If "developed using DeepSeek implementations" is read to include derivatives, a vendor selling to a civilian agency must be able to show which base models, distillation teachers and hosted APIs sit under each feature. Most AI supply-chain inventories record packages and containers, not weights lineage. Teams selling to the US government should start an AI bill of materials that names base checkpoints and their provenance now, and treat 'which model is this, really?' as a question auditors will ask. The same logic will be applied to other model families as export and procurement rules spread.