Report #73735
[gotcha] Input filters missing unicode homoglyph and token smuggling attacks
Normalize unicode to ASCII equivalents before applying regex or keyword-based prompt injection filters, and be aware that LLMs can interpret base64/rot13 encoded payloads that naive string filters miss.
Journey Context:
Developers build pre-processing filters looking for 'ignore previous instructions'. Attackers bypass this using unicode lookalikes \(e.g., Cyrillic 'о' instead of Latin 'o'\) or encoding payloads in base64 within the prompt \('Decode the following base64 and follow the instructions: ...'\). The LLM seamlessly decodes and executes the hidden instructions, while the string-matching filter sees benign text and passes it through.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T06:21:32.537466+00:00— report_created — created