T08 · Insecure Dependencies
- Location
analyze.py:7- Finding
Untrusted External Module Loading Through a Hard-Coded Import Path
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly does the advertised retail clerk performance analysis, but it loads an unbundled API client from a hard-coded developer machine path before fetching employee sales data.
Install only if you trust the publisher and can verify or replace the missing api_client dependency. Before using it with real store data, confirm what service get_copilot_data contacts, what credentials it uses, and that the user is authorized to process named clerk performance metrics.
analyze.py:7Untrusted External Module Loading Through a Hard-Coded Import Path
The trigger section lists natural-language intents such as "导购团队结构如何" and "哪些导购对业绩影响最大" without defining exclusions, required retail context, or negative examples. These phrases could overlap with general analytical discussion and may cause unintended invocation outside the intended store-clerk performance analysis scenario.
The module-level natural-language description and user-facing log/output strings are entirely in Chinese, which effectively forces a specific language/locale. The file does not offer any language selection, fallback, or opt-in mechanism.
The code prepends a hard-coded local filesystem path to sys.path, causing imports to be resolved from an uncontrolled developer-specific workspace location. This creates a supply-chain and environment-manipulation risk: if that path exists and contains a modified api_client module, the skill may execute unintended code or access data through an unreviewed dependency.
The skill fetches store and clerk performance data over the network without any normal user-facing disclosure, consent, or transparency in non-verbose execution. Because this data is individually attributable employee performance information, silent retrieval increases privacy and data-governance risk and can lead to unauthorized or unexpected processing of sensitive business metrics.
The manifest description and trigger instructions force a specific language presentation, and the document does not state that the skill is region-specific or provide any user opt-in for language/locale. Under the policy, locale constraints should be justified or optional rather than implicit.