T09 · Insecure Skill Coding Practices
- Location
SKILL.md:268- Finding
Remote Password Disclosure Through a URL Query Parameter
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:268
Vulnerability Type: Plaintext sensitive-data transmission to a third-party API
Risk Level: HighVulnerable Code
bash curl -s "https://60s.viki.moe/v2/password/check?password=abc123" # Password strength checkThe endpoint is also documented in the API reference at
SKILL.md:348:markdown | /v2/password/check | GET | password | Password strength check |Technical Analysis
The Skill directs the Agent to send a password to the remote
60s.viki.moeservice in a GET query parameter. Although HTTPS protects the request while it is in transit, it does not prevent the complete URL from being recorded by the remote server, reverse proxies, observability systems, diagnostic tooling, or other infrastructure with access to request metadata.Invoking the example through a shell also risks exposing the password through command history, process inspection, execution traces, or Agent/tool logs. Sending a credential to an external service is unnecessary for password-strength analysis because policy, pattern, and entropy checks can be performed locally.
This behavior exceeds least privilege: the declared operation only requires evaluating password strength, but the implementation discloses the password to a third party.
Attack Path
- A user asks the Agent to assess the strength of an actual password.
- Following the Skill documentation, the Agent constructs a request to
/v2/password/check. - The plaintext password is inserted into the URL's
passwordquery parameter. - The Agent invokes the request through
curland the execution tool. - The URL may be retained in local command or tool logs and in remote API, proxy, monitoring, or diagnostic logs.
- An attacker or unauthorized operator with access to any retained log obtains the password.
- If the user reused the password, the exposed credential may be tested against oth ...[truncated 514 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the remote password-strength endpoint and its example from the Skill instructions and API reference.
- Perform password-strength evaluation locally using length, character diversity, repetition, common-pattern, dictionary, and estimated-entropy checks.
- Explicitly instruct the Agent never to submit passwords, API keys, tokens, or other secrets to third-party services.
- Never place sensitive data in URL query parameters. If a remote operation is unavoidable, require explicit informed user consent and use a vetted service with a documented privacy policy and a request body, while recognizing that this still discloses the secret to that service.
- Prevent secret-bearing commands and request bodies from entering shell history, process listings, Agent traces, telemetry, and debug logs.
- Add a warning that users should not provide real credentials and that any sample must use an obviously synthetic value.
- Add automated linting or policy checks that reject Skill instructions containing credential-like parameters in URLs.
