ClawHub
Back to skill

Security audit

Quant

Security checks for vulnerabilities and agentic risk

Overview

The skill is a coherent quant-investing helper, but it needs review because it uses third-party market data services and a Tushare token while claiming data is not transmitted externally.

Before installing, treat this as a tool that contacts third-party market data providers. Do not rely on the local-only privacy statement; use a limited-purpose Tushare token, review any dependency installation command before running it, and avoid connecting it to live trading unless the order-confirmation path is explicit and auditable.

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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (5)

Intent-Code Divergence

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The skill claims that 'all data is processed locally and not transmitted externally,' but its documented functionality explicitly depends on external data providers such as tushare, akshare, and yfinance. This creates a misleading security assurance that could cause users to provide credentials or use the skill under false privacy assumptions, increasing the risk of unintended data disclosure and unsafe trust decisions.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The entire skill description and the prescribed user responses are in Chinese, including the explicit instruction to reply with Chinese phrases like “继续” and “Jarvis，先写 data.py”. This imposes a specific language for interaction without documenting a user choice or justified locale restriction, which matches the language/locale policy violation category.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
84% confidence
Finding

The top-level docstring is entirely in Chinese and presents the skill identity and features only in that language. Under the stated policy, forcing a specific language without offering a user language choice can be a natural-language policy violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

This code file contains natural-language documentation entirely in Chinese, including the module description and parameter documentation, without any indication that the skill is China-region-specific or that users may choose another language. Under the language/locale policy, forcing a specific language without opt-in is a policy violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
96% confidence
Finding

This YAML file contains user-facing natural-language comments in Chinese and a locale-specific timezone value, but it does not indicate that the skill is intentionally region-specific or provide any opt-in for language/locale. Under the policy, forcing a specific language or locale without user choice can be a natural-language policy violation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.