UpKuaJing global company and contact search, find global companies, verify contacts, and generate high-quality B2B leads for cross-border trade. UpKuaJing helps exporters, sourcing agents, and sales teams discover decision-makers, source suppliers, and accelerate international customer acquisition — all in one search.

• Outcome: Pass
• Latest audit: May 29, 2026 at 8:37 PM UTC
• Version:
  1.0.6

Overview

This is a coherent UpKuaJing API integration for paid company and people/contact searches, with sensitive but disclosed credential and data-handling risks.

Install only if you trust UpKuaJing with your searches and contact-data use case. Prefer setting UPKUAJING_API_KEY through an environment secret or secret manager instead of printing or manually inspecting ~/.upkuajing/.env, confirm expected charges before running searches, and delete local task_data or log files when no longer needed.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• MCP Least Privilege: Underdeclared Capability, Wildcard Permission, Missing Permission Declaration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (8)

Lp3

Medium

• Category: MCP Least Privilege
• Confidence: 93% confidence
• Finding: The skill declares no permissions while instructing use of environment variables, reading and writing `~/.upkuajing/.env`, and making networked API calls. This mismatch reduces transparency and weakens consent boundaries, making credential handling and external data access more dangerous because users and platforms cannot accurately evaluate what the skill can do.

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The documentation explicitly states that the API may return employee contact data such as email, phone, WhatsApp, and a sample employee contact record, but it provides no privacy, consent, purpose-limitation, retention, or lawful-use guidance. In a skill whose stated purpose is customer development, background checks, and talent search, this omission materially increases the risk of misuse for unsolicited outreach, profiling, or privacy-law violations.

Missing User Warnings

Medium

• Confidence: 84% confidence
• Finding: The code writes a newly issued API key directly to a local .env file without any confirmation, explicit warning, or permission hardening. This can unintentionally overwrite credential storage or place secrets in a predictable location that may later be read by other tooling, backed up, or exposed through weak filesystem permissions.

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The script sends company-search parameters to a remote API and persists returned company data to task files, but it provides no explicit notice, consent checkpoint, retention policy, or access-control indication around that transmission and storage. In a skill explicitly designed to collect business registration and contact details, silent persistence increases privacy, compliance, and unintended data exposure risk if task files are later accessed by other users or processes.

Missing User Warnings

Medium

• Confidence: 88% confidence
• Finding: The script retrieves person records and persists them to task result files via append_result_data without any visible notice, consent flow, retention control, or access restriction in this file. Because the skill explicitly targets contact details and background information, silent local storage increases privacy, compliance, and secondary exposure risk if those files are accessible to other users, processes, or logs.

Credential Access

High

• Category: Privilege Escalation

Content

### **API Key Not Set**
First check if the `~/.upkuajing/.env` file has UPKUAJING_API_KEY;
If UPKUAJING_API_KEY is not set, prompt the user to choose:
1. User has one: User provides it (manually add to ~/.upkuajing/.env file)
2. User doesn't have one: You can apply using the interface (`auth.py --new_key`), the new key will be automatically saved to ~/.upkuajing/.env
Wait for user selection;

• Confidence: 91% confidence
• Finding: .env

Credential Access

High

• Category: Privilege Escalation

Content

First check if the `~/.upkuajing/.env` file has UPKUAJING_API_KEY;
If UPKUAJING_API_KEY is not set, prompt the user to choose:
1. User has one: User provides it (manually add to ~/.upkuajing/.env file)
2. User doesn't have one: You can apply using the interface (`auth.py --new_key`), the new key will be automatically saved to ~/.upkuajing/.env
Wait for user selection;

### **Account Top-up**

• Confidence: 90% 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: 87% confidence
• Finding: .env

VirusTotal

67/67 vendors flagged this skill as clean.