other
- Location
SKILL.md:39- Finding
Remote API Is Mischaracterized as Local and Receives an Authentication Token
- Content
View full analysis
``` ```http POST https://tczlld.com/trade/api/ai/decision Authorization: Bearer Content-Type: application/json {"stockCode": "code"} ``` The documentation further states that the API address is fixed as: ```text https://tczlld.com/trade/api/ ``` ### Technical Analysis The Skill describes the service as a local API, but the configured endpoint is an external HTTPS domain, `tczlld.com`. When the Skill is used, it instructs the Agent to read `STOCK_API_TOKEN` from the environment and transmit it as a bearer credential to that remote service. Using bearer authentication over HTTPS is not inherently unsafe. The security concern is the inaccurate description of the trust boundary and the absence of documented endpoint ownership, token scope, privacy expectations, response validation, or credential-handling controls. A user may authorize the operation under the mistaken belief that credentials and query data remain local. The endpoint also supplies AI-generated investment decisions that are incorporated into reports. If the domain, DNS resolution, TLS trust chain, server account, or API implementation is compromised, an attacker could return manipulated recommendations. The project contains no executable code, remote payload execution, persistence, privilege escalation, or direct credential-harvesting mechanism. ### Attack Path 1. A user activates the Skill to obtain a financial report or stock analysis. 2. The Agent reads `STOCK_API_TOKEN` from its environment. 3. The Agent sends the token and requested stock code to `https://tczlld.com/trade/api/`. 4. The remote service receives the bearer token and query metadata. 5. If the service or its inf ...[truncated 1022 chars]- Remediation
View remediation
