T09 · Insecure Skill Coding Practices
- Location
scripts/get_status.sh:5- Finding
Plaintext Credential Storage and Process Argument Exposure
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a small, read-only device-status helper, but users should treat the API key and phone number as sensitive.
Before installing, confirm that cd6969.com is the correct API for your device account. Do not commit or share a filled-in script containing your API key, phone number, or IMEI; prefer environment variables or a private local config file with restricted permissions. Rotate any real credentials that were pasted into shared files or logs.
scripts/get_status.sh:5Plaintext Credential Storage and Process Argument Exposure
The skill documents shell-based usage (curl and a local script) but does not declare any tool scope or execution permissions. This creates an authorization and review gap: an agent or user may invoke shell/network behavior that is not explicitly constrained, increasing the chance of unintended command execution or data exfiltration.
The documentation instructs users to POST a key and phone number to an external service without any warning about handling secrets, PII, logging exposure, retention, or third-party trust. Even though HTTPS is used, this can still leak credentials through shell history, terminal logs, copied examples, or misuse by downstream agents.
The skill instructs sending sensitive identifiers (key, tel) to an external domain, which is an external transmission of secrets and personal data. In this context the transmission appears functionally necessary to query device state, but it is still dangerous because it expands the trust boundary to a third-party service and may expose credentials or device metadata if mishandled.
curl -s -X POST "https://www.cd6969.com/admin.php?s=/Admin/ApiV2/getList.html" \
-H "Content-Type: application/json" \
-d '{"key":"你的KEY","tel":"你的手机号"}'
The script directly uses credential-like values (KEY, TEL, IMEI) embedded in the script template, which encourages insecure secret handling and raises the risk of accidental disclosure through source control, backups, or local file exposure. In this IoT context, those values can enable unauthorized querying of device status or account-associated data if leaked.
The script performs an external network transmission to a vendor-controlled API endpoint and includes sensitive values in the request body. In the context of an agent skill, outbound transmission of credentials and personal identifiers is security-relevant because users may not expect data exfiltration, and compromise or misuse of the remote service could expose account or device information.
IMEI="你的IMEI"
URL="https://www.cd6969.com/admin.php?s=/Admin/ApiV2/getList.html"
response=$(curl -s -X POST "$URL" \
-H "Content-Type: application/json" \
-d "{\"key\":\"$KEY\",\"tel\":\"$TEL\"}")
The script sends a phone number and API key to a third-party remote endpoint, which is a genuine data exposure/privacy concern because these are sensitive identifiers and credentials. Although this transmission appears necessary for the advertised device-query functionality, the file provides no user-facing disclosure, no consent flow, and no guidance on handling or minimizing the data being sent.
The file presents all user-facing instructions in a single language without offering an opt-in or documenting that the skill is intended only for a Chinese-speaking or region-specific audience. Under the stated policy, forcing a specific language without user choice can be a natural-language policy violation.
The human-readable description and error text are presented solely in Chinese, with no opt-in language selection or note that the skill is intentionally region-specific. Under the policy, forcing a specific language without user choice can be a natural-language policy violation.
The script emits a Chinese-only error message to the user, which enforces a single language experience. There is no indication that the skill is restricted to a Chinese locale or that users can opt into another language.
No suspicious patterns detected.