T09 · Insecure Skill Coding Practices
- Location
src/utils/request.js:78- Finding
API Token Exposure Through URL Query Parameters
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This appears to be a real Xiaohongshu data-collection skill, but it needs Review because its top description understates broader search and author-tracking capabilities and its API token is sent in URL parameters.
Install only if you want a broader Xiaohongshu research tool, not just a single-note comment retriever. Use a dedicated token you can rotate, avoid submitting sensitive or private links, and remember that returned public-profile, note, and comment data will be sent to the third-party API service and saved locally in logs.
src/utils/request.js:78API Token Exposure Through URL Query Parameters
The documentation exposes a full keyword-search workflow with filtering and task completion semantics, which is materially broader than single-note comment retrieval. In context, this makes the skill more dangerous because it is positioned as a narrow comments tool but can be used for broader content discovery and collection at scale.
The documentation exposes a full keyword-search workflow with filtering and task completion semantics, which is materially broader than single-note comment retrieval. In context, this makes the skill more dangerous because it is positioned as a narrow comments tool but can be used for broader content discovery and collection at scale.
The documentation exposes a full keyword-search workflow with filtering and task completion semantics, which is materially broader than single-note comment retrieval. In context, this makes the skill more dangerous because it is positioned as a narrow comments tool but can be used for broader content discovery and collection at scale.
The documentation exposes a full keyword-search workflow with filtering and task completion semantics, which is materially broader than single-note comment retrieval. In context, this makes the skill more dangerous because it is positioned as a narrow comments tool but can be used for broader content discovery and collection at scale.
The documentation exposes a full keyword-search workflow with filtering and task completion semantics, which is materially broader than single-note comment retrieval. In context, this makes the skill more dangerous because it is positioned as a narrow comments tool but can be used for broader content discovery and collection at scale.
The documentation exposes a full keyword-search workflow with filtering and task completion semantics, which is materially broader than single-note comment retrieval. In context, this makes the skill more dangerous because it is positioned as a narrow comments tool but can be used for broader content discovery and collection at scale.
The documentation exposes a full keyword-search workflow with filtering and task completion semantics, which is materially broader than single-note comment retrieval. In context, this makes the skill more dangerous because it is positioned as a narrow comments tool but can be used for broader content discovery and collection at scale.
The documentation exposes a full keyword-search workflow with filtering and task completion semantics, which is materially broader than single-note comment retrieval. In context, this makes the skill more dangerous because it is positioned as a narrow comments tool but can be used for broader content discovery and collection at scale.
The documentation exposes a full keyword-search workflow with filtering and task completion semantics, which is materially broader than single-note comment retrieval. In context, this makes the skill more dangerous because it is positioned as a narrow comments tool but can be used for broader content discovery and collection at scale.
The documentation exposes a full keyword-search workflow with filtering and task completion semantics, which is materially broader than single-note comment retrieval. In context, this makes the skill more dangerous because it is positioned as a narrow comments tool but can be used for broader content discovery and collection at scale.
The documentation exposes a full keyword-search workflow with filtering and task completion semantics, which is materially broader than single-note comment retrieval. In context, this makes the skill more dangerous because it is positioned as a narrow comments tool but can be used for broader content discovery and collection at scale.
The documentation exposes a full keyword-search workflow with filtering and task completion semantics, which is materially broader than single-note comment retrieval. In context, this makes the skill more dangerous because it is positioned as a narrow comments tool but can be used for broader content discovery and collection at scale.
The documentation exposes a full keyword-search workflow with filtering and task completion semantics, which is materially broader than single-note comment retrieval. In context, this makes the skill more dangerous because it is positioned as a narrow comments tool but can be used for broader content discovery and collection at scale.
The top-level manifest markets the skill as comment-only, but the body documents broader search, note-detail, and author-tracking features. This kind of scope deception is dangerous because it can mislead users, reviewers, and automated policy gates into granting approval for a narrower tool than what is actually shipped.
Referenced artifact was not completely inspected
- "分析这条小红书笔记评论区的主要观点和负面反馈: node src/xiaohongshu/detail-cli.js --url 'https://www.xiaohongshu.com/explore/xxx?xsec_token=yyy' --limit 100"
Referenced artifact was not completely inspected
- "分析这条小红书笔记评论区的主要观点和负面反馈: node src/xiaohongshu/detail-cli.js --url 'https://www.xiaohongshu.com/explore/xxx?xsec_token=yyy' --limit 100"
Referenced artifact was not completely inspected
- "分析这条小红书笔记评论区的主要观点和负面反馈: node src/xiaohongshu/detail-cli.js --url 'https://www.xiaohongshu.com/explore/xxx?xsec_token=yyy' --limit 100"
Referenced artifact was not completely inspected
- "分析这条小红书笔记评论区的主要观点和负面反馈: node src/xiaohongshu/detail-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/comment-cli.js` | 笔记 URL | 该笔记的评论内容、评论者信息、互动数据 |
Referenced artifact was not completely inspected
| 看某篇小红书笔记的评论数据 | `src/xiaohongshu/comment-cli.js` | 笔记 URL | 该笔记的评论内容、评论者信息、互动数据 |
Referenced artifact was not completely inspected
| 看某篇小红书笔记的评论数据 | `src/xiaohongshu/comment-cli.js` | 笔记 URL | 该笔记的评论内容、评论者信息、互动数据 |