linkfox-shopee-store-video

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

• Third-party content exposure detected (medium risk: 0.30). 该 skill 在运行时通过 scripts/video_api.py / _video_api_runner.run_video_api() 将用户传入的 shopId/merchantId/body/query 组装后调用 POST /shopee/developerProxy 并直接把 Shopee 返回的 JSON（含任意字符串字段）打印/落盘（scripts/_shopee_video_common.py:emit_result）。

HIGH W008: Secret detected in skill content (API keys, tokens, passwords).

• Secret detected (high risk: 1.00). I scanned the skill files for high-entropy, literal values that could be usable credentials. I ignored obvious placeholders and examples such as "", "xxx", "67890", "$KEY", and simple setup strings (per the provided rules).

Finding flagged:

• scripts/onboarding.py [48-49] defines a literal base64url-looking string assigned to _LOGIN_FIXED_UID with a preceding comment "登录链路固定 uid header（实测可用）". The value "eyJhX2lkIjoiNmEyMmM4YjA1YmM5MTZhIiwiZF9pZCI6IiJ9" is a high-entropy/base64-encoded token-like value and the comment indicates it is a fixed, actually usable UID header. Because it is a non-placeholder, hardcoded token that the code will use as a uid header when no environment override is present, it meets the definition of a hardcoded credential and should be treated as a secret.

Ignored items (examples/placeholders):

• Numerous occurrences of placeholders for API keys or examples (e.g., export LINKFOXAGENT_API_KEY="", curl examples, "xxx" in accessToken, "67890" as shopId) — these are documentation/test values and were not flagged.