Arena technique · Plain
Does a PII filter catch an API key pasted as it is?
The key is pasted as it is. Any filter should catch this, so it is the baseline every other column is measured against.
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 Plain
| Secret | Vrymdor AI Node | Basic regex |
|---|---|---|
| Private key | Blocked | Caught |
| JWT sign-in token | Blocked | Caught |
| Vrymdor access token | Blocked | Caught |
| Bearer token | Blocked | Caught |
| Anthropic key | Blocked | Caught |
| OpenAI key | Blocked | Caught |
| Stripe key | Blocked | Caught |
| GitHub token | Blocked | Caught |
| AWS key | Blocked | Caught |
| Google key | Blocked | Caught |
| Slack token | Blocked | Caught |
The latest attempt
No published attempt yet
The latest attempt for Plain shows here after the next published Rival Run.
Compared with a basic regex filter
From 11 stored attempts hidden with Plain. The basic regex result is computed on the same attempts.
- Vrymdor AI Node
- 11 of 11 blocked
- A basic regex filter
- 11 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.