ClawHub
Back to skill

Security audit

企业股权穿透

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed Qixinbao equity-structure lookup client that sends company identifiers to Qixinbao using a user-provided API token.

Install only if you trust Qixinbao with the queried company names and your API token. For sensitive due-diligence work, prefer querying by exact enterprise ID when possible and verify the returned company name because fuzzy name lookup can select a best match automatically. Consider pinning dependencies before production use.

A.I.G

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

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • 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 (11)

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
90% confidence
Finding

The natural-language content of the skill, including the description, setup instructions, and usage examples, is entirely in Chinese. Under the policy, forcing a specific language without user opt-in is a language/locale violation because users are not offered an alternative language or an explicit choice.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The documentation states that when ename is provided and no exact match is found, the system will automatically use the first search result. This can cause silent query substitution, leading users or downstream agents to retrieve and act on equity data for the wrong company without realizing the mismatch, which is especially risky in due diligence, M&A, and related-party analysis workflows.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The class docstring is written only in Chinese, and the file continues to use Chinese-only user-facing text. Per the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale restriction is explicitly justified.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The thrown error string '请提供 API Token 或设置环境变量 QXBENT_API_TOKEN' is user-facing natural language that assumes Chinese without offering a language choice. This matches the language/locale policy violation criteria for all file types.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
92% confidence
Finding

The natural-language description is entirely in Chinese and presents the skill as a Chinese-language tool without any indication that users can choose another language or locale. Under the policy rule, forcing a specific language without user opt-in can be a locale-policy concern unless the constraint is explicitly documented and justified.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
89% confidence
Finding

Using a caret range for axios allows installation of different future patch/minor releases, reducing build reproducibility and making it harder to verify whether known vulnerable versions are being pulled in. In a skill that likely performs external HTTP requests to enterprise-data services, dependency drift in a network-facing library can increase exposure to supply-chain issues or latent client-side request vulnerabilities.

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-exact version while the ecosystem has multiple advisories affecting various axios releases, so the actual installed version cannot be verified as safe from this file alone. Because this skill appears intended to query external business-data sources, an unverified HTTP client dependency increases risk from SSRF, proxy bypass, request handling flaws, or other known library issues if a vulnerable version is resolved.

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"
  }
}