Secrets leak in plaintext through agent reads, MCP configs, chat history and hijacked package installs — with nothing gating the access
Use this brief as evidence in a free GTM Coach skill for Cursor, Claude Code, and other AI agents— sign in to install.
Summary
Sensitive credentials are sitting in plaintext everywhere an agent runs: .env files, ~/.npmrc, ~/.aws/credentials, MCP configs (mcp.json), and even the agent's own SQLite chat history — one user's scan found 45 secrets, 12 of them inside Cursor's own files. Worse, the scan itself leaked secret values into the stored chat log because nothing gates the read. On top of that, supply-chain attacks exploit the same gap: a hijacked Microsoft agent-framework PyPI package dropped .pth hooks that triggered a credential stealer on every interpreter startup, harvesting .env, .netrc, .git-credentials and minting live cloud/OIDC tokens — all with zero interception, because installs run unpinned and unapproved with unrestricted egress. Developers are left manually rotating keys after the fact and told to 'run gitleaks and check mcp.json' — reactive advice, not a solution. No local runtime gate exists to pause or block an agent reading secrets or installing a package before the exfiltration happens, making this a severe, high-value, still-unsolved problem.
Reddit context (brief)
Short excerpts derived from discussions—open the source links for full threads.
Agents read secrets in plaintext from .env, mcp.json and chat history, and even a security scan leaks secret values into stored agent logs because nothing gates the read.
Agent package installs run unvetted and unapproved, letting a hijacked PyPI package harvest .env files and cloud credentials with zero interception.
Free AI-agent skill · no Premium
Use as evidence: Secrets leak in plaintext through agent reads, MCP configs, chat history and hij
Get the skill in a few minutes
Sign in free
Create a Nichestarter account with Google or email. No credit card. Premium is optional.
Open Projects and issue a key
After sign-in, create or confirm a project, then copy the GTM Coach bind key. Binding is free.
Paste the skill and the key in your AI agent
Paste the SKILL.md prompt plus the project key in Cursor, Claude Code, Codex, or WorkBuddy. Coaching starts after the key verifies. The plan stays in .gtm/.
The Coach plans and drafts; you publish, send, and spend. AI-agent setup guide · Pricing.
Related angle: Secrets leak in plaintext through agent reads, MCP configs, chat history and hijacked package installs — with nothing gating the access
Context: r/cursor
Get started in a few minutes
Install NicheReach
Add the free Chrome extension from the Web Store.
Sign in with Nichestarter
Use the same Google or email account—no separate NicheReach signup.
Confirm your product
Paste your site so NicheReach knows who you help and where they talk.
Draft, then you post
Open a matching thread, generate an account-safe reply, edit it, and click Comment yourself.
Safety first: NicheReach never posts for you. Limits: pricing.