Full contact data validation eliminates inaccurate lead information for global B2B prospecting. Run multi-dimensional phone checks to distinguish valid/invalidnumbers, landlines, mobile lines and WhatsApp registered accounts. Complete email authentication to flag active and dormant mailboxes, alongside domainvalidation to confirm functional or defunct business websites. Streamline email validation, phone validation and domain verification workflows for sales teams,recruiters and export businesses. Cut email bounce rates drastically and boost efficiency for B2B cold outreach and global prospect search. Execute professionalCRM data cleansing, candidate screening and supplier lead validation via all-in-one verification features. Perfect for bulk export email pre-sending datacleaning, talent recruitment screening and overseas buyer identity verification.

• Outcome: Review
• Latest audit: Jul 17, 2026 · 12:36 AM UTC
• Version: 1.0.3

Overview

This skill appears to be a disclosed paid contact-validation API wrapper, with some privacy and credential-handling caveats users should understand.

Install only if you are comfortable sending the contact data you validate to UpKuaJing's remote API and paying per API call. Protect the UPKUAJING_API_KEY file, do not enable API logging when processing sensitive contact lists unless you accept local retention, and review top-up/payment URLs before acting on them.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep
• MCP Least Privilege: Underdeclared Capability, Wildcard Permission, Missing Permission Declaration

Findings (13)

Lp3

Medium

• Category: MCP Least Privilege
• Confidence: 89% confidence
• Finding: The skill invokes capabilities beyond a purely declarative contact-checking workflow: it expects environment-secret access, reads a local .env file, may write configuration, and makes outbound network requests, yet those capabilities are not explicitly declared as permissions. This weakens transparency and informed consent, making it easier for a user or hosting platform to underestimate what the skill can access and do.

Tp4

High

• Category: MCP Tool Poisoning
• Confidence: 92% confidence
• Finding: The advertised purpose is contact-info validation, but the skill also includes account-management and billing-related behaviors such as account info lookup, recharge-order creation, payment URL handling, pricing queries, and remote version checks. This materially expands the trust boundary: users invoking a verification tool may not expect actions that touch billing state or expose financial/account metadata.

Context-Inappropriate Capability

Medium

• Confidence: 94% confidence
• Finding: This file implements API key issuance, account info retrieval, recharge order creation, and pricing queries, which are unrelated to the advertised contact-info validation function. That scope expansion increases the skill's privilege and risk surface by introducing credential lifecycle and billing capabilities that a user may not expect when installing a validation skill.

Description-Behavior Mismatch

Medium

• Confidence: 96% confidence
• Finding: The behavior in this file diverges from the stated skill purpose by managing credentials and payment flows instead of performing phone, email, WhatsApp, or domain validation. Such mismatch is dangerous because it can mislead users into granting or running code with financial/account side effects outside the expected task.

Missing User Warnings

Medium

• Confidence: 85% confidence
• Finding: The documentation instructs users to send phone numbers and a Bearer authorization token, but it provides no warning that these are sensitive data or guidance on secure handling. In a contact-validation skill, this omission increases the chance that users will transmit personal data to a third-party API without informed consent, proper minimization, or safe logging/storage practices.

Missing User Warnings

Medium

• Confidence: 89% confidence
• Finding: The code can log full request parameters and response bodies to ~/.upkuajing/logs when ENABLE_API_LOGGING is enabled, with no redaction or user-facing disclosure. In this skill context, request/response data may contain emails, phone numbers, WhatsApp status results, domain details, and possibly account-related metadata, creating a local privacy leak and sensitive-data retention risk.

Missing User Warnings

Medium

• Confidence: 96% confidence
• Finding: The script sends user-supplied email addresses to a remote validation endpoint via make_request('/agent/validation/email', params) without any explicit user-facing disclosure, consent prompt, or minimization controls. Because email addresses are personal/contact data and the skill is specifically marketed for CRM cleansing and cold-email workflows, silent transmission to a third-party service creates privacy, compliance, and confidentiality risk if operators assume processing is local.

Missing User Warnings

Medium

• Confidence: 89% confidence
• Finding: The script sends phone numbers to a remote endpoint via make_request('/agent/validation/phone', params) without any explicit user-facing notice, confirmation, or documented consent flow at execution time. Because phone numbers are personal data, silent transmission to a third-party service creates a privacy and compliance risk, especially in CRM cleansing and recruiter/exporter workflows that may process large third-party contact lists.

Missing User Warnings

Low

• Confidence: 76% confidence
• Finding: The module performs an undocumented outbound version-check request that is not part of the skill's stated contact-validation workflow, which can surprise users and leak metadata about installed skills or usage timing to a remote service. In a data-cleansing skill context, hidden network behavior is more concerning because users may expect tight control over what leaves their environment, even if only the skill name is transmitted here.

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: Guide user to apply at [UpKuaJing Open Platform](https://developer.upkuajing.com/)
Wait for user selection;

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

Credential Access

High

• Category: Privilege Escalation

Content

except IOError as e:
        return {
            "success": False,
            "message": f"API密钥申请成功，但保存到 .env 文件失败：{str(e)}。\n请手动设置环境变量 {API_KEY_ENV}。",
            "envFilePath": str(env_file)
        }

• Confidence: 84% confidence
• Finding: .env

Unpinned Dependencies

Low

• Category: Supply Chain

Content

httpx>=0.23.0

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

VirusTotal

64/64 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

File appears to expose a hardcoded API secret or token.

Critical

• Code: suspicious.exposed_secret_literal
• Location: SKILL.md:95