Skip to content
Sign in
Technology · North America

DHS orders federal agencies to remove DeepSeek technology

The Department of Homeland Security directed federal agencies to remove covered DeepSeek technology on October 19 over security concerns, and restricted federal purchases of covered products and services.

AI-assisted synthesis · Based on 5 outlets' reporting · Article text read from 3 of 5 outletsHow it's made

View timeline · 5 entries
5 outlets2 regionsLatest reporting 3 min read
Coverage: Too few ratedL 0 · C 1 · R 1 · 3 unrated

What happened

Key facts

  • The order was signed by Homeland Security Secretary Markwayne Mullin and took effect upon issuance.
  • The Department of Homeland Security said employee or vendor prompts could expose sensitive information to China, which combined with public information could reveal intelligence about U.S. persons or government programs.
  • The order describes potential risks; it does not report that information was transferred.

The brief

The Department of Homeland Security ordered federal civilian agencies to remove covered DeepSeek technology, citing risks to information security in government systems. DHS Secretary Markwayne Mullin signed the order on July 24, 2026, under the Federal Acquisition Supply Chain Security Act of 2018.

The directive gives agencies 60 days to remove covered technology and restricts future federal purchases of covered products and services. DHS said prompts entered into DeepSeek by government employees or vendors could expose sensitive information to China.

The department said that information, when combined with public material, could reveal intelligence about U.S. persons or government programs. The stated concern is a potential exposure pathway; the sources do not report a transfer of information.

The order also sets out a route for agencies seeking an exception: they had 60 days after issuance to submit a written request, provide a compelling justification and describe alternative mitigations. The order’s removal requirement and its exception process therefore place implementation decisions with federal agencies, subject to the conditions DHS specified.

The coverage emphasizes different parts of the measure. EconoTimes describes restrictions on covered federal purchases and the exception process. MeriTalk highlights the removal period and says the purchase ban extends to third-party products and services built using DeepSeek implementations.

Startup Fortune characterizes the order as barring DeepSeek from federal contracts and notes that it does not place the company on the Entity List. These accounts describe procurement and system-use restrictions, not an Entity List designation. DHS also warned that DeepSeek models could generate inaccurate, biased or harmful content.

Separately, Startup Fortune reported that an Anthropic threat report dated September 10 accused DeepSeek and Moonshot AI of routing more than 35 million combined user requests to Claude models, some of which allegedly contained data linked to Chinese police and military.

That allegation is attributed to Anthropic’s report and is distinct from the security rationale DHS gave for its order. The order was publicly noticed on October 19, with Federal Register publication scheduled for October 20, according to EconoTimes and MeriTalk.

MeriTalk says the restrictions had already taken effect in late July after Mullin signed the order; EconoTimes says the order took effect upon issuance. The reported publication timing therefore concerns public notice of an order whose effective date the outlets place at issuance.

Why it matters

  • Federal agencies face the operational cost of removing covered DeepSeek technology within 60 days and evaluating any exception requests under the order’s written-justification and mitigation requirements.
  • Government employees and vendors are the users exposed to the specific information risk DHS described: prompts could reveal sensitive information that, combined with public material, may expose intelligence about U.S. persons or government programs.
  • Federal contractors and providers of covered products and services face procurement restrictions; MeriTalk says the scope includes third-party products and services built using DeepSeek implementations.
  • Agencies seeking to retain covered technology must submit a compelling justification and proposed alternative mitigations within the 60-day request period.

What to watch next

  • Whether federal agencies complete removal of covered technology within the 60-day period described in the order.
  • Whether agencies submit written exception requests with compelling justifications and proposed alternative mitigations within the stated 60-day period.
  • Whether the Federal Register publishes the order on October 20, as scheduled in the reported notice.
  • How agencies apply the purchase restrictions to covered third-party products and services using DeepSeek implementations.

How it's being covered

Coverage analysisShow details
5 source articles · 5 unique outlets
Outlet political mix: Too few rated· 1 Center · 1 Right · 3 unrated
Where the outlets are based: US/Canada 40% · Asia 40% · Other 20%
Outlet political mix
Too few rated
Left
Center
Right
0 outlets
1 outlet
1 outlet
The marker shows coverage balance: each unique outlet counts once. 3 unrated outlets are not included.
Geography
Where the outlets covering this story are based.
5 unique outletsDominant coverage: US/Canada
How we measure coverage

How outlets' accounts compare

2 framing differences · 3 uncorroborated claims · 1 information gap
The reports repeat the same account with different emphasis; its central claims are not independently confirmed in the reporting Updat3 read.Compared across 3 reports whose article text Updat3 read; 2 other outlets were checked by headline only.
Framing / emphasis differences
Sources emphasise different angles, actors or consequences of the same reporting.
  • EconoTimes focuses on the order’s information-exposure rationale, federal purchasing restrictions and exception process; MeriTalk foregrounds removal, third-party products and model-output risks; Startup Fortune stresses the federal-contract bar and absence of an Entity List listing.
  • The sources describe potential exposure risks but do not report that sensitive information was transferred.
Updat3: These are differences of emphasis, not disputes about what is reported. They do not show that the reported claims are true.
One-sided or uncorroborated claims
Claims that come from one party or one source family and are not independently corroborated.
  • DHS attributes the potential information risk to prompts entered by employees or vendors; Startup Fortune separately attributes the request-routing allegation to an Anthropic threat report.
  • MeriTalk quotes DHS describing DeepSeek as presenting “multiple threat vectors” that pose a significant cybersecurity risk to U.S. government systems.
  • Startup Fortune reports that an Anthropic threat report accused DeepSeek and Moonshot AI of routing more than 35 million combined user requests to Claude models.
Updat3: Not independently corroborated yet — treat as a claim, not an established fact.
Not established by the reporting
Information the available reporting does not contain or confirm. This is a gap, not a disagreement.
  • The sources do not provide an independent assessment of the security risks described by DHS.
Updat3: Updat3 cannot conclude anything about this from the current sources.

Timeline

Developments from this story's sources, dated background we compiled and fact-checked, and our earlier coverage. Each row says which.
  1. The House Intelligence Committee released a report on Huawei and ZTE, citing security concerns.
    Background · compiled and fact-checked by Updat3
  2. Liang Wenfeng founded DeepSeek in Hangzhou, China.
    Background · compiled and fact-checked by Updat3
  3. DeepSeek released its V3 model.
    Background · compiled and fact-checked by Updat3
  4. DeepSeek released its R1 reasoning model.
    Background · compiled and fact-checked by Updat3
  5. Before the federal order, the U.S. Navy warned personnel on January 24, 2025, not to use DeepSeek’s generative-AI tools, citing security and ethical concerns.
    Background · from our historical context

How we got here

Before the federal order, the U.S. Navy warned personnel on January 24, 2025, not to use DeepSeek’s generative-AI tools, citing security and ethical concerns.

DeepSeek had released its V3 model on December 26, 2024, and its R1 reasoning model on January 20, 2025; the company, founded in Hangzhou in 2023 by Liang Wenfeng, drew attention for models it described as comparatively low-cost.

Original sources

2 of 5 articles · Asia · Show all

Every story links to the reporting it was built from. How we choose sources

Spotted a factual error, a broken link or a misleading summary? Tell us.