Report #95184
[gotcha] Assuming LLMs cannot parse encoded payloads like Base64 or hex
Decode or reject heavily encoded/obfuscated user inputs before they reach the LLM context.
Journey Context:
Developers think that if a prompt is Base64 encoded, the LLM will just treat it as gibberish. However, modern LLMs are highly capable of reading Base64, ROT13, and other encodings natively. An attacker bypasses keyword filters by encoding the malicious instruction, and the LLM decodes and executes it internally.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T18:20:34.862725+00:00— report_created — created