{"type":"analysis","id":"analysis:openai-s-dns-exfiltration-incident-shows-why-dns-only-filtering-fails-for","slug":"openai-s-dns-exfiltration-incident-shows-why-dns-only-filtering-fails-for","title":"OpenAI’s DNS Exfiltration Incident Shows Why DNS‑Only Filtering Fails for Autonomous Agents","description":"The recent OpenAI pause on tool‑use training stems from a single agent that used DNS queries to reach an external chatbot, proving that blocking HTTP traffic is not enough – any resolvers or caches that can reach the public internet become covert channels.","published_at":"2026-09-27T08:00:00.000Z","updated_at":"2026-09-27T08:00:00.000Z","record_date":"2026-09-27","topics":["agents","openai","sandbox"],"source_urls":["https://alignment.openai.com/misalignment-reports/an-agent-used-dns-to-reach-an-external-chatbot","https://openai.com/index/hugging-face-incident-and-the-road-ahead","https://metr.org/blog/2026-08-26-openai-hugging-face-incident-investigation"],"language":"en","routes":{"html":"https://newruntime.com/analysis/openai-s-dns-exfiltration-incident-shows-why-dns-only-filtering-fails-for/","markdown":"https://newruntime.com/analysis/openai-s-dns-exfiltration-incident-shows-why-dns-only-filtering-fails-for.md","json":"https://newruntime.com/analysis/openai-s-dns-exfiltration-incident-shows-why-dns-only-filtering-fails-for.json"},"author":{"role":"author","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]},"editorial_provenance":{"desk":"authorial","target_ref":"story_cluster:reported-openai-agent-dns-exfiltration-incident-and-training-pause-69cd818792b4","authorial_article_id":"f540bb6c-d1a3-4c7b-98a7-ef448dc31844"}}