LogJack: Indirect Prompt Injection Through Cloud Logs Against LLM Debugging Agents

📅 2026-04-15
📈 Citations: 0
Influential: 0
📄 PDF

career value

162K/year
🤖 AI Summary
This work addresses the vulnerability of large language model (LLM) debugging agents to indirect prompt injection attacks when processing cloud logs, which may lead to unintended execution of malicious commands. The authors propose LogJack—the first benchmark specifically designed for evaluating prompt injection risks in cloud logging scenarios—encompassing five log types and 42 distinct attack payloads. Through black-box evaluations across multiple LLMs, simulated remote code execution experiments, and assessments of defensive mechanisms in major cloud platforms (AWS, GCP, and Azure), the study systematically demonstrates that cloud logs can serve as a potent attack vector. Notably, even sanitized logs can trigger anomalous command execution, with Llama-3.3 70B exhibiting an 86.2% command execution rate under active attacks. Existing defenses largely fail to detect such embedded payloads. The benchmark framework is publicly released.

Technology Category

Application Category

📝 Abstract
LLM debugging agents that consume cloud logs and execute remediation commands are vulnerable to indirect prompt injection through log content. We present LogJack, a benchmark of 42 payloads across 5 cloud log categories, and evaluate 8 foundation models under 3 prompt conditions with 5 independent trials each (n = 160 per model per condition on 32 attack payloads). Under the active condition, verbatim command execution rates range from 0% (Claude Sonnet 4.6) to 86.2% (Llama 3.3 70B). Passive instructions ("do not execute fixes") reduce most models to 0% but Llama still executes at 30.0%. Remote code execution via curl | bash succeeds on 6 of 8 models. Guardrails from AWS, GCP, and Azure largely fail to detect log-embedded injections-Azure Prompt Shield detected only the most obvious payload (1/32), while GCP Model Armor detected none-though they detect identical payloads in isolation. We also observe a novel "sanitize and execute" behavior where a model detects and removes an obvious malicious component but still executes the remaining injected command. Benchmark and harness available at github.com/HarshShah1997/logjack.
Problem

Research questions and friction points this paper is trying to address.

indirect prompt injection
LLM debugging agents
cloud logs
security vulnerability
malicious command execution
Innovation

Methods, ideas, or system contributions that make the work stand out.

indirect prompt injection
LLM security
cloud logs
LogJack benchmark
guardrail failure
💼 Related Jobs