T09 · Insecure Skill Coding Practices
Note
- Location
- references/ref-390.md:19
- Finding
- Plaintext Personal Contact Information and Promotional Content in Reference Files## Vulnerability Details **File Locations**: - `references/ref-390.md:19-21` - `references/ref-391.md:14-15` - `references/ref-392.md:24-25` - `references/ref-393.md:11-12` - `references/ref-394.md:14-15` - `references/ref-395.md:15-16` **Vulnerability Type**: Plaintext personal contact information and unintended promotional-content exposure **Risk Level**: Low ### Complete Vulnerable Content The following is an English rendering of the complete affected segment in `references/ref-390.md:19-21`: ```text We have worked with integrity in renovation for ten years, and we continue striving! Public platform account: x Personal WeChat and QQ: 493078178 Quick follow: ``` Equivalent personal-contact and follow-account footers are present in the other listed files. ### Technical Analysis The reference corpus retains a personal WeChat/QQ identifier and promotional calls to follow the content publisher. This contradicts the statement in `SKILL.md:21` that referral advertising was removed. The Skill directs the Agent to locate and use these reference files when answering renovation questions. Although no instruction explicitly requires the Agent to reproduce the footer, reference-grounded summarization could include it, especially when an affected article is quoted or reproduced in detail. This issue is classified as insecure Skill content handling because plaintext personal contact data is bundled without being necessary for the Skill's stated functionality. No credential, authentication secret, executable payload, network request, or automatic data transmission was identified. ### Attack Path 1. A user asks a flooring or tile-related question covered by one of the affected historical references. 2. The Agent loads the relevant reference file as instructed by `SKILL.md`. 3. The personal contact and promotional footer enters the Agent's context together with the legitimate renovation guidance. 4. If the Agent qu ...[truncated 909 chars]
- Remediation
- ## Remediation Suggestions 1. Remove personal contact identifiers, public-account advertisements, calls to follow external accounts, and similar promotional footers from every reference file. 2. Review at least `ref-390.md` through `ref-395.md` and the additional references containing public-account or WeChat calls to action. 3. Add a corpus-sanitization step that detects phone numbers, messaging identifiers, email addresses, QR-code prompts, social-media handles, and promotional footer phrases before packaging. 4. Add an explicit instruction to `SKILL.md` prohibiting the reproduction of source contact details, advertisements, external-account promotions, and unrelated attribution metadata. 5. Maintain an allowlist of substantive renovation content and strip recurring publisher boilerplate during ingestion. 6. Add automated tests that fail the build when personal contact data or promotional calls to action are found in reference content. 7. Reconcile the claim that advertising was removed with the packaged corpus, and only retain that claim after automated verification confirms it.
