Menu

1 / 4

Leaked API Keys in LLMs: How AI Agents Expose Secrets

DEV Community: devsecops·Dwayne McDaniel·about 16 hours ago
#mjAOdbRg
#devtodevsecops#devto#dev#secrets#credentials
Reading 0:00
15s threshold

TL;DR

LLMs can reproduce real leaked keys : Using only API output access, researchers recovered DeepSeek and Google keys from Qwen3-27B, GPT-Codex 5.3, and Claude Haiku 4.5, and every key had a matching public GitHub occurrence.

Agents pull secrets in from the laptop : Developer endpoints hold credentials in .env files, shell history, and MCP configs that never reach Git. Claude Code-assisted commits leaked secrets at 3.2%, versus a 1.5% baseline.

Stop secrets before the model sees them : AI Hooks block secrets in prompts, tool calls, and output, while Developer Endpoint Protection reduces the plaintext credentials on managed fleets that agents can find.

More AI, more places to leak secrets

More and more teams are adopting AI agents, allowing them to create new tools, apps, and software at unprecedented speed.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.