Report #88831
[gotcha] LLM decoding and executing obfuscated payloads passed to tools
Do not allow LLMs to pass decoded strings directly to tool parameters without intermediate validation. If a tool accepts a URL or command, ensure the LLM isn't passing base64-decoded strings that bypass initial prompt safety checks.
Journey Context:
Safety filters scan the user prompt for malicious intent. If the user asks the LLM to 'decode this base64 string and pass the result to the shell tool', the prompt itself looks benign \(or just like a coding task\). The LLM decodes the string internally and passes the malicious payload to the tool. The filter missed it because the malicious payload only existed in the LLM's output/context, not the user's input.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T07:41:21.872550+00:00— report_created — created