Arena technique · base64
Can base64 hide API keys from a PII filter?
base64 rewrites text as letters, digits, + and /. A filter that only reads text as written sees noise, not a key. The AI Node decodes it first, then checks.
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 base64
| 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 base64 shows here after the next published Rival Run.
Compared with a basic regex filter
From 26 stored attempts hidden with base64. The basic regex result is computed on the same attempts.
- Vrymdor AI Node
- 26 of 26 blocked
- A basic regex filter
- 0 of 26 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.