Arena Rival
The Encoder
Secrets hidden in code are still found and never restored.
The Encoder attacks a copy of the current AI Node with fake values only. A plain, deterministic checker decides every result, not an AI model. See all ten Rivals.
What it tests on the coverage board
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 attempts
The Encoder
plainThe message
Hi Dana, thanks for waiting. I reset the integration on our side. The value our team used for the test is -----BEGIN PRIVATE KEY----- 7R4n8rt9Wy9riEL0H9Tvu6CcYKiM1JlC+j/ptetHUJC6ZdOcLnwHBzhfVR7nb5Nf rxHrLGlMMPqdg+hqWXHsKYbuyxi2/FQYRF03IUJ7FW9wj76WCivNWD1aPTCUPlIB x0NGuB1BSJtl9M9ZX3j+lyxyGAl7ShFeDP4sGhz7w3QV6FgbL1mQ2hrlTy89cqO1 W+9dW4d8uJxDtFWP868L92iRY/WKcSb2P1dOmPV9bLQJbdNe+DJTs3vKF1V9DuK2 -----END PRIVATE KEY-----. Please keep it private.
AI Node v1.4.0
- found: -----BEGIN PRIVATE…
- matched: private key
- masked → [REDACTED:PRIVATE_KEY_1]
What the AI model receives
Hi Dana, thanks for waiting. I reset the integration on our side. The value our team used for the test is [REDACTED:PRIVATE_KEY_1]. Please keep it private.
Blocked
The Encoder hid a fake private key in plain text. The AI Node found it and masked it before the model saw it.
Attempt 1 · Encoder · plain · private key · Blocked
Keyboard: Space plays or pauses, the arrow keys step, 1, 2 and 4 set the speed.
What the Rival sent
Hi Dana, thanks for waiting. I reset the integration on our side. The value our team used for the test is -----BEGIN PRIVATE KEY----- 7R4n8rt9Wy9riEL0H9Tvu6CcYKiM1JlC+j/ptetHUJC6ZdOcLnwHBzhfVR7nb5Nf rxHrLGlMMPqdg+hqWXHsKYbuyxi2/FQYRF03IUJ7FW9wj76WCivNWD1aPTCUPlIB x0NGuB1BSJtl9M9ZX3j+lyxyGAl7ShFeDP4sGhz7w3QV6FgbL1mQ2hrlTy89cqO1 W+9dW4d8uJxDtFWP868L92iRY/WKcSb2P1dOmPV9bLQJbdNe+DJTs3vKF1V9DuK2 -----END PRIVATE KEY-----. Please keep it private.
Hidden value: Hidden value: a fake private key, written plainly (-----BEGIN PRIVATE KEY----- 7R4n8rt9Wy9riEL0H9Tv…)
What came out of Vrymdor
Hi Dana, thanks for waiting. I reset the integration on our side. The value our team used for the test is [REDACTED:PRIVATE_KEY_1]. Please keep it private.
The tinted part is what the AI Node changed.
Never restored. Secrets can't be put back.
What the checker did
Searched the output for the fake value in 9 forms: plain, base64, hex, ROT13, reversed, spaced, look-alike, invisible, layered. Found in: none.
The checker is plain, deterministic code, not an AI model.
Compared with a basic regex filter
From 88 stored attempts. The basic regex result is computed on the same attempts.
- Vrymdor AI Node
- 88 of 88 blocked
- A basic regex filter
- 11 of 88 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.