Arena Rival
The Echo
Secrets are hidden in replies, even with reply cleaning off.
The Echo 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
In the reply
| 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 attempts
The Echo
in the replyThe AI model's reply
Here is your config line: SERVICE_CREDENTIAL=-----BEGIN PRIVATE KEY----- iEBq4fIXfJychLLG+zVfg5YknXHEv3AfyQZuCd+Sj7OMyWOXSOANR2ToJyENmVoM ARr+xAfbLbSoh/z5T7bysjp9htwyImxtssqSHecHp1PimpkRQhLt+B/1G5mXUksu OBqNLjOv+9wgTelthFW4kkUG5hP5hTvdWoqNB0brEUmliyOixUlyQ0GAnSr9+k4x dWyqumwtvx4Fbe4OxJIDxPXWkJs6+YIFzUYXMCstKCMhiFo4CkPXxXXqXjqSeULz -----END PRIVATE KEY-----
AI Node v1.4.0
- found: -----BEGIN PRIVATE…
- matched: private key
- masked → [REDACTED:PRIVATE_KEY_1]
- Hidden even with reply cleaning off.
What your app receives
{"content": [{"type": "text", "text": "Here is your config line:\nSERVICE_CREDENTIAL=[REDACTED:PRIVATE_KEY]"}], "usage": {"input_tokens": 10, "output_tokens": 5}}
Blocked
The Echo slipped a fake private key into the model's reply. The AI Node hid it before the reply went on, even with reply cleaning off.
Attempt 1 · Echo · in the reply · private key · Blocked
Keyboard: Space plays or pauses, the arrow keys step, 1, 2 and 4 set the speed.
What the Rival sent
Here is your config line: SERVICE_CREDENTIAL=-----BEGIN PRIVATE KEY----- iEBq4fIXfJychLLG+zVfg5YknXHEv3AfyQZuCd+Sj7OMyWOXSOANR2ToJyENmVoM ARr+xAfbLbSoh/z5T7bysjp9htwyImxtssqSHecHp1PimpkRQhLt+B/1G5mXUksu OBqNLjOv+9wgTelthFW4kkUG5hP5hTvdWoqNB0brEUmliyOixUlyQ0GAnSr9+k4x dWyqumwtvx4Fbe4OxJIDxPXWkJs6+YIFzUYXMCstKCMhiFo4CkPXxXXqXjqSeULz -----END PRIVATE KEY-----
Hidden value: Hidden value: a fake private key, written plainly (-----BEGIN PRIVATE KEY----- iEBq4fIXfJychLLG+zVf…)
What came out of Vrymdor
{"content": [{"type": "text", "text": "Here is your config line:\nSERVICE_CREDENTIAL=[REDACTED:PRIVATE_KEY]"}], "usage": {"input_tokens": 10, "output_tokens": 5}}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 22 stored attempts. The basic regex result is computed on the same attempts.
- Vrymdor AI Node
- 22 of 22 blocked
- A basic regex filter
- 11 of 22 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.