linkfox-shopee-store-orders

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

• Third-party content exposure detected (medium risk: 0.30). 在 required workflow 的运行时通过 POST /shopee/developerProxy 调用 Shopee Order API，并将代理返回的 developerProxy.body 解析进 out[response_key] 后（即上游数据的自由文本字段）进行摘要/打印并落盘到 linkfox/.../data/...json，因此会处理外部（Shopee订单数据/可能含买家自由文本如备注/处方 free_text）里的内容。

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

• Secret detected (high risk: 1.00). I scanned the skill files for literal, high-entropy credentials. I ignored obvious placeholders and examples such as "", "<order_sn>", "67890", environment variable names (LINKFOX_AGENT_API_KEY, etc.), and short/simple passwords because those are documentation examples or setup defaults.

I found one hardcoded, non-obvious, high-entropy value:

• A base64url-like constant assigned to _LOGIN_FIXED_UID in scripts/onboarding.py. It is used as a fixed UID header for the login flow (used when access_token/user_id are missing). This is a literal token-like value (not a placeholder) and therefore should be treated as a secret (or at least sensitive), so I flag it.

All other potentially-looking values in the repo are placeholders, example IDs, environment-variable defaults, or non-secret configuration and were ignored per the rules.