other
- Location
token.env:2- Finding
Lookalike Domain in Credential Acquisition Instructions
- Content
View full analysis
Vulnerability Details
File Location:
token.env, line 2
Vulnerability Type: Potential phishing through a lookalike domain
Risk Level: MediumVulnerable code snippet:
dotenv # 获取地址:https://tussahre.pro → 个人中心 → 接口TokenTechnical Analysis
The configuration template directs users to
https://tussahre.pro, while the service identified throughoutSKILL.mdishttps://tushare.pro. The former transposes letters in the legitimate service name and is therefore a lookalike hostname.Directing users to a lookalike domain is unnecessary for the Skill's declared market-data functionality. Even if this is an accidental typographical error, users may trust the bundled instructions and visit the unrelated domain while attempting to obtain an API token. The security of TLS does not mitigate this issue because HTTPS only authenticates the hostname that the user actually visits.
Attack Path
- A user installs the Skill and reads
token.envfor token setup instructions. - The user opens
https://tussahre.pro. - If the lookalike domain is controlled by an attacker, it presents a page resembling the legitimate Tushare service.
- The user submits account credentials, an existing token, or other sensitive information.
- The attacker captures that information and uses it against the legitimate service.
Impact Assessment
Exploitation could disclose the user's Tushare credentials or API token to an unrelated party. A captured token may permit unauthorized API requests within the victim's Tushare account permissions, consume quotas, access entitled financial datasets, or cause account disruption. This issue does not directly grant local system privileges or code execution.
- A user installs the Skill and reads
- Remediation
View remediation
Remediation Suggestions
- Replace
https://tussahre.prowith the verified official URL,https://tushare.pro. - Review all documentation and configuration templates for inconsistent or lookalike hostnames.
- Prefer linking to a verified provider documentation page rather than directing users generically to an authentication page.
- Add an automated URL-validation or allowlist check during release review.
- Inform users that the API token should only be submitted to the verified Tushare API endpoint.
- Replace
