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)→

Original post →

More from Safety

Safety channel →