Credential access and network transmission in one file
Expected behavior · high confidence
This plugin reads the API key you already saved in SillyTavern and sends it to the API endpoint you configured, so it can make requests on your behalf. That is exactly what the plugin says it does and is normal behavior for an API adapter.
Technical evidence
Scanner reason: A credential source and an outbound network operation were detected in the same file.
Contextual assessment: The file retrieves a stored Custom API key via SillyTavern's secret management and sends it as the standard Anthropic x-api-key header to an endpoint derived from the user-supplied custom_url. This matches the project's stated purpose: an optional server plugin that proxies eligible Claude requests through Navy's Anthropic-compatible endpoint using the user's own stored Custom API key. The key is not persisted elsewhere, not logged, and only transmitted to the user-configured endpoint for the legitimate request. The credential source and network sink coexist because the adapter's function is to forward authenticated API calls.
Impact: none · Exploitability: unlikely
Developer action: none
- Scanner
- tavernkeeper 3
- Rule
- credential-exfiltration
- File role
- production
- Source
- server-plugin/index.mjs:157