​

US Capitol dome — DHS Exclusion Order #2026-01 bans DeepSeek from all civilian federal agency IT systems

Photo: Pexels. The order reaches every civilian federal agency — and any vendor product built on DeepSeek.

TL;DR — On October 20, 2026, the Department of Homeland Security published Exclusion & Removal Order #2026-01: every civilian federal agency must rip out all DeepSeek products — including third-party software built on DeepSeek — and stop buying them. Signed in July, kept quiet until now, it's the first government-wide supply-chain exclusion of a Chinese open-weight AI model. The Pentagon is exempt. China has formally objected. And if your company sells software to the government, your compliance team just got new homework.

Disclosure: this article contains no affiliate links. Every claim below is sourced from the Federal Register filing and reporting from October 19–20, 2026, linked in-line.

What the Order Actually Says

The order is short, specific, and broader than the headlines suggest. Issued under the Federal Acquisition Supply Chain Security Act of 2018, it does three things:

  1. Removes — civilian agencies must remove all DeepSeek and DeepSeek-affiliate products from their information systems.
  2. Blocks purchases — agencies may not procure DeepSeek products going forward.
  3. Reaches downstream — and this is the part with teeth — agencies must also remove third-party products built on DeepSeek implementations. If a vendor's dashboard, analytics tool, or chatbot quietly runs on a DeepSeek model under the hood, it's covered.

The timeline matters. The order was signed on July 24, 2026 by DHS Secretary Markwayne Mullin, filed for public inspection on October 19, and published in the Federal Register on October 20 as FR Doc 2026-21447 (docket DHS-2026-0628). Nearly three months passed between signature and publication — a long fuse for an order this consequential.

Why "supply-chain exclusion" matters: This isn't an app ban or a stern memo. A supply-chain exclusion order is a formal legal instrument that makes a product radioactive across federal procurement. Contractors and subcontractors must certify their offerings are clean — and the "third-party products built on DeepSeek" clause means the certification burden flows down the entire vendor chain.

DHS's Stated Reasons

DHS cited "multiple threat vectors" in the order, including:

  • The possibility of data transfer to the People's Republic of China through DeepSeek software
  • Malware risk embedded in DeepSeek products
  • Broader supply-chain integrity concerns around a foreign-controlled AI model inside government systems

These are the same categories of concern that drove earlier US actions against Chinese technology — but this is the first time they've been aimed, government-wide, at an open-weight AI model rather than hardware or a consumer app. Open weights make the problem harder: anyone can download, fine-tune, and rebrand the model, which is exactly why the order extends to third-party products built on DeepSeek implementations.

Could Your AI Tool Be Affected? The Gateway Problem

Here's the part of the order that should make every AI-tool user pay attention. The ban doesn't just cover software made by DeepSeek — it reaches third-party products "built using DeepSeek implementations." That phrase is doing a lot of work, and it's deliberately vague.

As The Register pointed out in its October 20 coverage, this wording could plausibly catch AI gateway services — platforms like OpenRouter or Vercel's AI Gateway that route user requests to whichever model is cheapest or fastest at a given moment. If a gateway quietly routes your prompt through a DeepSeek model for one request out of a hundred, is your product "built using DeepSeek implementations"? The order doesn't say — and that ambiguity is the point. Government procurement officers will read the clause broadly, because their job is to avoid risk, not to parse technical nuance.

To be clear: this is The Register's interpretation, not a stated DHS position. But the plain-English takeaway stands regardless of how the clause is ultimately enforced:

  • Ask your vendors what models they route through. If an AI tool or API you use doesn't publish its model list, that's now a compliance question, not just a curiosity.
  • "Open weights" does not mean "clean supply chain." A model anyone can download can still carry geopolitical baggage.
  • Watch for vendor attestations. Expect software companies — especially those selling into government — to start publishing explicit "no DeepSeek" statements, the same way they published software bills of materials (SBOMs) after the SolarWinds-era executive orders.
Why this matters beyond government: Enterprise security teams routinely copy federal supply-chain standards into their own vendor requirements. A clause written for civilian agencies today becomes a line in corporate procurement questionnaires tomorrow. If your company uses AI gateways or multi-model routers, find out what's actually running under the hood — before a compliance audit asks.

Who's Exempt — and Who Responded

The Pentagon is exempt from this order. Military departments operate under separate supply-chain security authorities, and the Defense Department has its own processes for evaluating foreign technology risk. The exemption is procedural, not a vote of confidence in DeepSeek.

China responded the same day — and kept pushing. Foreign Ministry spokesperson Mao Ning said on October 20 that Beijing opposes the order, accusing Washington of "overstretching the concept of national security and politicizing technology and trade issues" (as reported by TechCrunch), and vowing to "resolutely safeguard the legitimate rights and interests of Chinese enterprises." The message was still circulating in international coverage on October 21 — a sign Beijing intends to keep this in the spotlight rather than let the exclusion settle quietly.

The other side of the story: While Washington squeezes, Beijing is stockpiling. Reuters reported on October 20 that ByteDance, Alibaba, and Tencent have ordered 3 million-plus Nvidia RTX PRO 5500 workstation GPUs — worth over $35 billion combined (roughly $11,400 each). The RTX PRO 5500 is the most powerful Nvidia chip still export-compliant for China; the more advanced Blackwell B300 is banned outright, and the H200 is approved only case by case. China's total orders reportedly exceed 6 million units against roughly 3 million planned for global 2027 production — and Nvidia has told customers they may receive only 5–10% of what they requested. Squeezed on one side, stockpiling on the other: this is the US–China AI decoupling playing out in real time.
Context: This order lands in a year when governments are simultaneously banning and embracing AI agents. On the very same day DHS published the DeepSeek exclusion, Japan's Digital Agency rolled out AI agents to roughly 180,000 government employees via its Gennai platform — with published safety standards. Washington fears the supply chain; Tokyo is deploying at national scale. Both stories are about the same question: who controls the AI inside government systems?

What It Means for Enterprises (Even Outside Government)

The order binds federal civilian agencies — not your company. But three groups should pay attention:

1. Government contractors and vendors

If you sell software to any civilian agency, you now need to prove a negative: that no component of your product is built on DeepSeek. Audit your model supply chain, document your base models, and expect the question in every RFP from here on.

2. Enterprise compliance and security teams

Large companies routinely mirror federal supply-chain standards in their own vendor requirements. Expect DeepSeek-derived components to start appearing on corporate prohibited-software lists — especially in finance, healthcare, and critical infrastructure, where regulators take cues from DHS.

3. AI startups building on open weights

The order is a case study in open-weight risk: a freely downloadable model can still be excluded government-wide when its provenance is the problem. If your product fine-tunes an open model, know exactly where that model came from — "it's open source" is not a compliance strategy.

What to Watch Next

  • Enforcement details — the order sets the requirement; agency-level implementation guidance (inventories, removal deadlines, certification language) will follow.
  • Vendor disclosures — watch for software vendors proactively publishing "no DeepSeek" attestations, the same way they published SBOMs after the SolarWinds-era executive orders.
  • Retaliation risk — Beijing's fast response suggests this becomes another data point in the US–China technology standoff, alongside chip export controls and the ongoing fights over AI training data.
  • The open-weight precedent — if DHS can exclude one open-weight model government-wide, the legal template now exists for others. Model provenance just became a board-level issue.
The bottom line: The US government just drew its clearest line yet around Chinese AI inside federal systems — and it drew it around the supply chain, not just the app. For everyone building on open models, the message is simple: know your model's provenance, document it, and don't assume "open" means "safe."

Frequently Asked Questions

What does the DHS DeepSeek exclusion order do?

Exclusion & Removal Order #2026-01 requires every civilian federal agency to remove all DeepSeek and affiliate products from its information systems, stop buying them, and also remove third-party products built on DeepSeek implementations. It was signed July 24, 2026 by DHS Secretary Markwayne Mullin and published in the Federal Register on October 20, 2026 (FR Doc 2026-21447).

Does the DeepSeek ban apply to the Pentagon?

No. The order covers civilian federal agencies. The Pentagon and military departments are exempt from this particular exclusion order, though the Defense Department maintains its own separate supply-chain security authorities.

Why did DHS ban DeepSeek?

DHS cited multiple threat vectors: the possibility of data being transferred to the People's Republic of China, malware risk in DeepSeek software, and broader supply-chain concerns. The order was issued under the Federal Acquisition Supply Chain Security Act of 2018.

Does the ban affect private companies?

Directly, no — the order binds federal civilian agencies, not private firms. But it sets a powerful precedent: any vendor selling to the government must now prove its products contain no DeepSeek-derived components, and compliance teams at large enterprises are treating it as a signal to audit their own AI supply chains.

How did China respond to the DeepSeek ban?

Chinese Foreign Ministry spokesperson Mao Ning said on October 20, 2026 that China opposes the order, accusing the US of "overstretching the concept of national security and politicizing technology and trade issues" and vowing to "resolutely safeguard the legitimate rights and interests of Chinese enterprises" (as reported by TechCrunch). Beijing's message was still circulating in international coverage on October 21.

Could my AI tool be affected by the DeepSeek ban?

The order's "built using DeepSeek implementations" clause is deliberately broad — and, as The Register noted, could plausibly reach AI gateway services that route requests through DeepSeek models. The order binds federal agencies, not private users. But the practical move is the same for everyone: ask your AI vendors what models they actually route through, and expect "no DeepSeek" attestations to become standard in government and enterprise procurement.

Is this the first US government ban on a Chinese AI model?

It is the first government-wide supply-chain exclusion order targeting a Chinese open-weight AI model. Earlier actions were narrower — agency-level restrictions or app-store removals — while this order reaches every civilian agency and extends to third-party products built on DeepSeek.

Related reading: Yelp, Delta, JPMorgan and Schwab Are Blocking AI Agents — What It Means for You · Meta Walked Back Its AI-Training Terms · What Are AI Agents? The Complete Beginner's Guide

No comments:

Post a Comment

​