Friday, 23 October 2026Global tech news & guides — what changed, and what it means for you.
AuTechWire
Original illustration: a dark government server room at night, rows of racks with one glowing red node being pulled out by a silhouetted hand, cables hanging, cool blue emergency lighting with an amber alarm glow in the distance, teal and amber grade

The US Just Ordered DeepSeek Ripped Out of Federal Systems — Including Apps That Quietly Use Its Models

by

In brief

  • The Department of Homeland Security has ordered all US federal civilian agencies to remove DeepSeek products from their IT systems and stop buying them, under the Federal Acquisition Supply Chain Security Act of 2018.
  • The order does two separate things: it excludes DeepSeek products from future procurement, and it mandates the removal of everything already installed — including third-party products and services “developed using DeepSeek implementations.”
  • DHS says DeepSeek models present “multiple threat vectors,” warning that use by government employees or vendors “may result in the transfer of sensitive data” to China.
  • The order covers civilian agencies only — the Pentagon is exempt, and exceptions are possible with a written request. Private and overseas users are not affected.
  • The open-source paradox: DeepSeek’s weights are freely downloadable, so the order is really a data-custody rule about which software runs on government machines — and vendors that quietly built on DeepSeek models now have an audit to run.

What the order actually says

The notice, which went on public inspection on October 19 and was published in the Federal Register on October 20 (docket DHS-2026-0628), is not one prohibition but two. That distinction matters, because the second reaches much further than the first.

The first instruction is a procurement exclusion: federal civilian agencies may no longer buy IT products or services developed by Hangzhou DeepSeek Artificial Intelligence Co., Ltd, including affiliated entities. Going forward, DeepSeek is simply off the approved vendor list.

The second is a removal mandate, and it is the broader of the two. It covers “all DeepSeek and DeepSeek-affiliate products, and third-party products and services developed using DeepSeek implementations,” which must come out of civilian agency information technology. Read that carefully: it is not just DeepSeek’s own apps. Any vendor product that runs on DeepSeek’s models — and many apps quietly run on borrowed AI models — is caught. For federal vendors, the question is no longer “did we buy DeepSeek” but “does anything in our stack use it.”

The legal authority is the Federal Acquisition Supply Chain Security Act of 2018, codified at 41 U.S.C. 1321 to 1328, with the Secretary of Homeland Security acting after a review by the Federal Acquisition Security Council. Bloomberg and CyberScoop report that the underlying order was signed by Homeland Security Secretary Markwayne Mullin months before it was made public; the Federal Register notice itself carries the signature of the department’s General Counsel, James H. Percival II. Agencies can request exceptions, but they must apply 60 days in advance with a “compelling justification.”

Why Washington did this

DHS’s reasoning, as stated in the order, is blunt. DeepSeek’s models present “multiple threat vectors,” and the department warned that their use by government employees or contractors “may result in the transfer of sensitive data to the People’s Republic of China.” The department argued the technology could be used to “track or digitally fingerprint” users, that prompts might result in sensitive data transfers to the Chinese government, and that the models themselves “may contain malware or other security vulnerabilities” — potentially producing “actionable intelligence on US persons and/or government agencies.” Cointelegraph’s reporting adds that DHS pointed to security vulnerabilities identified in DeepSeek’s iOS application.

The notice did not identify specific instances of data being transferred. It did not need to: the order is a supply-chain exclusion, and those are issued on assessed risk, not proven incidents. In a July memo made public alongside the order, DHS had already told federal agencies to monitor traffic flows in and out of government websites to address potential risks from DeepSeek — the removal order is the escalation of a concern that has been building for months.

The context is the crackdown that has been brewing since DeepSeek stunned the industry with its R1 model in 2025: an open-source system, trained with less powerful chips at a fraction of the cost of American rivals, that outperformed models from OpenAI and Anthropic on several complex tests. The free app was downloaded by millions of Americans. At the time, a full US ban was floated, with one cybersecurity expert calling DeepSeek’s privacy policy not “worth the paper it is written on.” Commerce Department barred it from government devices in 2025, and the Navy directed its personnel not to use it. Australia banned it from government systems and devices in February 2025. This order turns what had been agency-by-agency discretion into government-wide policy.

The third-party catch-all is the real story

Most coverage frames this as “DeepSeek banned from government computers.” That understates it. The phrase “developed using DeepSeek implementations” reaches into the software supply chain: any vendor product that built on DeepSeek’s models is now disqualifying for civilian federal customers unless the vendor re-platforms or wins an exception.

That lands awkwardly because of how AI models actually flow through the industry. Open-weight models like DeepSeek’s are embedded, fine-tuned, re-hosted and rebranded constantly; an app’s marketing may never mention DeepSeek while its inference stack quietly runs a DeepSeek-derived model. Days before the order, DeepSeek shipped its V4.1-Flash update alongside its own Search and Fetch APIs for developers building agents — the company’s developer footprint was growing, not shrinking.

The compliance picture gets murkier still because of AI gateways. Services like OpenRouter and Vercel’s AI Gateway route each request to whichever provider they judge the best fit — DeepSeek included — unless the customer pins the provider down. The Register flags the awkward possibility: a federal agency could be running DeepSeek models without ever choosing them, simply because nobody constrained the gateway. The order never defines “DeepSeek implementations,” so agencies now have to figure out whether that phrase means ongoing API access to DeepSeek’s models or merely software built with its help — a question with very different answers.

Vendors serving federal customers now have a straightforward but urgent job: audit the model lineage of every AI feature they ship, document it, and replace or except anything DeepSeek-derived.

The open-source paradox

Here is the nuance nobody leads with: banning DeepSeek-the-company does not remove DeepSeek-the-model from the world. The weights are open and freely downloadable; anyone can run them on their own hardware, and DHS cannot unpublish them. The order is therefore not a model ban at all — it is a data-custody and procurement rule about which software is allowed on government machines and in government contracts.

That distinction explains the order’s shape. DHS is not worried about the model’s existence; it is worried about DeepSeek-hosted services, where prompts and data flow to servers in China, where national security laws let officials demand company systems’ data. A self-hosted, air-gapped copy of an open-weight model does not have that exposure — but the order’s exclusion language does not try to draw that line finely. For government IT, the practical rule is simpler: if DeepSeek is anywhere in the lineage, it goes.

Private users and overseas users are unaffected, and the military side is carved out: the order covers civilian agencies, with the Pentagon exempt and exceptions available on written request. This is a government-systems rule, not a consumer ban — though the political signal to the broader market is unmistakable. Vendors selling into allied governments should take note too: Washington’s supply-chain orders have a way of becoming procurement norms elsewhere, as the earlier Huawei and Kaspersky exclusions showed.

What to watch next

Beijing has already answered the order. Foreign Ministry spokesperson Mao Ning said Tuesday that China opposes “overstretching the concept of national security and politicizing technology and trade issues,” promising to “resolutely safeguard the legitimate rights and interests of Chinese enterprises” (TechCrunch, Oct 20). No direct response from DeepSeek itself has surfaced, and no agency has yet published a compliance plan for the removal mandate. Three things to track from here: whether any major federal vendor discloses a DeepSeek dependency and what it replaces it with; whether agencies publish compliance plans for the removal mandate, which is the operationally hard part; and whether this order becomes the template for further supply-chain exclusions — Washington has accused Chinese labs of distilling capabilities from US models, and the Federal Acquisition Security Council now has a proven playbook. We will update this article as the responses land.

Sources

Related reading: Anthropic in Talks for a Second $45 Billion Nscale Deal: What It Means · One Hacker, $5,000, and an Army of AI Agents: How 100+ Company Sites Were Breached · DeepMind’s AI Agents Beat Minecraft in 27 Hours — It Cost $520

Sources: Reuters (via The Hindu BusinessLine) (2026-10-20 — DHS order, “multiple threat vectors,” sensitive-data-to-PRC warning, July memo on traffic monitoring); SiliconANGLE (2026-10-19 — 2018 Act basis, FASC review, digital-fingerprinting language, R1 context); Digital Trends (2026-10-20 — civilian-agencies scope, Pentagon exemption, written-request exceptions, third-party reach, servers-in-China argument); Dealroom (2026-10-20 — docket DHS-2026-0628, Mullin signature, 60-day “compelling justification” exception window, V4.1-Flash timing); Cointelegraph (2026-10-20 — iOS-app vulnerabilities cited, Commerce/Navy/Australia earlier restrictions); TechCrunch (2026-10-20 — Beijing pushback: Mao Ning “overstretching the concept of national security,” Dec-2025 intel-systems law; re-verified firsthand 2026-10-21); The Register (2026-10-20 — order vagueness, OpenRouter/Vercel AI Gateway inadvertent-routing risk, “developed using” ambiguity; re-verified firsthand 2026-10-21); The Hacker News (2026-10-21 — July 24 signature date, “DeepSeek implementations” undefined, 2018 law’s first 2025 use against Acronis; re-verified firsthand 2026-10-21).

Shoaib Hassan

Shoaib Hassan is the founder and editor of AuTechWire, an independent technology publication covering broadband, mobile networks, privacy, startups, and consumer tech.

Related Stories

Leave a Comment