T09 · Insecure Skill Coding Practices
- Location
SKILL.md:17- Finding
Disclosure of Sensitive Credentials Through a Third-Party GET Query
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 17-23
Vulnerability Type: Sensitive data exposure through URL query parameters
Risk Level: HighVulnerable Code
markdown Required arg: email, username, or password. Append `?query=` with the supplied email, username, or password. Simple request: ```bash curl 'https://api.proxynova.com/comb?query=jrubin'Technical Analysis
The Skill explicitly permits a raw password to be supplied as the API query and instructs the Agent to place that value in a GET URL parameter. Executing the documented command transmits the sensitive value to the external service
api.proxynova.com.URLs are commonly recorded by API access logs, reverse proxies, network-monitoring systems, security telemetry, command transcripts, and shell history. Consequently, using a password in the
queryparameter creates more exposure than transmitting sensitive data through a properly protected and non-logged request body. HTTPS protects the request in transit but does not prevent the destination service or endpoint infrastructure from recording the URL.The API response also contains plaintext leaked credential pairs, as demonstrated later in the document. If the Agent returns those records without redaction, the credentials can persist in conversation histories and downstream logs.
Attack Path
- A user or attacker persuades an operator to invoke the Skill with a current or reused password as the required argument.
- The Agent follows the Skill instructions and constructs a URL such as
https://api.proxynova.com/comb?query=<password>. curltransmits the raw password to the third-party ProxyNova service.- The password may be retained in service access logs, proxy logs, monitoring telemetry, shell history, or Agent execution records.
- Anyone with access to those records may recover the password.
- If the password is valid or reused, it may be tested against associated services, potenti ...[truncated 865 chars]
- Remediation
View remediation
Remediation Suggestions
- Prohibit passwords, authentication tokens, API keys, and other secrets as search inputs.
- Restrict queries to non-secret identifiers, such as an email address, and only process identifiers the requester is authorized to investigate.
- Clearly disclose that query data will be transmitted to ProxyNova and require explicit user consent before making the request.
- Prefer a vetted breach-checking service that supports privacy-preserving mechanisms, such as partial-hash or k-anonymity queries, so raw passwords are never disclosed.
- Do not include sensitive values in URL query parameters. If sensitive identifiers must be transmitted, use an appropriately protected request body and enforce redaction and no-log controls, while recognizing that raw passwords should still never be sent.
- Redact passwords from API responses before displaying, storing, or forwarding results. For example, return only the affected identifier, breach status, and remediation guidance.
- Disable command echoing and ensure shell history, Agent traces, HTTP diagnostics, and telemetry cannot retain sensitive request or response data.
- Add input validation that rejects password-like secrets and displays guidance to rotate any password already submitted.
- Document acceptable-use and authorization requirements to reduce the risk of credential harvesting or unauthorized account targeting.
