T09 · Insecure Skill Coding Practices
- Location
ids_admin_login.md:20- Finding
Publicly Exposed Static Signing Constants and Weak MD5 Request Signatures
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only APM authentication API skill, but it handles administrator/user credentials and reusable tokens without enough guardrails for such sensitive access.
Install only if you trust the APM service and intend to let an agent work with these authentication endpoints. Use authorized accounts only, do not log or persist passwords, verification codes, access tokens, or refresh tokens, avoid long-lived exported environment variables for APM_USER_TOKEN, and review the weak MD5/static-salt signing design with the service owner before relying on it for security-sensitive workflows.
ids_admin_login.md:20Publicly Exposed Static Signing Constants and Weak MD5 Request Signatures
SKILL.md:49Insufficient Protection Guidance for Passwords and Reusable Authentication Tokens
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The documentation instructs users to store an access token in the APM_USER_TOKEN environment variable without warning that tokens are sensitive secrets that may be exposed through shell history, process inspection, logs, CI output, or inherited subprocess environments. In a skill centered on authentication APIs, this increases the chance of credential mishandling and token theft, which could enable unauthorized API access.
The skill documents a login flow that sends highly sensitive data including account identifiers, passwords, and captcha values to a remote API, but it does not explicitly warn users that these secrets leave the local environment. In an agent or tool context, omission of this disclosure can mislead operators into providing credentials to an external service without informed consent, increasing the risk of credential exposure, misuse, or policy violations.
This markdown file documents a login flow that sends account, login_pwd, captcha_code_key, and captcha_code via POST, but it does not include any warning about sensitive credential handling, privacy impact, or security considerations. Under the markdown-file criteria for SQP-2, user-facing documentation should disclose behaviors that affect user data or privacy.
This markdown file describes an admin login flow that sends account, login_pwd, captcha_code_key, and captcha_code in a POST request to a remote service. Under the markdown-specific warning rule, the description should disclose that sensitive credentials are being transmitted and note the associated privacy/security implications, but no such warning is present.
The manifest description instructs callers to set lang=zh-cn, which imposes a specific locale. The file does not provide user opt-in, alternative language options, or a clear justification that this skill is region-specific, so it conflicts with the language/locale policy.
The user-facing markdown repeats the requirement to use lang=zh-cn, again enforcing a specific locale. Because no alternative is offered and no region-specific rationale is provided, this is a natural-language policy violation.
The skill documents collection of account credentials and the return of access and refresh tokens, but provides no warning about sensitive-data handling, storage, masking, or log exposure. In an agent/tooling context, this increases the chance that passwords or tokens are copied into prompts, traces, logs, or downstream tools, leading to account compromise if exposed.
The instructions explicitly require lang=zh-cn in the request headers, which is a language/locale constraint stated in natural language. The file does not offer an opt-in choice or explain why the skill must be restricted to Chinese locale, so this matches the locale-policy violation category.
The markdown body repeats the same locale requirement, again directing use of lang=zh-cn as a fixed header value. Because the skill does not provide language choice or explain a legitimate region-specific constraint, this is a natural-language policy issue.
This markdown file documents a login flow that uses a phone number, SMS verification code, device token, and request signing, which involves sensitive personal and authentication data. The description provides operational steps but does not include any warning about privacy, data handling, or the sensitivity of using login credentials over an API.
This manifest-style description explains how to call the refresh-token endpoint but does not define any explicit trigger phrases, activation conditions, or exclusions for when the skill should be invoked. Without clear boundaries or negative examples, the skill may be matched too broadly whenever token refresh or authentication is mentioned.
Hard-coding lang=zh-cn without user choice can cause requests to be sent with an unintended locale, which may produce misleading responses, incorrect UX, or policy mismatches in multilingual environments. In an authentication flow, this can increase operational risk because users may misread prompts or verification-related responses, though it is not a high-severity compromise by itself.
The main markdown body repeats operational steps for refreshing a token, but it does not state the precise conditions under which the skill should activate versus when other authentication skills should handle the request. This absence of trigger scope can cause unintended invocation overlap with general login, auth, or token-related requests.
The duplicate instruction to force lang=zh-cn reinforces a fixed locale requirement and can systematically override user or application language settings. In the context of authentication APIs, this is mainly a reliability and usability security issue, as misunderstanding token or verification responses can lead to mistakes during sensitive account operations.
The manifest description explicitly instructs callers to use lang=zh-cn, which imposes a specific locale. This is a natural-language policy concern because the file does not indicate user opt-in, alternatives, or a region-specific justification for forcing Chinese locale.
The markdown instructions again require lang=zh-cn, reinforcing a fixed locale behavior. Because no alternative language handling or rationale is provided, this conflicts with the policy against forcing a specific language or locale without user choice.
The natural-language description and usage instructions are entirely in Korean, and the file does not indicate that this skill is intentionally limited to Korean-speaking users or a Korean-only environment. Per the policy, forcing a specific language without user opt-in or justification is a natural-language policy violation.
The skill documents transmitting a user's phone number to an external API but does not warn users that personally identifiable information will leave the local system and be sent to a third-party endpoint. This can undermine informed consent and privacy expectations, especially because the endpoint is an external AWS-hosted service and the phone number is central to authentication flows.
The skill explicitly sends a phone number, country/area metadata, and registration-related context to an external API, but the documentation does not clearly warn users that personally identifiable information will leave the local environment. This creates a privacy and consent risk because an operator or downstream agent may invoke the endpoint without understanding that sensitive user data is being transmitted to a third-party service.
The file explicitly instructs requests to use lang=zh-cn, and the same requirement is repeated later in the body. This is a natural-language locale policy issue because it imposes a specific language/locale setting without user opt-in or a documented region-specific reason.
This markdown file documents a login flow that sends account and login_pwd in a POST body to a remote endpoint, but it does not warn users that sensitive credentials will be transmitted. Under the markdown-file criteria for SQP-2, behaviors affecting user data or privacy should include an explicit warning or disclosure.
The markdown instructions require lang=zh-cn for the request header but do not provide any option for the user to choose a different language or explain why this locale is required. That makes the locale constraint a policy concern under SQP-3.
The file explicitly instructs callers to set the request header lang=zh-cn, and the same requirement is repeated later in the document. This imposes a specific language/locale behavior without offering user opt-in or explaining a necessary region-specific constraint.
This markdown file documents a login flow that sends account and login_pwd in a POST body and yields reusable authentication tokens. Under the markdown-specific warning criterion, the description lacks any caution about sensitive credential/token handling, privacy implications, or safe storage/use of the returned tokens.