T09 · Insecure Skill Coding Practices
- Location
src/utils/request.js:76- Finding
API Credential Transmitted in URL Query Strings
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill appears to be a real Xiaohongshu research tool, but it needs review because its narrow comment-focused description conflicts with broader data-collection capabilities and it handles stored results and API tokens in risky ways.
Install only if you are comfortable sending Xiaohongshu keywords or links and your GUAIKEI_API_TOKEN to Guaikei's API, and with retrieved public data being saved locally under logs. Review the broader search, detail, comment, and creator-monitoring behavior despite the comment-only description, avoid sensitive workspaces, and rotate the API token if exposure through URL logging is a concern.
src/utils/request.js:76API Credential Transmitted in URL Query Strings
src/utils/log.js:25Retrieved Data Is Automatically Persisted in Plaintext Log Files
The search workflow supports keyword-based discovery across Xiaohongshu rather than retrieval of comments for a specific note. In context, that broader harvesting capability is dangerous because it can be used for large-scale content collection while masquerading as a narrow comment-analysis utility.
The search workflow supports keyword-based discovery across Xiaohongshu rather than retrieval of comments for a specific note. In context, that broader harvesting capability is dangerous because it can be used for large-scale content collection while masquerading as a narrow comment-analysis utility.
The search workflow supports keyword-based discovery across Xiaohongshu rather than retrieval of comments for a specific note. In context, that broader harvesting capability is dangerous because it can be used for large-scale content collection while masquerading as a narrow comment-analysis utility.
The search workflow supports keyword-based discovery across Xiaohongshu rather than retrieval of comments for a specific note. In context, that broader harvesting capability is dangerous because it can be used for large-scale content collection while masquerading as a narrow comment-analysis utility.
The search workflow supports keyword-based discovery across Xiaohongshu rather than retrieval of comments for a specific note. In context, that broader harvesting capability is dangerous because it can be used for large-scale content collection while masquerading as a narrow comment-analysis utility.
The search workflow supports keyword-based discovery across Xiaohongshu rather than retrieval of comments for a specific note. In context, that broader harvesting capability is dangerous because it can be used for large-scale content collection while masquerading as a narrow comment-analysis utility.
The search workflow supports keyword-based discovery across Xiaohongshu rather than retrieval of comments for a specific note. In context, that broader harvesting capability is dangerous because it can be used for large-scale content collection while masquerading as a narrow comment-analysis utility.
The search workflow supports keyword-based discovery across Xiaohongshu rather than retrieval of comments for a specific note. In context, that broader harvesting capability is dangerous because it can be used for large-scale content collection while masquerading as a narrow comment-analysis utility.
The search workflow supports keyword-based discovery across Xiaohongshu rather than retrieval of comments for a specific note. In context, that broader harvesting capability is dangerous because it can be used for large-scale content collection while masquerading as a narrow comment-analysis utility.
The search workflow supports keyword-based discovery across Xiaohongshu rather than retrieval of comments for a specific note. In context, that broader harvesting capability is dangerous because it can be used for large-scale content collection while masquerading as a narrow comment-analysis utility.
The search workflow supports keyword-based discovery across Xiaohongshu rather than retrieval of comments for a specific note. In context, that broader harvesting capability is dangerous because it can be used for large-scale content collection while masquerading as a narrow comment-analysis utility.
The search workflow supports keyword-based discovery across Xiaohongshu rather than retrieval of comments for a specific note. In context, that broader harvesting capability is dangerous because it can be used for large-scale content collection while masquerading as a narrow comment-analysis utility.
The manifest claims a comment-only analysis skill, but the body documents multiple broader capabilities: keyword search, note detail retrieval, and creator post monitoring. Security review, user consent, and policy routing often rely on manifest metadata, so this discrepancy can lead to under-scoped approvals for a significantly more capable data-collection tool.
Referenced artifact was not completely inspected
- "分析这条小红书笔记评论区的主要观点和负面反馈: node src/xiaohongshu/comment-cli.js --url 'https://www.xiaohongshu.com/explore/xxx?xsec_token=yyy' --limit 100"
Referenced artifact was not completely inspected
- "分析这条小红书笔记评论区的主要观点和负面反馈: node src/xiaohongshu/comment-cli.js --url 'https://www.xiaohongshu.com/explore/xxx?xsec_token=yyy' --limit 100"
Referenced artifact was not completely inspected
- "分析这条小红书笔记评论区的主要观点和负面反馈: node src/xiaohongshu/comment-cli.js --url 'https://www.xiaohongshu.com/explore/xxx?xsec_token=yyy' --limit 100"
Referenced artifact was not completely inspected
- "分析这条小红书笔记评论区的主要观点和负面反馈: node src/xiaohongshu/comment-cli.js --url 'https://www.xiaohongshu.com/explore/xxx?xsec_token=yyy' --limit 100"
Referenced artifact was not completely inspected
- "看这个小红书博主最近 20 条作品都在发什么: node src/xiaohongshu/post-cli.js --url 'https://www.xiaohongshu.com/user/profile/xxx?xsec_token=yyy' --limit 20"
Referenced artifact was not completely inspected
- "看这个小红书博主最近 20 条作品都在发什么: node src/xiaohongshu/post-cli.js --url 'https://www.xiaohongshu.com/user/profile/xxx?xsec_token=yyy' --limit 20"
Referenced artifact was not completely inspected
- "看这个小红书博主最近 20 条作品都在发什么: node src/xiaohongshu/post-cli.js --url 'https://www.xiaohongshu.com/user/profile/xxx?xsec_token=yyy' --limit 20"
Referenced artifact was not completely inspected
- "看这个小红书博主最近 20 条作品都在发什么: node src/xiaohongshu/post-cli.js --url 'https://www.xiaohongshu.com/user/profile/xxx?xsec_token=yyy' --limit 20"
Referenced artifact was not completely inspected
| 看某篇笔记的详情+评论 | `src/xiaohongshu/detail-cli.js` | 笔记 URL | `explore/` 或短链 |
Referenced artifact was not completely inspected
| 看某篇笔记的详情+评论 | `src/xiaohongshu/detail-cli.js` | 笔记 URL | `explore/` 或短链 |
Referenced artifact was not completely inspected
| 看某篇笔记的详情+评论 | `src/xiaohongshu/detail-cli.js` | 笔记 URL | `explore/` 或短链 |
The README presents the skill as a broad Xiaohongshu data-mining and marketing suite, which materially exceeds the manifest's declared comment-analysis scope. This scope mismatch is dangerous because it can hide undeclared capabilities from reviewers and users, enabling overcollection of platform data or use of functions that were not approved or expected in the advertised skill context.