Arena technique · ROT13
Can ROT13 hide API keys from a PII filter?
ROT13 shifts every letter 13 places, so sk_ becomes fx_. A plain pattern looks for the real prefix and misses it. The AI Node turns it back first.
Tested by the encoder against a copy of the current AI Node, with fake keys only. See the full coverage board.
Every secret type, hidden with ROT13
| Secret | Vrymdor AI Node | Basic regex |
|---|---|---|
| Private key | Blocked | Missed |
| JWT sign-in token | Blocked | Missed |
| Vrymdor access token | Blocked | Missed |
| Bearer token | Blocked | Missed |
| Anthropic key | Blocked | Missed |
| OpenAI key | Blocked | Missed |
| Stripe key | Blocked | Missed |
| GitHub token | Blocked | Missed |
| AWS key | Blocked | Missed |
| Google key | Blocked | Missed |
| Slack token | Blocked | Missed |
The latest attempt
No published attempt yet
The latest attempt for ROT13 shows here after the next published Rival Run.
Compared with a basic regex filter
From 11 stored attempts hidden with ROT13. The basic regex result is computed on the same attempts.
- Vrymdor AI Node
- 11 of 11 blocked
- A basic regex filter
- 0 of 11 caught
Put the tested version in your workflow
The same AI Node the Rivals attack runs in your n8n workflow or over the API.
Free scanner: Paste your n8n workflow and see what it leaks today.