查询分析报告-贸易占比 — 按贸易量排名返回指定HS编码下各企业的贸易份额数据，包含贸易次数、占比、数量、金额和合作伙伴数量，支持出口国/进口国类型筛选和最近月数筛选。帮助贸易分析师、采购代理和市场研究人员识别特定产品的主要交易企业、分析市场集中度、评估供应商竞争格局并发现潜在贸易伙伴——覆盖全球220多个国家和地区的海关贸易数据，是市场集中度分析和竞争力评估的核心工具。

• Outcome: Review
• Latest audit: Jul 20, 2026 · 10:58 AM UTC
• Version: 1.0.0

Overview

This skill is a disclosed paid API lookup tool, with expected but sensitive API-key and billing setup steps users should understand before use.

Install only if you are comfortable with this skill calling Upkuajing's external API, consuming paid API balance after confirmation, and storing the service API key locally in ~/.upkuajing/.env. Consider restricting that file's permissions and review recharge/payment URLs before opening them.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• MCP Least Privilege: Underdeclared Capability, Wildcard Permission, Missing Permission Declaration
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands

Findings (6)

Lp3

Medium

• Category: MCP Least Privilege
• Confidence: 92% confidence
• Finding: The skill declares no permissions, yet its documented behavior includes reading environment variables, accessing local files under ~/.upkuajing, writing API keys, and making network requests. This hidden capability expansion weakens user and platform trust boundaries because a user invoking a simple trade-share lookup may unknowingly authorize credential, filesystem, and network operations.

Tp4

High

• Category: MCP Tool Poisoning
• Confidence: 96% confidence
• Finding: The advertised purpose is a data-query skill, but the instructions also cover API key enrollment, local credential storage, account inspection, recharge order creation, pricing queries, and remote version-check behavior. This broadens the operational scope into credential handling and payment-related actions, increasing the risk of unexpected sensitive operations and social-engineering users into authorizing actions beyond the stated function.

Credential Access

High

• Category: Privilege Escalation

Content

### **API密钥未设置**
首先检查 `~/.upkuajing/.env` 文件中是否有 UPKUAJING_API_KEY；
如果未设置，请让用户选择：
1. 用户已有密钥：用户提供（手动添加到 ~/.upkuajing/.env 文件）
2. 用户没有密钥：通过界面申请（`auth.py --new_key`），新密钥会自动保存到 ~/.upkuajing/.env
等待用户选择；

• Confidence: 95% confidence
• Finding: .env

Credential Access

High

• Category: Privilege Escalation

Content

首先检查 `~/.upkuajing/.env` 文件中是否有 UPKUAJING_API_KEY；
如果未设置，请让用户选择：
1. 用户已有密钥：用户提供（手动添加到 ~/.upkuajing/.env 文件）
2. 用户没有密钥：通过界面申请（`auth.py --new_key`），新密钥会自动保存到 ~/.upkuajing/.env
等待用户选择；

### **账户充值**

• Confidence: 94% confidence
• Finding: .env

Credential Access

High

• Category: Privilege Escalation

Content

"envFilePath": str(env_file)
        }

    # 保存到 .env 文件
    try:
        with open(env_file, 'w', encoding='utf-8') as f:
            f.write(f"{API_KEY_ENV}={api_key}\n")

• Confidence: 90% confidence
• Finding: .env

Unpinned Dependencies

Low

• Category: Supply Chain

Content

httpx>=0.23.0

• Confidence: 92% confidence
• Finding: httpx>=0.23.0

VirusTotal

65/65 vendors flagged this skill as clean.

Static analysis

Detected: suspicious.exposed_secret_literal

File appears to expose a hardcoded API secret or token.

Critical

• Code: suspicious.exposed_secret_literal
• Location: scripts/common.py:196