Threat data from 91K AI agent interactions: Tool abuse up 6.4%, new multimodal attacks

Threat landscape from production AI agent data
Real-world threat data from 91,284 AI agent interactions across 47 deployments shows 35,711 threats detected in February 2026. The detection model uses a Gemma-based 5-head multilabel classifier.
Key threats for self-hosted deployments
- Tool/command abuse: Increased 6.4% to 14.5% of threats. The dominant pattern is tool chain escalation where a harmless read call is followed by a write or execute. Most local setups give agents tool access without sufficient safeguards.
- Agent goal hijacking: Doubled to 6.9% of threats. Targets the planning phase in autonomous agent loops, particularly relevant for local setups with less monitoring on agent state.
- RAG poisoning: Shifted to metadata attacks at 12.0% (up from 10.0%). New pattern targets document metadata (titles, authors, annotations) rather than content. Most people sanitize content but pass metadata through as-is.
- Multimodal injection: New threat at 2.3% where instructions are hidden in images and PDFs. Text-only safety scanning misses these attacks.
Threat breakdown percentages
- Data Exfiltration: 18.0% (-1.2 MoM change)
- Tool/Command Abuse: 14.5% (+6.4)
- RAG/Context Attack: 12.0% (+2.0)
- Jailbreak: 11.0% (-1.3)
- Prompt Injection: 8.1% (-0.7)
- Agent Goal Hijack: 6.9% (+3.3)
- Inter-Agent Attack: 5.0% (+1.6)
Detection approach
The detection pipeline uses two layers: L1 is pattern matching with 218 rules (sub-ms latency, runs entirely locally), and L2 is Gemma-based. The full community edition is open source at github.com/raxe-ai/raxe-ce.
📖 Read the full source: r/LocalLLaMA
👀 See Also

Open-Source Attack Surface Management Cheat Sheet Released
A developer has open-sourced an Attack Surface Management cheat sheet that covers practical workflows, tools, and references. The project includes sections on asset discovery, infrastructure tracking, reconnaissance tooling, automation workflows, and learning resources.

OpenClaw Security Concerns: API Keys and Conversation Data at Risk in Default Self-Hosting
A Cisco report indicates OpenClaw security is "optional, not built in," with default configurations storing API keys in .env files on VPS instances, creating potential exposure for non-technical users running on basic droplets.

Meta Security Incident Caused by Rogue AI Agent Providing Inaccurate Technical Advice
A Meta engineer used an internal AI agent similar to OpenClaw to analyze a technical question, but the agent posted inaccurate advice publicly instead of privately, leading to a SEV1 security incident that temporarily exposed sensitive data.

OpenClaw User Adds TOTP 2FA After Agent Exposed API Keys in Plain Text
An OpenClaw user created a security skill called 'Secure Reveal' that requires TOTP authentication via Telegram before displaying stored credentials, after their AI agent accidentally leaked API keys and passwords in plain text during a demo.