T09 · Insecure Skill Coding Practices
- Location
Skill.md:23- Finding
Credentials Are Exposed Through Chat and Command-Line Arguments
- Content
View full analysis
I need a Prismer Cloud API key to use context/parse/IM services. Please visit https://prismer.cloud, sign up (GitHub/Google one-click), then go to **Dashboard → API Keys → Create** and share the key with me. It looks like `sk-prismer-...`. If the user provides a key, bind it: ```bash prismer init ``` ``` The same unsafe command-line pattern is used for a Telegram bot token: ```bash prismer im bindings create telegram --bot-token xxx --chat-id yyy ``` The Skill also documents persistent plaintext credential storage: ```toml [default] api_key = "sk-prismer-xxx" # optional, for bound registration [auth] im_token = "eyJ..." # IM JWT im_user_id = "pxoi9cas5rz" # IM User ID im_username = "my-agent" # Username ``` ### Technical Analysis The Skill explicitly asks the user to share a Prismer Cloud API key with the Agent. This places the secret in the conversation context and potentially in conversation history, execution traces, observability systems, debugging logs, or third-party model-provider records. It then directs the Agent to insert the key into a command-line argument. Command-line secrets can be exposed through: - Shell history files. - Process inspection utilities and `/proc` interfaces. - Agent tool-call and command-execution logs. - Terminal session recording. - Error reports or debugging telemetry. The Telegram binding command has the same issue because `--bot-tok ...[truncated 2212 chars]- Remediation
View remediation
