DeepSeek restrictions reach inside the tools
DHS's DeepSeek restrictions reach third-party tools, too. A separate poisoned-model experiment shows why knowing whose models are inside matters.

DHS's newly public notice describes its July 24 order excluding DeepSeek and affiliate products from federal civilian procurement and removing them from civilian agency systems—including third-party products and services developed using DeepSeek implementations. Filed October 19 for publication October 20, it's a federal civilian restriction, not a consumer ban. For tool buyers, the practical question is: whose models are inside?
Local tools raise that question, too. In ProjectDiscovery's controlled experiment, a deliberately poisoned Qwen model drove Codex CLI to send dummy credentials from a local .env file to a collector. That demonstrates a model supply-chain risk; it doesn't establish that DeepSeek or all abliterated models steal keys. Verify where your models came from and limit what their tools can read and send, even when the agent runs on your own machine.