T09 · Insecure Skill Coding Practices
- Location
src/utils/request.js:76- Finding
API Credential Exposed in HTTP Query Strings
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches its Xiaohongshu research purpose, but it handles tokens and saved result data in ways users should review before installing.
Review this skill before installing if your Xiaohongshu research, note URLs, or Guaikei API token are sensitive. It sends requests to Guaikei and automatically saves returned data under logs/, so protect that directory, avoid committing it, delete old outputs when no longer needed, and consider rotating the API token if logs or infrastructure traces may have exposed it.
src/utils/request.js:76API Credential Exposed in HTTP Query Strings
src/utils/log.js:25Automatic Plaintext Persistence of Retrieved Data and Access-Bearing URLs
The manifest claims broad keyword-based list retrieval and comparative analysis, but the reported implementation centers on fetching details/comments from a single note link. This mismatch can lead to overcollection, mistaken invocation, and data being sent to an external provider without the level of user awareness that a narrower, accurate description would provide.
The manifest claims broad keyword-based list retrieval and comparative analysis, but the reported implementation centers on fetching details/comments from a single note link. This mismatch can lead to overcollection, mistaken invocation, and data being sent to an external provider without the level of user awareness that a narrower, accurate description would provide.
The manifest claims broad keyword-based list retrieval and comparative analysis, but the reported implementation centers on fetching details/comments from a single note link. This mismatch can lead to overcollection, mistaken invocation, and data being sent to an external provider without the level of user awareness that a narrower, accurate description would provide.
The manifest claims broad keyword-based list retrieval and comparative analysis, but the reported implementation centers on fetching details/comments from a single note link. This mismatch can lead to overcollection, mistaken invocation, and data being sent to an external provider without the level of user awareness that a narrower, accurate description would provide.
The manifest claims broad keyword-based list retrieval and comparative analysis, but the reported implementation centers on fetching details/comments from a single note link. This mismatch can lead to overcollection, mistaken invocation, and data being sent to an external provider without the level of user awareness that a narrower, accurate description would provide.
The manifest claims broad keyword-based list retrieval and comparative analysis, but the reported implementation centers on fetching details/comments from a single note link. This mismatch can lead to overcollection, mistaken invocation, and data being sent to an external provider without the level of user awareness that a narrower, accurate description would provide.
The manifest claims broad keyword-based list retrieval and comparative analysis, but the reported implementation centers on fetching details/comments from a single note link. This mismatch can lead to overcollection, mistaken invocation, and data being sent to an external provider without the level of user awareness that a narrower, accurate description would provide.
The manifest claims broad keyword-based list retrieval and comparative analysis, but the reported implementation centers on fetching details/comments from a single note link. This mismatch can lead to overcollection, mistaken invocation, and data being sent to an external provider without the level of user awareness that a narrower, accurate description would provide.
The manifest claims broad keyword-based list retrieval and comparative analysis, but the reported implementation centers on fetching details/comments from a single note link. This mismatch can lead to overcollection, mistaken invocation, and data being sent to an external provider without the level of user awareness that a narrower, accurate description would provide.
The manifest claims broad keyword-based list retrieval and comparative analysis, but the reported implementation centers on fetching details/comments from a single note link. This mismatch can lead to overcollection, mistaken invocation, and data being sent to an external provider without the level of user awareness that a narrower, accurate description would provide.
The manifest claims broad keyword-based list retrieval and comparative analysis, but the reported implementation centers on fetching details/comments from a single note link. This mismatch can lead to overcollection, mistaken invocation, and data being sent to an external provider without the level of user awareness that a narrower, accurate description would provide.
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
- "拉这条笔记的评论做观点聚类: 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"
This file adds comment-collection functionality that goes beyond the skill’s stated scope of searching public notes and returning note-level engagement metrics. Scope expansion is dangerous because it can collect more granular user-generated content than users and reviewers expect, increasing privacy, compliance, and platform-policy risk.
The manifest describes a skill for keyword-based discovery of public Xiaohongshu notes, including sorting and time filtering, but this file implements a separate workflow that accepts a note URL and fetches comments for that note. Retrieving comment content is materially different from searching note lists and comparing keyword performance, so this behavior goes beyond the described capability.
The manifest describes a skill for searching public Xiaohongshu notes by keyword, with ranking by likes/comments/favorites and time filtering. This file instead requires a '小红书博主链接' profile URL and creates a '主页笔记' task to retrieve notes from a specific creator homepage, which is a different user intent and data access pattern.
The skill declares access to an environment secret (GUAIKEI_API_TOKEN) but does not define an explicit tool/permission scope. That weakens least-privilege boundaries and makes it harder for a host agent to reason about what capabilities the skill actually needs before invocation.
The description includes broad trigger phrases like "最近什么火" and "帮我找热门内容" even when the user does not explicitly mention Xiaohongshu. Overbroad activation criteria increase the chance that an agent routes unrelated social-media or general research requests into this skill, causing unintended third-party data transfer and scope creep.
The README claims competitor monitoring, KOL screening, trend prediction, and comment analysis despite the manifest describing a narrower public-note keyword search tool. Overstating data collection and analysis powers is dangerous because it obscures true operational scope and may hide higher-risk data handling behaviors from users and platform reviewers.
Detected: suspicious.exposed_secret_literal