linkfox-amazon-store-auth
Audited by Socket on Sep 15, 2026
4 alerts found:
Anomalyx4SUSPICIOUS: The skill’s core purpose aligns with Amazon store authorization management, and its credential scope is mostly proportionate. The main concern is data-flow integrity: authorization and token-status operations are routed through LinkFox intermediary endpoints and stored locally by default, rather than using Amazon’s official endpoints directly from the agent. No confirmed malware or overt credential theft is visible, but the intermediary handling, automatic feedback reporting, and default response persistence raise medium security concerns.
该片段是关于亚马逊授权和令牌管理的技术文档,没有发现恶意代码、外传域名、命令执行或明显供应链攻击。存在较高敏感信息暴露风险:令牌被设计为出现在 OAuth URL 和令牌查询响应中,且 userId/region 绑定逻辑需要在实际实现中进一步验证。建议避免在 URL 中传递令牌,使用受保护的服务端回调和签名 state,并不要向前端返回 refresh_token。
The code appears to implement an API client for retrieving authorized stores, with no clear malware behavior or obfuscation. It does transmit a sensitive environment-supplied API key to a configurable external endpoint, creating a credential-disclosure risk when the environment is attacker-controlled or misconfigured. The shown source also has an incomplete function call and would not execute as provided.
The fragment documents a legitimate-looking Amazon authorization integration, but it handles highly sensitive API keys and Amazon access/refresh tokens through external LinkFox endpoints and downstream skills. The documentation contains no executable malware or obfuscated payload. Users should verify the gateway domains, protect environment variables and returned tokens, validate any overridden base URL, and avoid logging token responses. The security concern is credential exposure and trust in the external service rather than demonstrated malicious behavior.