Generative AI Security: Are Your Developers Pasting Secrets Into LLMs?

GitGuardian reports that leaked secrets associated with AI services rose to more than 1.27 million in 2025, an 81% annual increase, with AI-assisted code exposing credentials at roughly twice the general GitHub rate. The post argues that prompts, tool calls, and agent workflows form an under-monitored channel because developers and automated agents may send commands, environment files, configuration data, or full files directly to third-party model providers without creating a repository artifact that can later be scanned. It recommends combining developer-side AI Hooks, which can block secrets close to their origin, with centrally managed AI gateways or LLM proxies that inspect all traffic crossing to providers, including shadow AI and automated workloads. Through GitGuardian’s Bring Your Own Source Custom Source integration, a gateway can submit payloads for in-memory scanning by more than 600 detectors, generate dashboard incidents without storing content, and either allow requests while recording findings or block them before reaching the provider. The suggested deployment approach is to begin in non-blocking mode for about two weeks to measure exposure and validate findings, then enable blocking, while recognizing that routing all model traffic through a gateway requires broader network and endpoint enforcement and provides coverage rather than complete containment.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.