lolcreds

Public credential defaults and exposure patterns for authorized security testing.

Visual Studio Code AI Extensions

MicrosoftAI API3 credentials

Credentials3 documented
01

AI Extension Provider API Key

vscode-ai-extensions / extension-provider-api-key

VS Code AI extensions commonly use provider API keys supplied through environment variables, workspace settings, extension settings, devcontainers, or SecretStorage.

user definedsecretAPI key

Looks like

example
example

OpenAI key used by VS Code AI extensions

sk-proj-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
example

Anthropic key used by VS Code AI extensions

«redacted:sk-…»
example

Google API key used by Gemini extensions

«redacted:AIza…»

Location

environment
OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY, GEMINI_API_KEY, GOOGLE_GENERATIVE_AI_API_KEY, AZURE_OPENAI_API_KEY, OPENROUTER_API_KEY
config file
~/.config/Code/User/settings.json, ~/.config/Code/User/globalStorage/state.vscdb, ~/.config/Code - Insiders/User/settings.json, ~/.config/Code - Insiders/User/globalStorage/state.vscdb

VS Code user settings and extension SecretStorage metadata/blobs on Unix-like systems

config file
%APPDATA%\Code\User\settings.json, %APPDATA%\Code\User\globalStorage\state.vscdb, %APPDATA%\Code - Insiders\User\settings.json, %APPDATA%\Code - Insiders\User\globalStorage\state.vscdb

VS Code user settings and extension SecretStorage metadata/blobs on Windows

config file
.vscode/settings.json, .vscode/mcp.json, mcp.json, .env, .env.local, .env.production, devcontainer.json, .devcontainer/devcontainer.json, docker-compose.yml, compose.yml

Workspace settings, MCP files, env files, and development container configuration used by AI extensions

secret store

VS Code SecretStorage, OS keychain, password vaults, GitHub/Codespaces secrets, Docker secrets, Kubernetes Secrets, and cloud secret managers

source code

Extension settings examples, notebooks, scripts, test fixtures, tool configs, MCP server definitions, and prompt/agent files

logs

Extension host logs, AI extension output channels, terminal transcripts, MCP server stdout/stderr, CI traces, and debug dumps

Notes

VS Code SecretStorage generally stores secrets through OS keychain-backed encrypted storage; state.vscdb is an exact extension storage surface but not guaranteed plaintext.

02

GitHub Copilot Token

vscode-ai-extensions / copilot-token

Built-in and marketplace Copilot integrations use GitHub/Copilot tokens, including environment variables passed to integrated terminals or automation.

generated on installgenerated on installuser definedsecrettoken

Location

environment
COPILOT_GITHUB_TOKEN, GITHUB_COPILOT_GITHUB_TOKEN, GH_TOKEN, GITHUB_TOKEN
config file
~/.config/Code/User/globalStorage/state.vscdb, ~/.config/Code/User/settings.json
config file
%APPDATA%\Code\User\globalStorage\state.vscdb, %APPDATA%\Code\User\settings.json
config file
.vscode/settings.json, .github/workflows/copilot-setup-steps.yml, .devcontainer/devcontainer.json, devcontainer.json
secret store

VS Code SecretStorage, OS keychain, GitHub Actions secrets, Codespaces secrets, and enterprise secret stores

logs

Copilot Chat logs, extension host logs, coding-agent logs, and terminal traces

Notes

GitHub token value shapes are intentionally modeled in github.yaml. This VS Code entry keeps editor/Copilot storage and environment context only so it does not override canonical GitHub token classification.

03

MCP Server Secret

vscode-ai-extensions / mcp-server-secret

VS Code MCP and AI-agent extensions can invoke local or remote MCP servers with API keys and OAuth tokens in configuration or command environments.

user definedgenerated on installsecretsecret value

Location

config file
.vscode/mcp.json, mcp.json, .vscode/settings.json, settings.json, .env, .env.local
environment
OPENAI_API_KEY, ANTHROPIC_API_KEY, GITHUB_TOKEN, GH_TOKEN
secret store

VS Code SecretStorage, OS keychain, password vaults, and cloud secret managers used by MCP servers

source code

MCP server command wrappers, extension configs, and workspace automation

logs

MCP server logs, extension output channels, terminal transcripts, and debug traces

Notes

MCP credential formats vary by server; scanner value patterns should come from the specific provider or server template where possible.

Scope

Authorized use

LOLCreds helps map the credential surface of real products: known defaults, generated values, credential locations, and exposure patterns.