AI Safety Filters Can Be Used Against You
Key Takeaway
AI safety filters are frequently weaponized by both attackers and defenders to trigger refusals, effectively blocking frontier closed models from analyzing threat data while open-source models bypass these constraints to complete security tasks.
Highlights
A tracking script found on a top website hides a fake AI instruction string designed to trigger safety filters and prevent AI models from reading the code.
Frontier closed models like OpenAI's Astra and Anthropic's Claude block deobfuscation tasks when encountering safety trigger keywords, whereas open models like GLM and DeepSeek ignore these triggers and complete the work.
Tracebit's context bombs reduce an AI hacker's success rate at reaching full admin access from 93% down to 0% by weaponizing the attacker's own guardrails.
Hugging Face investigators were blocked by major Western AI safety filters when trying to analyze 17,000 attacker action logs, forcing them to use an open model instead.
Timeline
Discovery of Safety Filter Triggers in Tracking Scripts
Researchers crawling top websites identified an obfuscated fingerprinting script containing names related to biological poisons and sensitive political topics. This technique acts as a tripwire designed to force automated AI analysis tools into immediate safety refusals.
- A tracking script on a top website contains hidden strings that mimic poison-making instructions and political keywords.
- These strings are packed with terms intended to trip AI safety filters and prevent models from reading the underlying code.
Frontier Versus Open Model Responses to Trigger Strings
Testing the script against major closed models results in safety blocks under biological and political risk policies, even with explicit warnings that the names are fake. In contrast, open models parse through the decoy naming conventions, recognize them as mathematical variables, and execute the requested tasks without intervention.
- OpenAI Astra and Claude opus models refuse or get cut off immediately when attempting to read the obfuscated script.
- Open-source models such as GLM, DeepSeek, and Kimi successfully ignore the trigger phrases and process the underlying code.
Evolution of Anti-AI Techniques and Context Bombs
Beyond simple trackers, both malware authors and defenders use safety tripwires to confuse security scanners and automated agents. Planting context bombs inside target environments forces attacking AI agents to halt their operations upon reading fake sensitive data, turning safety guardrails into an effective kill switch.
- The underlying script resolves to a standard anti-bot tool originating from a Russian company named Servicepipe.
- Security company Tracebit uses context bombs inside canary files to drop an AI hacker's admin access success rate from 93% to zero.
Real-World Impact on Incident Responders
Because safety filters cannot distinguish between an attacker and a security responder, major lab models routinely hinder defensive investigations. This limitation drives security professionals toward open models that allow unrestricted analysis of cyber threat data.
- Hugging Face investigators were blocked by Western AI safety filters from analyzing thousands of hacker logs during a real security incident.
- Responders had to rely on locally hosted open-source models like GLM to bypass rigid safety restrictions.
Description
A browser fingerprinting script found on one of the internet's top 10,000 websites hides poison-themed text, so any AI asked to read it refuses. 🔗 Relevant Links Why Is This Fingerprinting Script Creating Bioweapons?: https://nullpt.rs/fingerprinting-bioweapons ❤️ More about us Radically better observability stack: https://betterstack.com/ Written tutorials: https://betterstack.com/community/ Example projects: https://github.com/BetterStackHQ 📱 Socials Twitter: https://twitter.com/betterstackhq Instagram: https://www.instagram.com/betterstackhq/ TikTok: https://www.tiktok.com/@betterstack LinkedIn: https://www.linkedin.com/company/betterstack 📌 Chapters: 0:00 - Intro 0:30 - The Tracking Script 1:23 - Testing 8 AI Models 2:16 - The Researcher's Results 2:49 - What the Script Does 3:17 - Not the First Time 4:07 - Defenders Use It Too 5:13 - Hugging Face Got Blocked 5:52 - My Take Sources (numbered as on screen) [1] veritas, "Why Is This Fingerprinting Script Creating Bioweapons?", nullpt.rs, 28 Oct 2026: https://nullpt.rs/fingerprinting-bioweapons [2] Our own test: eight AI agents in OpenCode (via OpenRouter and OpenCode Go) asked to deobfuscate the same script, 31 Oct 2026. One run per model. [3] OpenAI, "Use Daybreak in the Responses API": https://developers.openai.com/api/docs/guides/daybreak [4] Hacker News discussion, 28–29 Oct 2026: https://news.ycombinator.com/item?id=50276998 (comment: https://news.ycombinator.com/item?id=50286599) [5] Check Point Research, "In the Wild: Malware Prototype with Embedded Prompt Injection", 25 Jun 2025: https://research.checkpoint.com/2025/ai-evasion-prompt-injection/ [6] Socket, "Mini Shai-Hulud, Miasma, and Hades Worms Target Bioinformatics and MCP Developers via Malicious PyPI Wheels", 8 Jun 2026: https://socket.dev/blog/mini-shai-hulud-miasma-and-hades-worms-target-bioinformatics-and-mcp-developers-via-malicious [7] Tracebit, "Context Bombs: stopping AI attackers in their tracks", working paper, Jul 2026: https://agentic.tracebit.com/context-bombs (repo: https://github.com/tracebit-com/context-bombs) [8] @_brucedh on X, 29 Oct 2026: https://x.com/_brucedh/status/2115766351792910570 [9] Hugging Face, "Security incident disclosure — July 2026", 16 Jul 2026: https://huggingface.co/blog/security-incident-july-2026 [10] OpenAI, "OpenAI and Hugging Face partner to address security incident during model evaluation", 21 Jul 2026: https://openai.com/index/hugging-face-model-evaluation-security-incident [11] OpenAI, "Cybersecurity checks": https://developers.openai.com/api/docs/guides/safety-checks/cybersecurity
