TL;DR: On October 19, 2026, the U.S. Department of Homeland Security ordered federal civilian agencies to remove DeepSeek products from their IT systems and barred new purchases. The order also covers many third-party services built on DeepSeek models. DHS cited data-transfer and security risks tied to the People’s Republic of China. Private companies are not covered by this civilian-agency order, but contractors who touch federal systems should read the notice carefully.
The U.S. government just drew a hard line under one of China’s most watched AI labs. According to notices covered by The Wall Street Journal and Reuters, DHS is ordering DeepSeek removed from federal civilian IT systems and locking the company out of related procurements. Here is what the order actually does, who it hits, and what it means if you build or buy AI tools that touch the government.
What DHS ordered on October 19
A Federal Register public-inspection notice titled for the exclusion and removal of DeepSeek products from Federal Civilian Executive Branch IT systems and procurements was posted for Monday’s filing cycle. Quartz reported that publication in the Federal Register is scheduled for Tuesday, and that the Secretary of Homeland Security acted under the Federal Acquisition Supply Chain Security Act of 2018 after a Federal Acquisition Security Council recommendation.
In plain English: civilian agencies must pull DeepSeek products off their systems, and they generally cannot buy new ones. Reuters summarized DHS language that the models pose “multiple threat vectors,” including potential transfer of sensitive data to the PRC, intelligence collection on U.S. persons or agencies, and possible malware or other vulnerabilities in the models themselves.
| Element | What sources report |
|---|---|
| Who must remove | Federal civilian executive branch agencies |
| Company named | Hangzhou DeepSeek Artificial Intelligence Co., Ltd. and defined affiliates |
| Products in scope | DeepSeek IT products/services and many third-party services developed using DeepSeek implementations |
| Legal hook | Federal Acquisition Supply Chain Security Act of 2018 (FASCSA) |
| Docket / questions | regulations.gov docket DHS-2026-0628; CISA FASCSA Order Implementation Team |
How this differs from earlier DeepSeek bans
This is not the first U.S. restriction. Reuters noted that agencies such as the Commerce Department and the Navy had already barred DeepSeek on government devices, and that states including New York, Tennessee, and Virginia had taken similar steps. What makes Monday’s action different is the breadth of a civilian-wide removal-plus-procurement exclusion under FASCSA, plus explicit coverage of third-party services that wrap DeepSeek models.
Bloomberg Law’s coverage framed the move as part of a wider Trump administration push against Chinese AI products that undercut U.S. labs on price. That competitive angle matters for Silicon Valley, but the legal text agencies will follow is the supply-chain security order, not market share.

What “third-party services using DeepSeek” likely means
Quartz reported that the removal requirement reaches third-party products and services developed using DeepSeek implementations. In practice, that can catch:
- Chat or agent apps that route prompts to DeepSeek-hosted endpoints
- Fine-tunes or distilled models that vendors advertise as DeepSeek-based
- Vendor APIs that quietly fall back to DeepSeek when another model is busy
- Open-weight deployments that agencies still treat as “DeepSeek products” under the order’s definitions
Exact scope turns on the signed order and FAR definitions of affiliates. Agencies and vendors should pull the signed order from regulations.gov rather than guess from headlines. DHS said a copy is available under docket DHS-2026-0628.
Why Washington keeps circling DeepSeek
DeepSeek’s R1 release in early 2025 rattled markets with strong reasoning performance at lower cost. U.S. lawmakers have argued the lab’s ties to Beijing are significant; Quartz cited Bloomberg reporting on an April 2025 House Select Committee on China letter. Separately, Anthropic alleged in a September report that DeepSeek was among China-based labs engaged in illicit distillation, logging millions of related exchanges in July 2026. Those claims are Anthropic’s; DeepSeek’s response was not detailed in the civilian-agency coverage we reviewed for this piece.
For readers tracking the open-weight side of the story, our earlier look at DeepSeek V4.1-Flash-1017 covered why agencies and enterprises alike were testing the models in the first place: cheap agent tasks and downloadable weights. Today’s order is about federal civilian risk, not a ban on private hobby use.
Who is not automatically covered
Based on the reporting available Monday:
- Private companies using DeepSeek for their own products are not themselves “federal civilian agencies.”
- State and local governments follow their own rules unless they adopt similar bans.
- Defense systems sit outside the “civilian executive branch” framing of this notice, though DoD components may already have separate restrictions.
- Contractors can still be pulled in if they supply IT to covered agencies or embed DeepSeek into deliverables those agencies must remove.
If you sell into the federal market, treat this like any other FASCSA exclusion: map dependencies, ask subcontractors which models sit behind their APIs, and document replacements before the next audit cycle.
What builders and buyers should do this week
- Inventory every AI endpoint your federal-facing stack calls, including “router” layers that pick models dynamically.
- Ask vendors in writing whether any DeepSeek implementation is in the path, even as a fallback.
- Watch the Federal Register publication and the signed order PDF for deadlines and exception language.
- If you still need open-weight reasoning models for non-federal work, separate those environments from anything that touches civilian agency networks.
The broader China AI export and control fight is still moving in both directions. For context on Beijing’s own controls, see our earlier piece on China’s AI export permission rules. And for how agent risk stories are landing in industry, compare Monday’s government order with our coverage of OpenAI’s misalignment incident disclosures.
Bottom line
DHS has told U.S. federal civilian agencies to get DeepSeek off their systems and out of their shopping carts. The order leans on a 2018 supply-chain security statute, names Hangzhou DeepSeek and affiliates, and reaches many third-party wrappers. It is a big signal for vendors who baked DeepSeek into “US-ready” stacks without a federal compliance story. Read the docket, map your dependencies, and do not assume a private SaaS label keeps you clear if the underlying model is DeepSeek.



