Arena technique · hex
Can hex hide API keys from a PII filter?
Hex writes every character as two digits from 0 to 9 and a to f. The key is still all there, just not in a shape a plain pattern knows. The AI Node decodes it 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 hex
| 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 hex shows here after the next published Rival Run.
Compared with a basic regex filter
From 15 stored attempts hidden with hex. The basic regex result is computed on the same attempts.
- Vrymdor AI Node
- 15 of 15 blocked
- A basic regex filter
- 0 of 15 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.