Back to skill

Security audit

企业上市信息查询

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed company-listing lookup client that sends a configured API token and company identifier to Qixin's listed-company API, with no hidden persistence or destructive behavior found.

Reasonable to install if you trust Qixin and need this listed-company data. Verify the returned enterprise name or use eid for important work, and consider pinning dependencies plus protecting QXBENT_API_TOKEN as a persistent credential.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (10)

Tp4

High
Category
MCP Tool Poisoning
Confidence
94% confidence
Finding

The declared description presents a fairly sophisticated cross-market aggregation and comparison tool. However, the supplied code is only a thin wrapper around one external API endpoint (/enterprise/getListedInfo) with two lookup modes: by enterprise name or by enterprise ID. There is no visible implementation of multi-market data aggregation, field standardization, horizontal comparison, batch querying, or integration across separate resources. While the backend API might internally provide some of that functionality, the code chunk itself only demonstrates simple single-entity retrieval. Therefore the declared description overstates what the provided code actually does, creating a material description-behavior mismatch.

Content

No source excerpt is available for this finding.

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
70% confidence
Finding

Without declared permissions the skill's intent is opaque and cannot be validated.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The only user-facing natural-language description is written in Chinese and presents the skill as Chinese-language oriented, with no indication that users may choose another language or that the locale restriction is intentional and documented. This can violate language/locale policy when no user opt-in or justification is provided.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The documentation explicitly states that when an enterprise name cannot be matched exactly, the system will automatically select the first search result. In a financial-research and due-diligence context, this can cause users or downstream agents to retrieve and act on data for the wrong listed company, producing materially incorrect analysis, comparisons, or compliance conclusions without any warning.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
85% confidence
Finding

This is a manifest file, so vague-trigger review applies. The description says the tool provides comprehensive listed-company queries in one place, but it does not specify concrete trigger phrases, activation boundaries, or exclusions, which can make invocation conditions overly broad for general finance-related requests.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
90% confidence
Finding

Using a caret range for a runtime dependency allows future installs to resolve to different releases, including versions that may later introduce vulnerable behavior or supply-chain compromise. In a skill that likely performs external HTTP requests for market and company data, an unsafe axios version could materially affect network security, request handling, or SSRF-related exposure.

Content

Scanner excerpt · package.json (reported line 26)May include surrounding context.

json
"author": "",
  "license": "MIT",
  "dependencies": {
    "axios": "^1.6.0"
  },
  "devDependencies": {
    "@types/node": "^20.0.0",

Unverifiable Dependency: axios has 16 known advisory(ies) (CVE-2026-44494 (axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `co); CVE-2026-44495 (axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollut); CVE-2025-62718 (Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF) +13 more), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
87% confidence
Finding

The manifest references axios with a non-pinned semver range while the package family has multiple known advisories, making it impossible to verify whether resolved installs are affected. Because this skill appears to aggregate external enterprise and market data over HTTP, uncertainty around a network-facing library increases the risk of SSRF, proxy bypass, credential leakage, or response manipulation if a vulnerable release is installed.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · package.json (reported line 29)May include surrounding context.

json
"axios": "^1.6.0"
  },
  "devDependencies": {
    "@types/node": "^20.0.0",
    "ts-node": "^10.9.0",
    "typescript": "^5.0.0"
  }

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · package.json (reported line 30)May include surrounding context.

json
},
  "devDependencies": {
    "@types/node": "^20.0.0",
    "ts-node": "^10.9.0",
    "typescript": "^5.0.0"
  }
}

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · package.json (reported line 31)May include surrounding context.

json
"devDependencies": {
    "@types/node": "^20.0.0",
    "ts-node": "^10.9.0",
    "typescript": "^5.0.0"
  }
}