Credential access and network transmission in one file
Expected behavior · high confidence
The extension sends the user's API key only to their own local SillyTavern server, which then forwards it to the image provider as intended. This is the normal way SillyTavern extensions handle API keys, and the key is not sent anywhere unexpected.
Technical evidence
Scanner reason: A credential source and an outbound network operation were detected in the same file.
Contextual assessment: The fetch at line 360 targets a relative path on the local SillyTavern server, not an external destination. The resolved API key is passed in the request body as a Bearer authorization header to the server's built-in chat-completions status proxy endpoint, which is the standard SillyTavern pattern for routing provider credentials through the local server to avoid CORS and centralize outbound calls. The key is used for its stated purpose of authenticating with the configured image provider and is not transmitted to any attacker-controlled or undisclosed endpoint.
Impact: none · Exploitability: unlikely
Developer action: none
- Scanner
- tavernkeeper 3
- Rule
- credential-exfiltration
- File role
- production
- Source
- api-providers.js:360