Blocking one hostname isn't enough: operator kept a second shim route to DeepSeek
colinmcnamara · x · 2026-11-22
Colin McNamara illustrates a gap in enterprise AI controls: an ARTEX operator had two routes to DeepSeek — a reseller and a local shim hitting the API directly. Blocking one hostname leaves the other route open, showing why hostname blacklists alone fail for AI governance.
Related event: FBI ARTEX Attack Report Sheds Light on LLM Gateway Risks(4 posts)→
More from Safety
- Anthropic's $1.5B book settlement unpaid; call grows to raise it to $20K per book — TuhinChakr · 2026-11-22
- AI Safety Researcher: Positive AI Futures Require Transparent US-China Collaboration — LuizaJarovsky · 2026-11-22
- NAS Report on Scientific Fraud Itself Contains Hallucinated Citations — KordingLab · 2026-11-22
- Hugging Face CEO: Answer to Chinese Open-Source AI Is More US Open Source — coherence · 2026-11-22
- MCP Is Not a Trust Boundary: why agent tool calls need signed permissions — JeremyCMorgan · 2026-11-22
- ContextDuty: open-source local-first firewall stops secrets and PII from reaching AI coding tools — Interesting_Big_8974 · 2026-11-21