Topic starter
24/06/2026 7:11 pm
TL;DR: Predictable assistant files can hold OAuth tokens, API keys, and MCP credentials in plaintext JSON, and Netwrix links that storage pattern to easy theft paths. Assistant-held secrets need tighter scope and inventory because one readable file can unlock multiple services and sessions.
Editorial analysis by NHI Mgmt Group, based on content published by Netwrix: “Your AI coding assistant is leaking secrets”.
Key questions
A: Plaintext administrator credentials collapse the boundary between initial access and full environment control.
Q: What are the signs that AI assistant secret storage is misconfigured?
A: Look for inline tokens in JSON, synced extension settings, world-readable files in WSL, and any assistant profile that stores multiple service credentials together.
Q: What breaks when AI coding assistants store secrets in predictable local files?
A: Predictable file paths turn credential storage into a discoverable attack surface.
Practitioner guidance
- Audit assistant credential paths Inventory every AI desktop assistant, coding tool, and CLI that stores tokens in home-directory files, extension stores, or synced config paths.
- Replace plaintext token storage Move OAuth tokens, API keys, and MCP secrets out of plaintext JSON and into OS keychains or runtime credential helpers wherever the tool supports it.
- Reduce MCP credential aggregation Split multi-service MCP configs so one file does not carry GitHub, Slack, database, and cloud credentials together.
Bottom line: AI coding assistants are turning everyday developer workflows into secret distribution channels when tokens live in predictable local files and synced configs.
Glossary terms: Credential Aggregation, Persistent Token, Remote control session, Secrets Sprawl
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 21 hours ago by NHI Mgmt Group
25/06/2026 4:22 am
Predictable secret paths create identity exposure, not just storage exposure. When credentials live in known JSON files, the security boundary shifts from authentication to file discovery. That means local OS permissions and sync behaviour become identity controls, which is a poor fit for secrets that can authenticate to multiple external services. The practitioner conclusion is that file location is part of the trust model.
A question worth separating out:
Q: Should organisations treat AI assistant credentials as NHI assets?
A: Yes. Assistant-stored tokens behave like non-human identities because they authenticate to external services, persist across sessions, and often outlive the user action that created them. Governance should cover inventory, scope, storage, rotation, and revocation, because the exposure pattern is identity-driven rather than purely endpoint-driven.
👉 Read our full editorial: AI coding assistants are leaking credentials across predictable file paths