Most shell execution and obfuscation alerts are false positives from JavaScript template literals, ANSI escape codes, Markdown examples, and Chinese text. Confirmed issues are the external API dependency, token handling through environment or default credentials, and persistent local result caching. No prompt injection evidence was found in the reviewed files.
The code makes HTTPS requests to the external Guaikei service and includes user keywords and token-derived parameters. This is expected functionality but still transfers data outside the local environment.
The code makes HTTPS requests to the external Guaikei service and includes user keywords and token-derived parameters. This is expected functionality but still transfers data outside the local environment.
The code makes HTTPS requests to the external Guaikei service and includes user keywords and token-derived parameters. This is expected functionality but still transfers data outside the local environment.
The code makes HTTPS requests to the external Guaikei service and includes user keywords and token-derived parameters. This is expected functionality but still transfers data outside the local environment.
The script writes the full final search output to scripts/last-search.json. This can persist user keywords, result links, and returned metadata without a retention control.
The script writes the full final search output to scripts/last-search.json. This can persist user keywords, result links, and returned metadata without a retention control.
The command reads GUAIKEI_API_TOKEN from process.env and passes it into external API calls. Accessing a secret-bearing environment variable is security relevant.
The command reads GUAIKEI_API_TOKEN from process.env and passes it into external API calls. Accessing a secret-bearing environment variable is security relevant.
The flagged line reads GUAIKEI_API_TOKEN, which is then used in outbound API requests. The pattern is not an environment file read, but it is sensitive credential handling.
The surrounding token module returns a bundled default API token when GUAIKEI_API_TOKEN is absent. A shared embedded credential is a real security and abuse risk.
The token helper returns a hardcoded default token when GUAIKEI_API_TOKEN is missing. Shared fallback credentials can be abused and make API usage hard to attribute.
The fallback branch directly returns a 32-character token string after warning the user. The behavior is explicit in the token management module.
The API token is placed into query parameters for task creation and result lookup. Query strings are often logged by clients, proxies, and services.
The script reads GUAIKEI_API_TOKEN and both request builders include token in querystring parameters. This is direct evidence of credential exposure through URLs.
The command writes the latest complete result object to scripts/last-search.json. This can retain user keywords, Xiaohongshu links, and returned profile metadata after the command finishes.
The final output object contains keyword, result links, metrics, and metadata, then writeFileSync saves it locally. The code has no opt-out or retention setting.
04
是正措置
この監査で推奨される修正が記録されています。これらを適用する責任はメンテナーにあります。
FIX-001
高
Bundled default API token
Remove the hardcoded fallback token and fail closed when GUAIKEI_API_TOKEN is missing.
FIX-002
高
API token in URL query parameters
Send credentials in an Authorization header or another non-logged channel instead of query strings.
FIX-003
中
Persistent local result cache
Make last-search.json optional, document retention, and provide a setting to disable local writes.
FIX-004
中
Third-party network dependency
Clearly disclose data sent to www.guaikei.com and require user confirmation before network requests.