节假日查询 - 即刻数据

Security checks across malware telemetry and agentic risk

Overview

This holiday lookup skill is mostly coherent, but it has an undocumented API-host override that could send the user’s Jike AppKey to an unexpected server.

Review before installing. Use a low-scope Jike API key, do not set JIKE_API_BASE_URL unless you intentionally trust that endpoint, and avoid copying, logging, or sharing full request URLs because they include the AppKey. Use the skill for holiday/date lookups only.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Taint TrackingDirect Taint Flow, Variable-Mediated Taint Flow, Credential Exfiltration Chain
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Tainted flow: 'url' from os.environ.get (line 136, credential/environment) → urllib.request.urlopen (network output)

Critical
Category
Data Flow
Content
"""
    url = f"{API_BASE_URL}{API_PATH_MAP[command]}?{urllib.parse.urlencode({**params, 'appkey': appkey})}"
    try:
        with urllib.request.urlopen(url, timeout=15) as response:
            return json.loads(response.read().decode("utf-8"))
    except urllib.error.HTTPError as exc:
        return {"code": exc.code, "message": f"接口请求失败: HTTP {exc.code}", "data": ""}
Confidence
95% confidence
Finding
with urllib.request.urlopen(url, timeout=15) as response:

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The documentation instructs direct API use with `appkey` embedded in the URL query string, but does not warn that query parameters are commonly exposed in logs, browser history, proxies, and monitoring systems. This creates a realistic credential-leak risk for anyone copying the example literally, especially in agent/tooling environments that may log full request URLs.

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The AppKey is placed in the URL query string, which is commonly logged by proxies, servers, browser/history tooling, and debugging systems. Even over HTTPS, query parameters are more likely to be exposed in operational logs, increasing the chance of credential leakage.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal